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!

you are viewing a single comment's thread
view the rest of the comments

[–] muntedcrocodile@hilariouschaos.com 3 points 5 days ago (1 children)

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.lol 2 points 4 days ago (2 children)

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.

[–] rglullis@communick.news 2 points 4 days ago

but it does require responsibility from the user to maintain their keys

Not necessarily? We can have did methods that do not rely on key ownership.

[–] muntedcrocodile@hilariouschaos.com 1 points 4 days ago (1 children)

So did has different providers so atproto uses did:plc and did:web but their are many different options and its a standard so u can get comparability with so many things ie did:pgp, did:eth, and like a million other options

[–] silverpill@mitra.social 2 points 4 days ago

DID-based identity already exists in Fediverse: https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md

We currently use did:key but in theory any DID method can be used, someone even tried to use did:plc: https://github.com/bluesky-social/atproto/pull/3943