In my opinion, there are two big things holding Lemmy back right now:
-
Lemmy needs DIDs.
No, not dissociative identity disorder, Decentralized Identities.
The problem is that signing up on one instance locks you to that instance. If the instance goes down, so does all of your data, history, settings, etc. Sure, you can create multiple accounts, but then it's up to you to create secure, unique passwords for each and manage syncing between them. Nobody will do this for more than two instances.
Without this, people will be less willing to sign up for instances that they perceive "might not make it", and flock for the biggest ones, thus removing the benefits of federation.
This is especially bad for moderators. Currently, external communities that exist locally on defederated instances cannot be moderated by the home-instance accounts. This isn't a problem of moderation tooling, but it can be (mostly*) solved by having a single identity that can be used on any instance.
*Banning the account could create the same issue.
-
Communities need to federate too.
Just as instances can share their posts in one page, communities should be able to federate with other, similar communities. This would help to solve the problem of fragmentation and better unify the instances.
Obviously there are plenty of bugs and QoL features that could dramatically improve the usage of Lemmy, but these two things are critical to unification across decentralized services.
What do you think?
EDIT: There's been a lot (much more than I expected) of good discussion here, so thank you all for providing your opinions.
It was pointed out that there are github issues #1 and #2 addressing these points already, so I wanted to put that in the main post.
https://static.xtremeownage.com/blog/2023/join-the-fediverse/
Not sure if it helps or not, but, I made that post earlier to assist onboarding a bit.
Nice. Thanks. I spent a good amount of time on a few links jsut mass adding communities of interest. Will just remove ones that don’t work out. No way to really organize or group them by topic though.
There is a github issue to allow communities to be federated-
Ie, this community can be hosted on multiple instances, for example.
That would help some too.
On a side note. Do you mind if i post your blog post in the sidebar on my instance (i already did, but can pull it down if you want, no one is looking at my site most likely)
Right now my instance isnt open. But given a possible surge coming on 7/1 I am chewing on opening it up to be a "user-only" federated instance. As in, no real communities, just a speed instance to setup an account and join other communities.
Not sure if im going to even do it, just thinking about it right now.
Feel free- Just do me a favor, if you come across some useful information we can share to others, please let me know and I will update it.
After reading some of the concerns from other various communities today, I ended up locking down my registrations to requiring both approval, and a valid email. I don't expect to get a ton of users, but, I wanted to reduce the chance of "Troll users" joining, and then giving my instance a bad name.... Or users posting content, which is not appropriate/illegal.
That is essentially what my instance is. The small handful of communities here, are either for my instance itself for me to share news, OR, communities related to some of my public projects.
Absolutely will. And thanks a bunch.
I'm having the same thoughts on registration. Require email at least to just...reduce throwaways and trolls. Mines application only because "closing" it is confusing as it just spins. And I may leave it to application only.
Same with NSFW content. I don't know of a good way to defederate some of those instances and track that. So i unchecked the box and tossed a disclaimer in. I really just don't want drama from my hosting provider. Just want a place people can login and go to some of the other instances that are more focused on curating content and communities. I just dont have time for that myself.
That is an easy fix! Just host behind cloudflare. Your ISP/Datacenter/etc can't see anything as the data is encrypted between lemmy <---> cloudflare.
I don't care if anyone posts NSFW content, AS LONG AS... its in a NSFW community and/or tagged NSFW. (AND, obviously not questionable/illegal)
Yeah. Strongly considering cloudflare for sure.
Would different parts of the community be hosted on different instances, thereby spreading out the burden? Or would the entire community be mirrored to each of the hosting instances, thereby providing backup security?
I've actually been wondering about that. For example, what if an instance with a popular community went down or defederated from everyone? Would all the content of that community be lost to everyone else? I'm guessing that under those circumstances one or more new communities would be started to replace the "lost" community, although things could get complicated if there were more than one trying to replace the original - or if the original community refederated after the replacement communities developed.
Absolutely. Multiple ways to address some of these issues. Hopeful for the future.