Hey all, so I’ve been trying to embrace the fediverse life. My background - I’ve been on the internet since pre-WWW, so I’ve seen it all.
I think there’s a structural issue in the design of Lemmy, that’s still correctable now but won’t be if it gets much bigger. In short, I think we’re federating the wrong data.
For those of you who used USENET back in the early days, when your ISP maintained a local copy of it, I think you’ll pick up where I’m going with this fairly quickly. But I know there aren’t a ton of us graybeards so I’ll try to explain in detail.
As it’s currently implemented, the Fediverse allows for multiple identically named communities to exist. I believe this is a mistake. The fediverse should have one uniquely named community instance, and part of the atomic data exchanged through the federation should include the instance that “owns” the community and a list of moderators. Each member server of the Fediverse should maintain an identical list of communities, based on server federation. Just like USENET of yore.
This could also be the gateway into instance transference. If the instances are more in-sync, it will be easier to transfer either a user account or a community.
This would eliminate the largest pain point/learning curve that Lemmy has vs Reddit.
Open to thought. And I’ll admit this isn’t fully fleshed out, it was just something I was thinking about as I was driving home from work tonight
Lemmy is good, but it could be great.
Reading this just gave me an interesting idea, when you start to post a link that’s already been posted in another linked instance, it will start to show you that it’s been posted elsewhere to different communities in other instances (on Lemmy, I don’t know about Kbin). This clearly shows there’s functionality there to look around when posting links, so I wonder if similar could be implemented when creating communities.
If the interface told you ahead of time that the community you were about to create has already been created in other instances, you wouldn’t be prevented from going ahead & creating your own version, but you’d be more readily aware. Honestly a win-win approach imo, considering it would help you find a community you may have been looking for but didn’t think existed, and it doesn’t keep you from trying to make your own anyway.