64 points
*

How in the world does setting a bunch of subs to private crash the website?

permalink
report
reply
45 points

High-scale software is complex, sometimes there are edge cases where weird unexpected stuff happens. This isn’t a situation they would normally run into.

permalink
report
parent
reply
9 points

It absolutely is something they would normally run into. I work on maintaining a massive application; think 60+ teams of 6, each extremely specialized and minimal overlap. Almost 75% of my job is predicting issues and avoiding them. Peer testing draws on this a ton as well. They just continue to plainly show that they don’t care. Time and time again, year after year, they continue to have the exact same issues and do fuck all about it.

permalink
report
parent
reply
7 points

Why would they normally run into 6000+ subs going private? I’m sure they tested that their code can generally handle some (usually smaller) subs going private, but the number and size of the subs going dark isn’t a normal scenario and I doubt anyone would have assumed such a successful and coordinated protest involving some of the biggest subs would even be possible a few months ago.

permalink
report
parent
reply
44 points

Someone on Tilde posted that they used to work for Reddit and the way they have the front page set up to pull your subscribed subreddits and the ones that you might like to read from is spaghetti code and very brittle.

permalink
report
parent
reply
9 points

I mean, it’s worked until now lol. Probably should have fixed it, but I can understand why the higher ups wouldn’t want to.

permalink
report
parent
reply
29 points

Reddit has had extremely spotty reliability forever. It got better in recent years, but still came down every few weeks, or would just randomly say “you broke reddit!”. Circa 2015 every evening it would just randomly return 50x errors a good chunk of the time because it was always overloaded.

Backend reliability mustn’t be very high up their priority list. Well, neither is UX (old OR new reddit), and let’s not pretend that they’ve been masterminds when it comes to ad placement either, so the real question is what do the higher ups want, and why can’t they achieve it?

permalink
report
parent
reply
31 points

It’s the user/moderator fault. If they would just keep working without pay there wouldn’t be any problem. /s

permalink
report
parent
reply
20 points

honestly I figured it’d be the result of all those people running deletion scripts on their accounts

permalink
report
parent
reply
25 points

This is probably it. Also ArchiveTeam is archiving Reddit as a high priority target so lots of bots scraping it

permalink
report
parent
reply
4 points

God bless archive.org. We’d be so screwed without their efforts.

permalink
report
parent
reply
8 points

It’s not crashing. It’s just more than 7-80% of the requests getting request error because most of the subreddits went private. It sure does looks like crash to a completely uninformed users but it’s not a crash as we think.

permalink
report
parent
reply
5 points

Maybe their caching doesn’t work for private subreddits

permalink
report
parent
reply
1 point

they havent worked in a world where the site is not constantly slammed in years. they built the thing to be pre-loaded i bet.

permalink
report
parent
reply
34 points

thats kinda hilarious

permalink
report
reply
34 points

Just one thing, must be indefinitely not 48h, otherwise nothing will change. A year have 365 days, 48h it’s a weekend, if subreddits come back after 48h it’s nothing happened.

permalink
report
reply
8 points

I think that stating it as 48 hours was smart. Because if subreddits start saying it’s indefinite, then they have time to start replacing mods and shutting the protest down. Whereas here, 48 hours will pass. They lose a lot of money in just 2 days. And if nothing changes, you’ll likely see decreased quality and/or continued protest.

I think it left room at the table for reddit to cooperate. It’s a common bargaining thing.

permalink
report
parent
reply
4 points

I agree with you and I fear that is exactly what will happen.

permalink
report
parent
reply
33 points

I saw a lot of people saying they used bots to rewrite their entire post history to things like “fuck /u/spez”

I’m thinking that amount of comment editing might be quite the spike on the servers.

permalink
report
reply
17 points
*

I did that, but not “fuck u/spez” because that might get the comment deleted altogether making the edit meaningless. Instead I edited to say the comments been deleted in protest against the API changes.

permalink
report
parent
reply
14 points

If enough of us do it, entire comment chains will be illegible lol

permalink
report
parent
reply
25 points

How much spaghetti is your code if most of the communities switching to private fucks up your website?

permalink
report
reply
24 points

goto 10

permalink
report
parent
reply

Technology

!technology@beehaw.org

Create post

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community’s icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

Community stats

  • 2.8K

    Monthly active users

  • 3.4K

    Posts

  • 78K

    Comments