For example, for me, here are some things I wish to see (or would implement in my design) :

  • design around ease of self-hosting. A non technical user must be able to self host easily and at a very low cost.
  • Embrace content sorting and filtering algorithms, but on the client side, with optional control by the user.
  • Standardize tags on all content. So many of the different ways different platforms classify or organize content can be implemented as tags, which increases interoperability between them.
  • Abandon obsession with real-time-first implementations for use cases that don’t explicitly need it.
  • Transferable user identity (between instances)
  • User identity and authentication as separate service from social network instance

Would love to hear yours!

  • 🇦🇺𝕄𝕦𝕟𝕥𝕖𝕕𝕔𝕣𝕠𝕔𝕠𝕕𝕚𝕝𝕖@hilariouschaos.comEnglish
    3·
    11 days ago

    Unified identity really needs a modification at the core of activpub. The issue at the moment is that a user is just an actor and an actor is just a url. What it needs to be is something like a did(distributed identity) which is what atproto (bluesky uses) does. And the did points to a list of actors that can be across multiple servers. The did has a private, public key pair and signs all activities by per server actors as ur user. What this means is u don’t need to trust any server with login details or anything and u can do activities acting as any instance you want.

    • matcha_addict@lemy.lolOPEnglish
      1·
      11 days ago

      I do like this, but it does require responsibility from the user to maintain their keys. I think having it as an option is great, alongside the identity providers I speak about.