This is the main issue I see right now as well. I created my own instance for my account to live on, just so I know it will be there as long as I want it to. But that doesn’t do anything for communities I’m subscribed to that could, potentially, be on an instance that later goes down.
I think communities of similar topics are going to need to coordinate in the long run, and perhaps run their own instance to house their communities. This way the folks running the community and the folks hosting it are one in the same. You’d have instances that mainly house users, and perhaps a community or two. That’s where most folks would have their main account. Then you’d have instances that mainly house content, with few users besides the moderation/admin team(s).
I am gonna be honest but instances going down and losing communities could have the same probability as Reddit shutting down Subreddits just because they feel like it.
I understand your concern, but I think it would first be wise to let some communities flourish and look how it holds up in the grand scheme of things.
I think what would help is the introduction of multisubreddit equivalent for lemmy and then allowing similar duplicate communities to have the option of linking up with each other so people can subscribe to public multisubreddit. So regardless of what instance a community is on if it’s like a technology community it’ll display all the technology community duplicates.
That is brilliant. A sort of sub-federation within the grander federated instances. Subfeds (you heard it here first!) could feed off of and into each other, so if one instance goes dark it’s community and content are not lost as they’ve been replicated across the Fediverse. Sort of a cross between multisubs and RAID.
How about extending the software so that communities replicate between sets of servers over time? That way, things are more robust even if one server goes down.
This is the main issue I see right now as well. I created my own instance for my account to live on, just so I know it will be there as long as I want it to. But that doesn’t do anything for communities I’m subscribed to that could, potentially, be on an instance that later goes down.
I think communities of similar topics are going to need to coordinate in the long run, and perhaps run their own instance to house their communities. This way the folks running the community and the folks hosting it are one in the same. You’d have instances that mainly house users, and perhaps a community or two. That’s where most folks would have their main account. Then you’d have instances that mainly house content, with few users besides the moderation/admin team(s).
I am gonna be honest but instances going down and losing communities could have the same probability as Reddit shutting down Subreddits just because they feel like it.
I understand your concern, but I think it would first be wise to let some communities flourish and look how it holds up in the grand scheme of things.
I think what would help is the introduction of multisubreddit equivalent for lemmy and then allowing similar duplicate communities to have the option of linking up with each other so people can subscribe to public multisubreddit. So regardless of what instance a community is on if it’s like a technology community it’ll display all the technology community duplicates.
That is brilliant. A sort of sub-federation within the grander federated instances. Subfeds (you heard it here first!) could feed off of and into each other, so if one instance goes dark it’s community and content are not lost as they’ve been replicated across the Fediverse. Sort of a cross between multisubs and RAID.
Dude what a great idea I hope that’s on a roadmap
How about extending the software so that communities replicate between sets of servers over time? That way, things are more robust even if one server goes down.