This is @Dave@lemmy.nz and @Dave@piefed.nz but PieFed told me not to use my admin account for general browsing so here I am following instructions.

  • 0 Posts
  • 31 Comments
Joined 23 days ago
cake
Cake day: September 2nd, 2026

help-circle








  • Have you got experience self hosting other things?

    I really think that it’s good to start with something small and personal (say, a wiki or Jellyfin) where you can build some skills around hosting, reverse proxies, security practices, backups, etc.

    Hosting a service as part of a wider interconnected network of sites isn’t as difficult as it sounds but there is definitely potential to screw it up beyond repair.


  • A few phones back I started getting a second hand flagdhip phone every 3-4 years, I think it’s well worth the flagship second hand 1 year old model instead of the mid range phones I used to get for the same price.

    Plus the last couple have been pixels for GraphineOS, so it’s nice to not be directly handingb Google money.



  • Summit here too. I changed up some of the display settings so it feels like Relay for Reddit 😀

    The things that got me to move from Voyager were that when images didn’t load first time, there was no way to re-try - Summit has that. And I don’t think Voyager handled drafts that well. Summit has drafts but I do wish there was a client that had drafts like Relay did, where if you come back to the same comment/post and hit reply it has your draft from where you left off on that comment/reply.








  • For 1, there’s no central authentication. Accounts prove themselves to other instances with a private/public key pair. I guess you could have some system where the old and new instance connect then transfer that private key so the new instance could prove it’s really you nkt someone impersonating you.

    For 2, we don’t even backfill communities when they sync to an instance for the first time because of the volume. For a while, Lemmy instances would freeze (for everyone) when a user with a lot of content deleted their account, but if you wanted to achieve this I’m sure you could do some slow, async, progressive loading of the content that might happen over days, so volume alone wouldn’t make this impossible. It would also have the potential for large storage requirements or a mismatch between what is allowed on different instances, e.g. you could create an instance, load it up with spam posts, then import it to a major instance to get thousands of views before they could ban you. So here you’d need some protection. Admin review from the new instance? Only allow import from trusted instances? What if someone faked dates or other metadata in their posts before the transfer?

    1. On Lemmy, a community owns the content. So an upvote or comment will get sent to the community’s instance then that instance will federate it to other instances. If one instance transfers a user, there needs to be a way for the owners of the user’s content to federate that update. For something like Mastodon people directly follow a user so their instance is the owner, but for Lemmy with communities you need the user to tell the community about the change then that community would need to trigger the update to it’s own content. You’d have hundreds of communities each triggering updates to hundreds of instances. I see a big risk here of a user being in two states, e.g. one community federated updates ok but another didn’t, and now some instance has two records of the same user. I’m sure smarter people could work out some redundancy here.

    I honestly do think this sounds achievable but like others have said, it’s a lot of work with a lot of edge cases to cater for. So it’s likely not a high priority.