• MoogleMaestro@lemmy.zip
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 day ago

    While LOLA is great, I’d really love an established handshake mechanism for having two accounts on two bespoke services represent the same user.

    For example, I want to have a pixel fed and mastodon presence that can be authored between the two. However, you currently can’t make two accounts that are effectively linked to each other. I feel like this linking is important for further decentralizing the fediverse (by effectively decentralizing the user itself)

    • hector@lemmy.today
      link
      fedilink
      English
      arrow-up
      2
      ·
      15 hours ago

      I am unversed on all of this, but agree that interoperability between not only instances but also platforms like between lemmy and mastadon, and even a friend connection site to replace facebook, could help the fediverse grow to finally get a critical mass.

    • rako@tarte.nuage-libre.fr
      link
      fedilink
      Français
      arrow-up
      2
      ·
      1 day ago

      That’s because AP as it is implemented today is crap, it’s a superficial compatibility layer on top of a proprietary (as in, doing non-standardized stuff) platform. We need to take it on its head and make AP the actual core then build on top but that requires some work

        • rako@tarte.nuage-libre.fr
          link
          fedilink
          Français
          arrow-up
          1
          ·
          16 hours ago

          The mastodon api, or the lemmy api, or the xyz api. Eagh platform has its own. Being public doesn’t make it standard, hence the “proprietary” qualifier

          • julian@activitypub.space
            link
            fedilink
            arrow-up
            1
            ·
            16 hours ago

            Oh I see. Yes, AP first apps would be great, but getting older apps connected via AP is important too.

            NodeBB predates ActivityPub (or came around the same time), and so we added it recently. It works quite well with our existing code. Not much of a compatibility layer.