Live data from Hacker News

Super sorry to the guy with the username reset on GitHub

discuss.systems

241–250 of 261 posts

Re: Super sorry to the guy with the username reset on GitHub

#241
post #56

Earlier quoted context omitted.

Jenny? Don’t change your number.

It's been 41 years since the song came out. Assuming that Jenny was 21 when the song was written, (since there is a chance the number was written on a bar's bathroom wall) she would be at least 62 years old now. Statistically, there's at least a 1 in 4 chance that Jenny is dead now, and there is no chance that she didn't change her number after receiving 800 million horny crank calls.

It was about 5 years ago when I realized that 8675309 is hitting all of the numbers on the keypad diagonally in stripes from the upper left to the lower right, skipping 1 for some reason.

Probably so he could rhyme 'mine' with 'nine'

Re: Super sorry to the guy with the username reset on GitHub

#242

Earlier quoted context omitted.

Important to keep elected officials on their toes, or who knows what they'll come up with next

Biden: "I don't remember subscribing to hotsexyfiremen.com..."

I'm pretty sure that mailbox these days goes directly to /dev/null — if not, they must have the craziest spam filtering setup.

Isn't this the most popular email address?

Re: Super sorry to the guy with the username reset on GitHub

#243
post #216

Earlier quoted context omitted.

I own a few 867-5309 numbers for different areas. I have them do nothing these days but for a while I let them hit a pbx and we’d get up to 2500 calls a day on each line. Lots of drunk dudes trying to call Jenny.

There's a prank call podcast called The Snow Plow Show, and the guy set up a bot at a phone number that will automatically reply to callers with voice clips from a lady who yelled at him in a prank call one time. So fans of the show will put the number on windshields or craigslist ads so people will call the number and get yelled at, and the calls are all recorded so he can listen back to them later and pull out the…

Hahaha! Never thought I'd see BeverlyBot and Sorry I Dinged Your Car mentioned on HN.

Been listening to RBCP (The guy who does Snow Plow Show and Phone Losers of America) for a long time now. Great to throw on in the background for some laughs at the end of the day while reading.

Re: Super sorry to the guy with the username reset on GitHub

#244
post #223
post #120

I've been quite embarrassed to discover that linking to a github issue in another repo will create a back link in the linked issue. Removing the link doesn't undo it either, you need to delete the issue completely. I wish I could turn this feature off.

It's fine, it doesn't ping anybody. Unless you're doing something embarrassing or spammy, I doubt anyone cares. I like being able to see how an issue affects other projects, that can be useful information.

To me it just seems like noise when a "large" issue on a big project references a issue on my personal project with a single user. Having to scroll trough dozens of references would probably be annoying.

Re: Super sorry to the guy with the username reset on GitHub

#245
post #178

Earlier quoted context omitted.

I have my first name . last name @ gmail and it’s definitely a reminder of how big the world is. I had previously thought my name was fairly unique. I don’t engage anymore unless it’s a small business trying to get paid.

My girlfriend has a rather uncommon name, but her FirstNameMiddleName@gmail.com gets emails meant for someone else rather frequently. Sometimes it’s even official PII or PHI. She’s tried to let people know but they’re surprisingly sometimes not all that receptive? So I think she ignores it now.

I have a similar issue with my Gmail -- my policy is to try to rectify the issue the first couple times it happens, but then just let it happen. The dull ones I filter away from my inbox, but not the most interesting ones. Some of my favorites:

- Every year the same family in Houston includes me in their email thread about who is bringing what to Thanksgiving dinner.

- I am on the mailing list for a Masonic lodge somewhere in England.

- I get receipts when some guy in Australia orders a pizza from Dominos. I also get McDonalds coupons that I think are meant for the same guy.

- I have at various times been sent the meeting minutes from an AA group in Pennsylvania (I am more persistent with trying to get off this list than the others, given the sensitive nature of it).

- I get the newsletter for 4H a group in Sacramento.

Re: Super sorry to the guy with the username reset on GitHub

#246
post #219
post #171

Earlier quoted context omitted.

There use to be a site called batcave.net that gave free space and a subdomain. I had the name search.. search.batcave.net until one day when they decided to take back the search subdomain name and use it for themselves. From that point I've avoid great common usernames that one day might be too great

That's one reason why if you give out subdomains to users, you should do so on a different base domain than you use for your own subdomains.

It's the exact reason that GitHub moved to github.io for GitHub Pages hosting. At first there were a few individual users still grandfathered in to be allowed to use .github.com for their GitHub Pages, but I don't remember who they were and I don't know if that still works for them this many years later.

Re: Super sorry to the guy with the username reset on GitHub

#247
post #219

Earlier quoted context omitted.

That's one reason why if you give out subdomains to users, you should do so on a different base domain than you use for your own subdomains.

It's the exact reason that GitHub moved to github.io for GitHub Pages hosting. At first there were a few individual users still grandfathered in to be allowed to use .github.com for their GitHub Pages, but I don't remember who they were and I don't know if that still works for them this many years later.

The real reason is avoiding user-generated content from stealing authentication cookies. If worldmaker.github.com can run a little bit of javascript to add @worldmaker as admin to all the user's repositories on github.com, well, that's a problem.

Re: Super sorry to the guy with the username reset on GitHub

#248

Earlier quoted context omitted.

It's the exact reason that GitHub moved to github.io for GitHub Pages hosting. At first there were a few individual users still grandfathered in to be allowed to use .github.com for their GitHub Pages, but I don't remember who they were and I don't know if that still works for them this many years later.

The real reason is avoiding user-generated content from stealing authentication cookies. If worldmaker.github.com can run a little bit of javascript to add @worldmaker as admin to all the user's repositories on github.com, well, that's a problem.

Both reasons are true. Also, relatedly, "stealing perceived authenticity": if a user sets up "help.github.com" or "about.github.com" or "wwww.github.com" and then runs a scam from it, it looks like GitHub is running the scam.

Re: Super sorry to the guy with the username reset on GitHub

#249

Earlier quoted context omitted.

Funny that slack’s attempt to keep it from being mentioned revealed the existence of a private channel.

I don't think it works for private channels. Since, as OP says, non-members occasionally could find the channel, it was probably a public channel. The people who complained were probably "multi-channel guests". They'd see masked-out channel names except where they are explicitly allowed.

Ah, no, they wouldn't have been guests. The organisation was large enough that it had multiple “workspaces” corresponding to different divisions. Channels always belong to a workspace, but some are shared between workspaces. You can only see the channels belonging to or shared with your workspace.

Re: Super sorry to the guy with the username reset on GitHub

#250

At my previous job, I decided to make a Slack channel named after one of the C preprocessor directives (#define I think, or maybe #endif). A handful of people found it and appreciated the joke. But then, a few months later, one of the admins contacted me to ask if it would be okay to delete the channel. You see, in large organisations, Slack knows which channels are not meant to be visible to other parts of the org,…

Funny that slack’s attempt to keep it from being mentioned revealed the existence of a private channel.

Slack's search actually had a bug where it would return results with matches inside hidden channel names, highlighting the censored section :)
Post reply on HN