I swear, a bunch of rich people were bored, got in a room, and decided to see who could kill a social media site

The best freedom was realizing the armor wasn't doing that much to help me and it was just more fun to figure out the silliest outfit to kill bosses in.

I think there is probably a mix of things going on.

First, the angriest people already did leave.

Second, people suck at protesting. I mean, the entire reason it was a 2-day protest instead of defaulting to indefinite is because the idea of sacrificing your own habits in a protest blows people's minds. There is a reason "slacktivism" is a thing.

Third, there is probably a segment of the user base who basically got their addiction checked. Social media is addicting, and reddit is not exception, I mean, even I've kept habitually opening the site this whole week just cause that has been my browsing habit for over a decade. It's just how I've check ed news.

And then lastly, the protest reached the more casual core of people who may have not even known about the protest before hand or understood the extent of it, and they are angry that this thing that didn't affect them took away all their content.

A part of me believes they will give some bs reason to keep their "scab" mods immune, but I would love if they didn't and the chaos that would ensue.

Ostensibly they don't wish to scale at the expense of the quality of their community.

Its both a value add and a negative. For those more focused on their own community (Like beehaw) it's an obvious positive. But for many users, losing access to certain communities on your own instance of choice is going to be a negative. I personally don't blame Beehaw for favoring the former. I think improved moderation tools and more granular federation would at least make the move less of a blow to users.

For reasons no one can fathom

The ROM hacking community takes this personally.

ROM hacking and well, just retro development like this is awesome. I think there is something to be said about the creativity that comes with a limited canvas and so on

Certainly so. From a sort of... sociological point I'm wondering what the impacts are of major instances growing independent of each other. I feel like I can already feel it with kbin and lemmy both growing separately during the blackout. I'm wondering if the trend for major instances is going to be where each one has their own unique culture or if they will eventually homogenize.

Only real concern here, although I didn't participate during the mastodon surge last year, I heard that defederation became a bit of an issue with how common there. Granted, I feel like the impact is probably less here with the fact that you are interacting with topics rather than people.

With how chaotic my hotbars are, I could never imagine playing on a gamepad. I'm sure that is probably a great accessibility feature though.

To be honest, I had such low expectations for the blackout, I'm actually surprised how much impact it did have. This was never going to be the reddit killer. There is a reason why the 1% principle exists. Most people don't care, and most people who do aren't going to actually put in the effort to change their browsing habits. It's part of why being an early member of new sites like these are the best, because the people joining are the people who are actively seeking out new communities.

Yup, exactly. Welcome to the fediverse!

There is traction, and in fact already a fix in review.

Ah interesting. I actually see this post over there so it seems replies from kbin are actually federating now. The question is if I will see my own comment.

Edit: I do! Great news

They aren't saying to go to their instance, they are saying to go to a different thread. This is a federated thread from beehaw. This is the thread that they are mentioning, accesible from kbin: https://kbin.social/m/[email protected]/t/16497/Megathread-for-Reddit-Blackouts-and-News-Day-3#comments

The curious thing though is that they locked the thread, but we are still posting here. I'm wondering if that is a symptom of the current federation issues or if thread locking isn't a feature that kbin can replicate yet

Ironically, still some issues with the federation, so we can see them but they can't see us. We're in the walls.

Ernest might have also gotten up more servers to handle the load, noticing that cloudflare is off and we are federating again (this is a beehaw thread)

https://codeberg.org/Kbin/kbin-core/issues/173

Existing issue on the topic. If anybody is looking to contribute, this would make a great first issue to pick up.

https://codeberg.org/Kbin/kbin-core/issues/83

Popped an issue in the issue tracker for it. I think it should be default to be hidden, especially with the fact that most people coming from reddit would expect the same.

Ohh, I like zines as a shortened version

The true fear is when everything passes locally and then suddenly fails on the CICD pipeline.