I’ve recently tried to use peertube and I think it could improve a lot if it showed all the content in all instances. But instead you have to look around many instances to try and find something you like. Then there’s other thing, it can’t suggest content if it doesn’t know what you like and without sharing the data between the instances it doesn’t know anything about anyone. If the user data was encrypted and shared between all sites, when you log in it could use the now decrypted user data to suggest content. Or maybe it can share the data with third parties, I don’t really know.
Personally, I feel like it makes more sense to just have each instance be its own server without hosting the other instances content and instead have the user identity/account able to access every single server that speaks the same protocol (something like OpenID to have a common user account across services). Then use standards so a common UI can be used client-side or for any particular server-to-server communication (much like how blogs can do backtracking between blog posts from different blogs and so, without them really having to federate). It would be more efficient while having the same end result but with a more free and open ecosystem, like the blogosphere used to be before it was shadowed by twitter & facebook.
To me, federation between private servers the way mastodon does it only makes sense for private communication like XMPP or Matrix… but the minute you are publicly posting content in the internet it makes no sense to have servers mirror the content from others just so people can access that content from one server in the next… if redundancy was the point then it would make more sense a P2P model, if a common UI/account was the point then separating those as independent servers would make more sense. The current structure binds each user account to one instance, the content being public forces the instances to list which other instances they allow, and this makes it so you might end up having to create multiple accounts in different servers if you wanted to access instances that do not want to federate, and at that point it’s not much different from centralized services. It restricts what instances the user can access (based on which instance they are registered with) and places extra responsibility and bandwidth/storage requirements on the instances themselves.
I think I would have better insight if I had the experience from running an instance myself. I may do that one day, but right now I don’t have the means. But I still have some thoughts.
I think the best thing would be to make it easier for instance managers to connect with other instances. maybe have tools that would allow this to happen automatically. So if you connect with lemmy.ml, you also connect with all of the instances on their allow list. I don’t know the details of how things currently work well enough to give a clear picture.
Second, hexbear needs to figure out how to merge federation changes. I heard they are working on this, which I am excited to hear. It’s currently the most active lemmy instance, but completely separate from the fediverse.
I also think it would be good to have data of people’s entry point into the fediverse. Do they start at join-lemmy.org? Some other instance list? For join-lemmy.org, I think it would help if lemmy.ml and other big instances were not at the top of the list and instead smaller instances were ranked based on some other metric. (Like invidious has this “health” metric. not sure how it works) There is no shortage of instances as I’ve seen a lot of new ones lately, which is really encouraging. So I think the focus should be making sure these smaller instances offer a good experience to users and people find them and join.
Also very important, Lemmy needs a feature like mastodon to migrate your account to another instance. So people on big instances could migrate to smaller ones.
A community dedicated to fediverse news and discussion.
Fediverse is a portmanteau of “federation” and “universe”. It is a common, informal name for a federation of social network servers whose main purpose is microblogging, the sharing of short, public messages.
Please do, even if it’s a very rough draft kind of an idea, I wanna hear.
Personally, I feel like it makes more sense to just have each instance be its own server without hosting the other instances content and instead have the user identity/account able to access every single server that speaks the same protocol (something like OpenID to have a common user account across services). Then use standards so a common UI can be used client-side or for any particular server-to-server communication (much like how blogs can do backtracking between blog posts from different blogs and so, without them really having to federate). It would be more efficient while having the same end result but with a more free and open ecosystem, like the blogosphere used to be before it was shadowed by twitter & facebook.
To me, federation between private servers the way mastodon does it only makes sense for private communication like XMPP or Matrix… but the minute you are publicly posting content in the internet it makes no sense to have servers mirror the content from others just so people can access that content from one server in the next… if redundancy was the point then it would make more sense a P2P model, if a common UI/account was the point then separating those as independent servers would make more sense. The current structure binds each user account to one instance, the content being public forces the instances to list which other instances they allow, and this makes it so you might end up having to create multiple accounts in different servers if you wanted to access instances that do not want to federate, and at that point it’s not much different from centralized services. It restricts what instances the user can access (based on which instance they are registered with) and places extra responsibility and bandwidth/storage requirements on the instances themselves.
I think I would have better insight if I had the experience from running an instance myself. I may do that one day, but right now I don’t have the means. But I still have some thoughts.
I think the best thing would be to make it easier for instance managers to connect with other instances. maybe have tools that would allow this to happen automatically. So if you connect with lemmy.ml, you also connect with all of the instances on their allow list. I don’t know the details of how things currently work well enough to give a clear picture.
Second, hexbear needs to figure out how to merge federation changes. I heard they are working on this, which I am excited to hear. It’s currently the most active lemmy instance, but completely separate from the fediverse.
I also think it would be good to have data of people’s entry point into the fediverse. Do they start at join-lemmy.org? Some other instance list? For join-lemmy.org, I think it would help if lemmy.ml and other big instances were not at the top of the list and instead smaller instances were ranked based on some other metric. (Like invidious has this “health” metric. not sure how it works) There is no shortage of instances as I’ve seen a lot of new ones lately, which is really encouraging. So I think the focus should be making sure these smaller instances offer a good experience to users and people find them and join.
Also very important, Lemmy needs a feature like mastodon to migrate your account to another instance. So people on big instances could migrate to smaller ones.