I feel like communities are the bigger problem here. And not one that’s easily solved.
If users from multiple instances come together in communities, those communities are still centralized on a single server. So if something happens to that server, or if your instance defederates with it, the whole community goes with it.
The alternative would be to have tons of duplicate communities spread over many instances, but that’s a bad user experience.
I think it can continue even without the source server? Like, once I press the Reply button on this comment, it gets saved to my instance (lemmings.world) then it lets all the other instances know, including lemmy.world (where the community is hosted) and slrpnk.net where you are registered.
Now let’s say lemmy.world stops existing, my instance still would let all the other instances it federates with know, meaning you could read my reply on a community that basically no longer exists. Though I’m pretty sure there are downsides to that (like, what if all the mods were from lemmy.world? There’s no admin who can add a new mod).
meaning you could read my reply on a community that basically no longer exists
oh really? does it actually work this way? if lemmy.world dies, can all its communities continue to live on as long as there are lemmy instances out there federated and subscribed?
No. You would only ever be interacting with a snapshot-at-the-time-of-death of the community on your local instance only. It is the home instance of the community that federates all events, not the instance of the originating post/comment/vote/whathaveyou.
Ah, ok. So if lemmy.world dies, but [email protected] was federated to 2 different other instances, those instances wouldn’t be able to “talk to each other”? They’d just have snapshots that they could locally interact with, but never see anything else? So is the fate of the Lemmyverse a graveyard of communities from dead instances?
Wow, you’re right. We really need to bring back something like USENET, where newsgroups (their “communities”) weren’t tied to a specific server. We could almost just resurrect NNTP, although the handling of images (and binary data more generally) probably needs some tweaking.
I wonder about this as well – because communities are tied to a specific home instance, that instance going down affects that community, potentially killing it. Something more akin to hashtags/tags/labels wouldn’t be tied to an instance so they would be more robust, though you’d lose the moderation of a community and just have a firehose of posts/comments…
There needs to be a way for a person or group to essentially own a tag to enable moderation. It might be one of those rare problems for which a block chain is a good solution, because there would need to be a public ledger showing who is a moderator for a tag at any given moment.
I feel like communities are the bigger problem here. And not one that’s easily solved.
If users from multiple instances come together in communities, those communities are still centralized on a single server. So if something happens to that server, or if your instance defederates with it, the whole community goes with it.
The alternative would be to have tons of duplicate communities spread over many instances, but that’s a bad user experience.
I think it can continue even without the source server? Like, once I press the
Replybutton on this comment, it gets saved to my instance (lemmings.world) then it lets all the other instances know, includinglemmy.world(where the community is hosted) andslrpnk.netwhere you are registered.Now let’s say
lemmy.worldstops existing, my instance still would let all the other instances it federates with know, meaning you could read my reply on a community that basically no longer exists. Though I’m pretty sure there are downsides to that (like, what if all the mods were fromlemmy.world? There’s no admin who can add a new mod).At least that’s what I think it works like.
oh really? does it actually work this way? if lemmy.world dies, can all its communities continue to live on as long as there are lemmy instances out there federated and subscribed?
No. You would only ever be interacting with a snapshot-at-the-time-of-death of the community on your local instance only. It is the home instance of the community that federates all events, not the instance of the originating post/comment/vote/whathaveyou.
Ah, ok. So if lemmy.world dies, but [email protected] was federated to 2 different other instances, those instances wouldn’t be able to “talk to each other”? They’d just have snapshots that they could locally interact with, but never see anything else? So is the fate of the Lemmyverse a graveyard of communities from dead instances?
Pretty much. I wouldn’t pay much attention to that, though - the absolute majority of the internet that has ever existed is a graveyard.
Wow, you’re right. We really need to bring back something like USENET, where newsgroups (their “communities”) weren’t tied to a specific server. We could almost just resurrect NNTP, although the handling of images (and binary data more generally) probably needs some tweaking.
I wonder about this as well – because communities are tied to a specific home instance, that instance going down affects that community, potentially killing it. Something more akin to hashtags/tags/labels wouldn’t be tied to an instance so they would be more robust, though you’d lose the moderation of a community and just have a firehose of posts/comments…
Jesum Crow… Tags aren’t a new concept. Just group communities with a tag… is that incredibly complicated to implement or something?
There needs to be a way for a person or group to essentially own a tag to enable moderation. It might be one of those rare problems for which a block chain is a good solution, because there would need to be a public ledger showing who is a moderator for a tag at any given moment.
There is no need to own a tag, nor to tack blockchain into a problem to try and sell a solution. Ever.