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

Technology

37695 readers
306 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
top 19 comments
sorted by: hot top controversial new old
[–] [email protected] 4 points 1 year ago (2 children)

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.

[–] [email protected] 5 points 1 year ago

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.

[–] [email protected] 2 points 1 year ago

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

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (5 children)

A significant number of subreddits shifting to private caused some expected stability issues, and we’ve been working on resolving the anticipated issue.

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

[–] [email protected] 3 points 1 year ago

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

[–] [email protected] 3 points 1 year ago (1 children)

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.

[–] [email protected] 2 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago

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.

[–] [email protected] 2 points 1 year ago

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

[–] [email protected] 2 points 1 year ago

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.

[–] [email protected] 1 points 1 year ago

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.

[–] [email protected] 2 points 1 year ago (1 children)

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

[–] [email protected] 1 points 1 year ago
[–] [email protected] 2 points 1 year ago (1 children)

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.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] [email protected] 3 points 1 year ago

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

[–] [email protected] 1 points 1 year ago

thats kinda hilarious

[–] [email protected] 1 points 1 year ago

Let it burn to fucking ash!

[–] [email protected] 1 points 1 year ago

I suppose the protest may have played a role in the site going down but I thought the outage was mostly due to the cloudflare issues from earlier in the day.