Discord Incident – Resolved

Post by majorchord » Fri, May 08, 2026, 8:46 PM UTC

this_user wrote: post #8

113 wrote: post #3

It's not a novel opinion but I'm tired of things being fucked all the time.

It's gonna get a lot worse with all the AI slopcode that is about to be pushed directly to production.

Post by StableAlkyne » Fri, May 08, 2026, 8:48 PM UTC

omoikane wrote: post #11

Analemma_ wrote: post #7

Earlier quoted context omitted.

How would that have been different in the IRC days?

There would have been a server split, and half of the people would be chatting among themselves wondering why the some people suddenly got disconnected, while being unaware that there might be a server problem because they can still continue to chat. The other half of the people would think the same.

Post by lpcvoid » Fri, May 08, 2026, 8:53 PM UTC

majorchord wrote: post #12

this_user wrote: post #8

Earlier quoted context omitted.

It's gonna get a lot worse with all the AI slopcode that is about to be pushed directly to production.

You mean all the AI "slop" that's finding and writing new kernel exploits every day? And submitting hundreds of previously-unknown security bugs in critical software?

Post by dakolli » Fri, May 08, 2026, 8:56 PM UTC

majorchord wrote: post #12

this_user wrote: post #8

Earlier quoted context omitted.

It's gonna get a lot worse with all the AI slopcode that is about to be pushed directly to production.

You mean all the AI "slop" that's finding and writing new kernel exploits every day? And submitting hundreds of previously-unknown security bugs in critical software?

Post by Aurornis » Fri, May 08, 2026, 9:02 PM UTC

rweichler wrote: post #2

Times like this make me miss the IRC days, I was just able to reproduce a bug in an semi-open-source project, and Discord went down right in the middle of me sending my findings. Now there's nothing I can do about it. I can only wait.