• Skavau@piefed.social
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    10 days ago

    Maybe the instance model isn’t the right one for long term federated communities.

    The primary problem here is community mobility. If any community could be, with a few key presses, decoupled from an instance and essentially plopped onto another maintaining all of the posts, comments and subscribers - it wouldn’t matter as much at all. Piefed has community migration, and I assume that is ultimately the end-goal. It just needs all the major instances to read and recognise such moves.

    • jet@hackertalks.com
      link
      fedilink
      English
      arrow-up
      4
      ·
      10 days ago

      piefeed migration doesn’t save the old non-federated content, and doesn’t take over the old community name. It’s more like a community clone tool. But yeah, its a good start.

      • Skavau@piefed.social
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        10 days ago

        Yeah, it’s not where it should be. But I’m quite confident that such is the end-goal.

        Instances will always come and go in many cases.

    • Jeena@piefed.jeena.net
      link
      fedilink
      English
      arrow-up
      3
      ·
      9 days ago

      For all the whining Element gets when it comes to being buggy, etc. The matrix protocol has solved the room moving part very well. Any alias of the room has the same validity to be the main room because the content is being stored on all the servers where people joined the room and the room name is just that an alias and you can have many of them pointing to the same room.

      I understand it’s more difficult to do with the ActivityPub protocol, but something like that would solve this problem once and for all.