No Stupid Questions

Of course, every instance has the right to preserve their own echo chamber. That is not a problem, but it could be later when users keep seeing communities from one instance go away and come back, or users get effectively "banned" from interacting with those communities because they signed up on the wrong instance. Even if they refederate, they'll be seen as unreliable by everyone else.

Its like banning all people who drive a Toyota from parking in your parking lot because some people you don't like drive a Toyota. Sure, you have the right to do that, but you will be losing out on the parking fare of those big communities of Toyota drivers, and even people who dont drive Toyotas but see you banning them. Then you get less traffic, less users, people leave, and it becomes a parking lot that is 98% empty.

This leads to hyper segmented communities, which have benefits, but normies don't really like when a place only has 3 active users.

UI will probably be fixed over time. Third party clients will arrive soon (some are already in early releases, such as Thunder: https://github.com/hjiangsu/thunder/issues)

Kbin has potential, I even tried to sign up for kbin but registration was disabled. So I just signed up to lemmy.world instead. Unless kbin is reopened for registration, I foresee many others doing exactly the same thing.

It was also the biggest instance, and if you're not too familiar with how the Fediverse stuff works, it's a no-brainer to sign up to them, just in case you ended up stuck on there. You'd still have stuff to look at, compared to smaller instances like startrek.website, which might only have three communities.

Exactly, the easy access and low barrier of entry (like reddit, twitter, etc.) make it perfect to populate. That's kind of why some of the instances need signups right, to keep out the riff riff?

Not sure about that. Even if .ml was open to new signups, there are quite a few reasons people would pick .world over it:

1. .ml goes down more often than .world
2. .world allows non-nudity NSFW content, while .ml does not allow any NSFW content
3. A lot of people have concerns about "tankie" ownership of .ml (whether that's true or not), while the owners of .world seem more politically neutral

I got in before signups were closed, and have accounts on both .ml and .world, but have abandoned my .ml account for the above reasons

I absolutely couldn't imagine it at all.

Loved your performance in Suicide Squad, particularly the bit where you said it was Squad'in time and Squaded on the Joker

Take my username from my cold dead hands!

Beehaw.org defederated from lemmy.world, and sh.itjust.works, effectively disconnecting from them. According to the post they made, they were disconnecting due to the influx of new users on both those instances overwhelming the moderation tools and moderation team that they had going.

It's worth noting that Beehaw describes itself as a safe-space instance, where registration is restricted, and all users registering have to be approved by instance operators. This is fine and all, but there's an issue. See, with the way that Lemmy and Federation works, you don't have to be a registered user on an instance to post there. So a user can just circumvent Beehaw's account creation restrictions by creating an account on a less-restrictive instance (such as lemmy.world), and posting over there. Which isn't ideal for Beehaw's moderators and operators, who had trouble dealing with "bad actors" from those instances (trolls and things), simply because their open registration policy meant that there would be be an influx of new users who found Beehaw's community through lemmy.world, or sh.itjust.works, or trolls who could comment on Beehaw's posts through them, circumventing bans and things.

Since it was too much for them to deal with, using the current tools that they had available to them, Beehaw defederated themselves from those two instances, effectively separating themselves from those two. Beehaw users won't see new posts from those instances, and those users wouldn't be able to see any new posts from Beehaw.

Given the current state of things, I wouldn't be surprised if Kbin might also be on the chopping block, since they've been having a few problems with users from there too, but that's neither here nor there.

Still, the Beehaw operators have said that they're willing to reconnect with those instances once Lemmy develops better moderation tools that let them manage that amount of users (and they're in contact with the operators for those two instances), but we have no real idea when that might be.

They were like, beeNAH, and defederated.

https://beehaw.org/post/567170

They wanted to keep things personal and civil so they closed the gates.

Running the same protocol, it's a bit different, but can be interacted with from other fediverse platforms.

@ghostalmedia

AFAIK CDN's don't do much to help with logged in traffic. Only users who are not logged in. Kbin.social is on Fastly infrastructure, so it's likely to scale comparatively well.

It's probably not desirable for it to get too big, but it should be able to absorb waves of Redditors who will then move on to other instances hopefully.

@AskThinkingTim @WhatThaFudge