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

[–] matcha_addict@lemy.lol 2 points 3 days ago

You can only filter and sort what was downloaded by the client. So that runs into resource constraints.

There shouldn't be resource constraint issues in downloading new content Metadata from all your subscriptions

tags

When I say "standardize tags on all content", what I mean is make it a standard to have the option of having tags on every type of content, and treat tags as a first class attribute of the content. The XKCD you reference is not relevant.

That's more the ATproto/Bluesky vision.

Sure, they use it. But it is compatible with activityPub as well.