this post was submitted on 11 Jun 2023
1 points (100.0% liked)

/kbin meta

639 readers
1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago
1
What would happen if kbin's admin (ernest), or any other admin of a server( by that I mean Mastodon, Lemmy, not an instance of kbin) one day decided he's going to pull a spez? (kbin.social)
submitted 1 year ago by [email protected] to c/[email protected]
7 comments fedilink hide all child comments
 

For kbin in particular, what would happen to an instance's Magazines(subreddits), the communities would just go poof?

I'm a rat who left the sinking ship that is reddit and I want to better understand how the whole fediverse thing works. I get that "everyone can host their own instances and access the federated fediverse servers/instances", but if a particular large one has gained traction and would one day implode, is there any way to prevent/mitigate it?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 0 points 1 year ago (1 children)

I remember reading a similar question regarding mastodon and the answer was that the code is open source, every instance, server, community can download a copy of it and customize their experience. The Kbin admin or anyone else does not own all the servers that host the vast number of instances. So even if they were to sell the already open source code, or threaten to pull the plug on the project, the code is available for everyone to just continue like nothing happened, and for the community to take over and develop it how they see fit.

[โ€“] [email protected] 1 points 1 year ago

Yes, the code for Kbin, Mastodon, Lemmy, etc. is open source, so anyone can spin up a new instance if they want. However, spinning up a new instance of Kbin would not save the content of any other instance if it were to go down.

If kbin.social shuts down tomorrow, then all the communities and user accounts that are hosted there are gone too. Kbin would still exist because there are other instances, but nothing @kbin.social would exist, if that makes sense.