I noticed my feed on Lemmy was pretty dry today, even for Lemmy. Took me a while to realize lemmy.ml has been going up and down all morning, and isn’t federating new posts.
But, since this is all still federated, I can still create and read posts on other instances while I wait. Even this one! Any other service would just be unavailable completely right now.
I do miss the larger communities on lemmy.ml - asklemmy, memes, and I really wanted to watch the reddit fallout on /c/reddit. Maybe I’ll look around for some good replacements for those. Open to suggestions!
Yeah, I think it has a certain charm. However I fully agree, without it being addressed this will lead to issues and setbacks in the future trying to build communities. For now I’m subbing to all and trusting the process that creases will eventually iron themselves.
I think, kept this way, instances should be more clear what kind of ‘country’ they want to form. For example a group that has tech as the primary interest, should go about starting the instance as such, and setting ground rules for communities therein. Tech related, even if loosely, and differentiated from the masses. Or a better example would be, a European - English Instance could require a suffix like EU or UK like newsUK or photographyUK simply to attract the more locally relevant audiences.
A more involved solution could be to tag your community like Twitter into topics it wants to show up in feeds for (as well as tags that exclude it)… like ‘technews’ tagged in the ‘news’ and ‘technology’ but excluded from ‘politics’ and ‘finance’ and ‘onion’
Another one could be to allow communities to federate with one another. If a news community spots some large news audiences in other instances, the moderators for each community could federate with one another and create a supercommunity (like a multi on Reddit), allowing the super to operate on both instances but share hosting of something along those lines.
You could also have moderators agree to join forces by migrating one community over to the larger server and closing up shop. This may happen naturally with time.
We have to solve the content curation problem IMO. If we all love lemmy.world or sh.itjust.works and post 1000’s of hours of content to either and one of them just “shutters” the server then all that content is GONE. Or, am I missing something about how all this works?
If we want to “join” servers we need some type of content migration tool that allows the user to determine where their content is actually “hosted”.
We may see individual servers for heavy content creators as they’ll want some way to ensure that all of the federated servers can continue to access their content right?
Yeah good point actually. Independent servers is a strength but not future proof. Allowing larger servers to store back ups that other instances can link to in the event of down time, or allowing themselves to be absorbed if they shut down would keep the place running, there would just need to be a system in place where an instance can nominate another instance to hold a spare set of keys, so that duplicates don’t start fracturing the system.
It’s fractured by design. There are good things about being fractured. What we actually need is a “fractured” system with an aggregator to ensure the best user experience. You’ve heard of a system like this before: Cryptocurrencies are by nature ‘fractured’ but they use the term ‘decentralized’ and it’s what brings safety and security to digital assets. What we need is a “Coinbase” or a “Binance” who “aggregates” all of the “coins” so that a user can just go to the exchange and see ALL of the digital currencies without having to know each of their names and server addresses in advance.