Throw that thing in the bin. A human printing emails and placing them on your desk could handle that workload.
Best thing I've read today only after the email story.
I love me a good bedlam drama. One of the commenters on the PR had the best take: “I just wasted 2 minutes of my life I'll never get back.” The ones with the scorched earth PUNISH HIM attitude need to chill the hell out.
Yeah, being drama queens.
Doesn't that just add to the comedy?
the real issue here is shitty projects from shitty companies.
When you send at the volume someone like GitHub sends, you will always see peaks and valleys in your sending patterns that are much larger than 400k. It might cause an issue if they were already under peak load, but even then it would just take a bit longer.
> Every person who replies to that issue triggers another 400k emails. Personally, my email client is crashing.
Your email client only received 20 messages; why is it crashing? The very long To: header?
That would be a massive privacy breach, and people here would be making a lot more noise about such a large email database being leaked.
[1] https://web.mit.edu/~simsong/www/ugh.pdf page 85
To: [email protected] Subject: blah Action: block
This already happened with github & epic & unreal when it first did this organisation setup. So, given no solution appeared after exact same incident, I wouldn't hold my breath
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.