JohannesOliver

In the long run they are hoping for more flexibility. I think it is incorrect that they are separating from “all the major instances” but they are separating from (two) servers with open account creation. I personally think an instance admin should be informed when their users are being banned from other instances, so they have the option to review behavior and consider if they would like to do the same. Sh.itjust.works at least has instance rules that should be compatible with most of what beehaw doesn’t like.

It doesn’t. Post or comment votes affect that post or comment.

You posted this to the main page of sh.itjust.works… https://sh.itjust.works/post/103999

IMO the kbin microblogging is pretty confusing, I wish they made it look more like Mastodon. Gonna have people accidentally creating posts in random communities.

They do want similar features that are available on mastodon, that essentially allow their users to interact with the outside world but the ability limit what comes in. It’s still a disingenuous take though, as it has nothing to do with image hosting, not allowing people to view their content, etc. They just don’t want assholes.

Mostly interface, some say it is more simple. It does both the aggregation and communities like Lemmy and microblogging. It also does some sort of microblogging related to the individual communities but I don’t really understand how that feature works.

Somebody could use it instead of lemmy or mastodon, but it also federates to them so nobody misses out.

It is federated, but its own thing.

It’s also low pagerank right now.

It was an issue in Mastodon originally too, but Mastodon added more flexibility to the platform and the nuke option wasn’t the only option.

They are the primary corporate sponsor for Wine and employ many of the developers. so… a lot.

That includes people it knows about from Federated servers.

For the real numbers you need to use their nodeinfo, for example: https://kbin.social/nodeinfo/2.0

Kbin has 30119 right now.