this post was submitted on 12 Jun 2023
56 points (100.0% liked)

Technology

37603 readers
512 users here now

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.

founded 2 years ago
MODERATORS
alyaza@beehaw.org
TheRtRevKaiser@beehaw.org
gyrfalcon@beehaw.org
rs5th@beehaw.org
SemioticStandard@beehaw.org
TheRtRevKaiser@kbin.social
Los@beehaw.org
coldredlight@beehaw.org
remington@beehaw.org
56
Reddit is crashing because of the growing subreddit blackout (www.theverge.com)
submitted 1 year ago by hedge@beehaw.org to c/technology@beehaw.org
32 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] genfood@feddit.de 2 points 1 year ago (1 children)

We don’t know what switching a sub to private, will trigger on their backend. Maybe there is some internal shifting of data somewhere, or something similar to this. Doing this, on a lot of the big subs, could lead to large-scale performance issues.

[–] LemmyAtem@beehaw.org 0 points 1 year ago (1 children)

Interesting/fascinating. I have no idea how development works, but it's interesting to me to see the impact. Someone else mentioned that it could be resource allocation locking up too, which makes sense when I think about it more. A subreddit with subscribers in the millions would need more resources allocated to it due to the increased demand, so if they're suddenly unavailable I can kind of understand why/how that would creat issues. All very neat.

[–] sugar_in_your_tea@sh.itjust.works 0 points 1 year ago

I'm a backend developer and have to deal with this nonsense at my job. There are lots of options, each with tradeoffs, such as:

  • rely on checking at the subreddit level - this means that every time you access a page, you need to check whether the subreddit is private, which means slower page loads
  • include the flag on every post - flipping between private and public can be very expensive on the server
  • embed some info in the URL - breaks links when switching back and forth and is also expensive, but you can cut down on some checks (e.g. no database hit for most checks; i.e. if it's private and you aren't logged in, you cannot access it)

And if you go for one of the two last options, you can reduce the hit when switching by being eventually consistent, meaning you don't change everything all at once but instead set the flag or change the URL in batches over a period of time. That takes effort to get right, and there's going to be inconsistency until everything is done.

So there are multiple ways to do it, and each way has a big chance at devs messing something up when they don't consider something like a bunch of subreddits going private all at once.

Or it could just be a run of the mill DDOS because some redditors wanted to troll Reddit.