Live data from Hacker News

GitHub user sends notification to 400k users

github.com

371–380 of 468 posts

Re: GitHub user sends notification to 400k users

#371

Seems like an innocent enough mistake. Remind me of when I once helped organize a volunteer hackathon with people from different companies. We created a Slack organization just for the occasion. At the end of the event, I was supposed to ask all attendees to delete all the data we had given them before they went home. The message I posted to #general (the channel everyone in a Slack organization is required to be in)…

This reminds me of something that happened to me a couple of years ago, near the start of the pandemic and when we had recently switched from Skype for Business to Microsoft Teams.

I needed to set up a one-to-one Teams meeting with a colleague, so I hit the 'Schedule meeting' button, added my colleague as an attendee, filled in the meeting name, date and time.

I saw that Teams was asking me to select a channel. I didn't realise this was an optional field, so I just selected the General channel in my department's Teams channel. It seemed the most appropriate. And so I sent out the meeting invite, thinking it would only go to one colleague (the only one I had selected as a participant).

I realised something was wrong a few moments later when I started receiving out-of-office responses from people I didn't recognise. I checked the meeting invite in my sent folder and realised it had gone out to the entire department. Hundreds of people, including all the senior managers and even the CTO!

Turns out that when you specify a channel when creating a meeting in Teams, it also sends the meeting invite to everybody who has access to that channel which, in this case, was the entire department. There was no indication that this would happen, however.

Still, I learnt my lesson. Now I know not to select a channel when creating a Teams meeting.

Re: GitHub user sends notification to 400k users

#372

Earlier quoted context omitted.

if it's open source but in a private repo, couldn't somebody just make a public mirror? open source implies the right to redistribute source code.

Open source has no formal definition. There are tons of different licenses. They can be OSI-approved or not. Edit: I doubt the license for this code is an OSI-approved one with this registration business. But I have not checked and I won't check.

There is a trademark for "Open Source", and if you want to use it without written approval from OSI, you have to use it for something under an OSI-approved license: https://opensource.org/trademark-guidelines#Usage_That_Does_...

I think this is the closest you can come to a "formal definition", short of a law defining the term.

Re: GitHub user sends notification to 400k users

#374

Innocent mistake. The kid is barely 18. The emotion and stress resulting from mistakenly sending a notification to 400,000 is likely overwhelming. Now his real name is going to stay at the center of the internet for a while thanks to being 1st on HN. I would definitely not have coped well with that much internet attention at his age. Some Github replies are more immature than the initial action and I hope he does not…

The patch itself is indeed worse than useless, it's the kind of rephrasing just to say "I did something", but which actually makes it worse (adds useless words and English mistakes). If the "kid" is ready to send this kind of useless "contribution" (which takes some deliberate effort), they surely are ready for being reprimanded (or, more likely, they will be actually proud of it).

Reprimanding for the useless PR and rude tone makes sense.

But tagging half a million people was clearly an accident that should be better protected against.

Re: GitHub user sends notification to 400k users

#375

Innocent mistake. The kid is barely 18. The emotion and stress resulting from mistakenly sending a notification to 400,000 is likely overwhelming. Now his real name is going to stay at the center of the internet for a while thanks to being 1st on HN. I would definitely not have coped well with that much internet attention at his age. Some Github replies are more immature than the initial action and I hope he does not…

I disagree, the PR is some pointless wordsmithing and then to comment "Verify the pull request and merge asap" is a bit ridiculous. Also, no one is going to care in a day.

> Verify the pull request and merge asap" is a bit ridiculous

I see you're not familiar with Indian-English. What he said sounds quite "reasonable" (if not a bit unnecessarily, but understandably urgent) to someone like me (am Indian).

Re: GitHub user sends notification to 400k users

#376

Earlier quoted context omitted.

Looks like a typical PR from young programmers who are learning English, which is consistent with the rest of the profile.

Yeah typical of people that have more narcissism than technical acumen The better action would be to report the user as spam

I am in several communities that receive many users from the east and that is very common of them: absolute disregard for the rules, common courtesy or even common sense. If they want something, they will keep asking for it even if it's offtopic or even the wrong channel/group/forum/etc until they get it, regardless of whether they are disrupting ongoing conversations or whatever. I suppose that it's a cultural thing.

Re: GitHub user sends notification to 400k users

#380
post #68

There are quite a few other, uh, interesting PRs for that repo. https://github.com/EpicGames/Signup/pulls https://github.com/EpicGames/Signup/pull/10/files https://github.com/EpicGames/Signup/pull/18/files What is going on?

Looking at the content of the OP and the PRs you linked, my first thought is "Is it Hacktoberfest[1] already?". I mean, seriously, what's up with the such low quality PRs? Is it common to have people spamming repos with trivial changes absent some sort of incentive? [1] https://www.theregister.com/2020/10/01/digitalocean_hacktobe...

The main repo I work on for my job is open-source, and yes, it happens fairly regularly that someone opens a nonsensical PR that might randomly perturb some Markdown or YAML file, or attempt to merge commits from some other developer's in-progress branch.

I'd say we only get them about once every week or so, but then the repo is not anywhere near as high-profile as the Unreal Engine, nor as likely to be on the radar of children.

Post reply on HN