• 0 Posts
  • 7 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle
  • For me, the bigger problem with how Lemmy is federated is the way comments and posts have unique IDs for every instance. You can’t easily find a comment or post from one instance on any other instance. With users, you just have /user/username@instance, what we need is /post/###@instance or /comment/###@instance. Instead, we just have /post/### and the ### is different everywhere (I think it’s just sequential for every post/comment the instance federates).

    Maybe there’s some reason they did it this way, but it feels like the better solution is to have the original host instance decide the number, then every other instance just use their number and their @instance.

    Pretty sure that was on the bug list 2 years ago.




  • To be fair, lemm.ee didn’t really act as host to any major communities to begin with. So communities aren’t really the loss here, and it could be that having at least a few big active communities on an instance is a key part of maintaining its long term viability.

    Also, all the text posts and comments from lemm.ee will still remain on other instances. I’m sure the instance could also back up content, if the specific admin so desired to re-host.




  • I think there’s a lot of development going on with the lemmy UI, for example the lemm.ee developer has next.lemm.ee for his new UI design beta. I’m looking out for a golden age of lemmy UI development where everyone’s copying each other’s functionality and they all continually improve until it ends up being about whichever interface personally prefer, like we had with 3rd party reddit apps.

    To be clear to others, though, PieFed is itself its own lemmy instance first, but it’s open source so works as an example UI that could be implemented by any other instance. Every instance of lemmy is potentially different, not just in which version of lemmy code they use but any number of modifications the instance admin may choose to apply.