Comment on How do you even post that much
HK65@sopuli.xyz 4 days agoI’m OOTL, what happened to Kbin?
This is one of the crazy parts of the Fediverse that I don’t understand yet.
I am aware of Kbin and was under the impression that it was very popular. I haven’t been there but how would I know when an instance disappears or where would I be able to find out where it’s been picked up later on?
The email analogy kinda works here.
- See: lemmy.world/c/13thFloor@kbin.social This is the copy of the kbin.social community “13th floor” that was made on lemmy.world to show people on lemmy.world. - Now look at: lemm.ee/c/13thFloor@kbin.social This is the copy of the same community, but made for the lemm.ee instance. You’ll note that it is missing a post that was made on July 6th. That’s because the July 6th post was made by a user on lemmy.world. Because kbin.social was down by then, the post didn’t “federate” from lemmy.world through kbin.social to lemm.ee. - See lemmy.world/c/synthwave@waveform.social for another example. waveform.social was an instance that died, but people were still posting to the lemmy.world copy, but only lemmy.world people were able to see those posts because they were not federating. So in comments we just decided to make any new posts to another community on a “living” instance, and we put a notice to that effect.
Interesting, the Lemmy World 13th floor link takes me to K-Bin because I’m using the Voyager app. Normally, it’s nice that the app handles those links this way, but it seems, in the case of instances which have died, where commenters want to link and show people new posts that have been happening, the Voyager feature is actually a shortcoming.
Forked to Mbin.
jqubed@lemmy.world 4 days ago
Kbin was a project from a solo developer who also ran the main instance but had his real life (health issues, IIRC) demand all his time in the past few months. He had to abandon the project and the instance. Since it was open source it got forked and is continuing under the new Mbin project.