• kopper [they/them]@lemmy.blahaj.zoneEnglish
    3·
    7 days ago

    yeah no i seriously don’t see how that one actually helps anything. maybe for the odd self hoster it could make sense but realistically it’s way too under-defined (but then that’s the norm for ap, sadly)

    let’s say lemmy implemented it. ok. what now? my current account is still under lemmy.blahaj.zone. i still can’t move to some other instance without changing my account’s id and breaking all the existing object ids. i can move my posts between instances (or perhaps connect multiple instance software to the same actor, though a generic C2S server can in theory accomplish something of that sort without needing to alter other instances communicating with mine) but my identity is not any more portable than without it.

    actor relative ids requires everyone to anticipate being portable and set their account up with it from the very start. maybe the existing account migrations can be used to one-time migrate a non-portable account to a portable one, but you’re still required to host your own account on your own “identity instance” yourself, and you are more or less stuck on that identity instance if it ever goes down without you sending the same account move activity we already have out. it’s not as simple as taking an account from one instance and moving it to another.

    https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md is imo better at accomplishing the goal, and unlike relative URLs it has real existing implementations proving it’s viable in the first place. but it has it’s own downsides as well (severly limiting domain block effectiveness for authorized fetch enabled instances, no key rotation afaict, …)

    as a side note, don’t get too hyped up by feps. they have no power over anything and an existence of one does not mean anything for the future of the protocol. implementations are still the only ones making the final call on how the protocol actually functions (because real governance and “spec compliance” is anywhere between doesn’t exist and being actively hijacked by threads via swf), and the only implementation that actually matters in terms of protocol improvements is mastodon.

    • isoOPAEnglish
      1·
      7 days ago

      As I understand, it will make things work like Bluesky. Users will be able to use their own domain handles while not hosting an instance as a whole.

      • hendrik@palaver.p3x.deEnglish
        4·
        7 days ago

        I skimmed the first few pages. And it seems it’s just concerned with the content? You can store your notes (posts, file uploads, …) on arbitrary instances and move them around. But you still need a fixed instance that hosts your actor identity (your account) which then tells where to go to fetch a post. And that one can’t change. So your account and username would still be tied to a fixed domain handle. And you can’t move it. And even for the content, it seems like you’d need that fixed instance to do the 302 forward, so it needs to be contacted to resolve each location.

        Edit: But you might be right. I don’t grasp the full concept. Maybe it enables us to configure a webserver on our own domain to forward a user handle to some external server. Meaning we don’t have to install a server ourselves. And the servers would then be interchangable (if this translates to fetching everything). You’d still be tied to your domain name. But not to a service anymore. That’d be great.