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.

My suspicion is kbin is not actually listing every possible community either, just the ones it knows about through the same sort of indexing, where Lemmy does not have an interface to view all of the known communities by instance. This hampers discovery a bit, but also avoids confusion as there may be additional communities available that don’t show up in that list if someone else on your instance hasn’t subscribed to it.

Kbin is heavily centralized right now, so the main instance does know about a ton of stuff.

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.