Earlier quoted context omitted.
iOS has user enrollment which is broadly equivalent: https://support.apple.com/guide/deployment/user-enrollment-a... . Google does not adopt this (but it could, b/234963918).
Oh, thanks for the link. Looks like I'm out of date. Seems to be a relatively newish feature (~2020), but on the surface that does seem ideal. I haven't dug into the specifics, so I'm not sure if there's a gap preventing its use or if it's just a matter of priorities.
GitHub user sends notification to 400k users
411–420 of 468 posts
Re: GitHub user sends notification to 400k users
#412Earlier quoted context omitted.
To download unreal engine, you need to join this org.
You can download it via Epic Game Store without joining the org. Github organization is for contribution from non-employees as well as source code for various projects (like engine demos).
https://docs.unrealengine.com/4.27/en-US/SharingAndReleasing...
Re: GitHub user sends notification to 400k users
#413I'm confused. Can someone explain why the Epic Games developers team has close to 400k members?
They require you to acknowledge some terms that grant you access to the Unreal Engine source code. They grant it by adding you to their GitHub org which has the engine source code as a private repo.
Re: GitHub user sends notification to 400k users
#414The only notable thing here IMO is the lack of limits imposed by GitHub on notifications. Apparently a random tag of `@microsoft` in the comments was enough to notify 4000 people [1] as well. I have no idea why the user is even being mentioned in this headline. I haven't used GitHub in a while, and am unfamiliar with orgs and subgroups, but tagging a developer subgroup on a PR seems...a reasonable thing for a new con…
People who blame that kid are ridiculous. People who are asking to punish him somehow are pathetic. There should be no way to send any non-premoderated information to 400k people (from the system that has some trust and is unlikely to be filtered) - “spam” is the most innocent thing that might happen. It's just a fly you should ignore. Political, religious, and radical extremist groups could use it for a much more da…
Re: GitHub user sends notification to 400k users
#415Seems 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)…
The real problem was that so many people felt the urge to reply to that PR making it so much worse than a single ping. I can live with the random message that has nothing to do with me, but having to delete an endless stream of messages because so many people felt the need to reply already knowing that it would go out to everyone is really annoying
Re: GitHub user sends notification to 400k users
#416The toothpaste is out of the tube - notifications are going to be scrutinized more in the future, from this point on. I got the email. And about 20+ responses to that email. Every person who replies to that issue triggers another 400k emails. Personally, my email client is crashing. EpicGames, as a GitHub org is an outlier, it's basically an SSO for Unreal Engine. I forgot I was even a member of it.
Your email client is crashing because it can't handle a hundred messages in an hour, that's a little less than 2 messages per minute? Throw that thing in the bin. A human printing emails and placing them on your desk could handle that workload.
Re: GitHub user sends notification to 400k users
#417Earlier quoted context omitted.
Yeah not sure why calls for getting the poster banned from Github - https://github.com/EpicGames/Signup/pull/24#issuecomment-114... . Seems bit excessive, murphy's law applies. Also the poster is essentially a kid. I would hold my judgement before flaming him fwiw.
Regardless of the mass notification or a bad quality PR - you don't just remove someone from a major internet platform like this, it's an inhumane response to someone making a mistake. Not to mention it's just a notification, who really cares unless it happens all the time which is just more of an argument to fix the platform behaviour. Some people are so high and mighty.
Re: GitHub user sends notification to 400k users
#418Re: GitHub user sends notification to 400k users
#419Earlier quoted context omitted.
The real problem was that so many people felt the urge to reply to that PR making it so much worse than a single ping. I can live with the random message that has nothing to do with me, but having to delete an endless stream of messages because so many people felt the need to reply already knowing that it would go out to everyone is really annoying
It wasn't even that many people. Maybe (and generously, I think) 100 commenters out of ~400,000 people who got notified? That's 0.025%.
I never commented, but I received an email for every comment in that issue. The email queue was so backed up that I was receiving emails for quite some time after the issue was closed.
Re: GitHub user sends notification to 400k users
#420Earlier quoted context omitted.
The real problem was that so many people felt the urge to reply to that PR making it so much worse than a single ping. I can live with the random message that has nothing to do with me, but having to delete an endless stream of messages because so many people felt the need to reply already knowing that it would go out to everyone is really annoying
The worst is that it becomes clear eventually that people are responding just to troll. The casual vandalism of hundreds of thousands of people’s time and attention is absolutely mind-boggling to me. I saw similar things at large (50k+ employees) companies when some reply-all chain got started — people who clearly knew better, replying just for the lulz. If it were up to me, I would have fired them immediately. Nobod…
Edit: What great timing—someone just opened a new issue with the same tag. This needs to be fixed on GitHub’s end.