JohannesOliver

It’s either this or we go outside, but the sun is out there. And people.

There are likely more communities available on an instance that kbin does not know about. I think that list is limited to what kbin has indexed and cached based on user activity. The downside to such a list is that a user may think it is exhaustive.

For a while vendors tried to lock down the BIOS pretty hard. Dell might still, I remember having to call and get assistance when a password was forgotten and they had to generate a backdoor key of some sort. Maybe that is less of a thing now that Bitlocker is widely used on corporate laptops and it is sensitive to tampering.

I don’t think I’m the only person who won’t reply to an email until there is something actually productive to say.

In the past they had jumpers for the same purpose.

What fediverse services are set up that way? For most projects, the flagship instance is by far the largest. For Mastodon it is something like 900k difference between the next most popular instance.

That’s why the government makes sure they can garnish you wages and even social security.

It’s unfortunate if the sh.itjust.works folks aren’t speaking, their listed rules seem pretty reasonable and the problem users appear to be breaking the rules of that instance too.

Communities have moderators too.

kbin paused federation while they dealt with the server/network issues, but was federated before that.

Who is “they”? The users, or the communities? Beehaw creates the communities, that’s why there are relatively few, so I don’t see that Beehaw communities would have much reason to move anyway. Beehaw has no create community button.

Yeah I think it is. If you go to settings you can change the default (under “Type”).