I’d really like to see some client-API consolidation. A common client API that could efficiently handle both “microblog” style and threaded discussions (lemmy etc) and leave the door open for other discussion formats too. This would allow for clients/frontends to flourish even more and backends could compete on features and efficiency. The backend specific features could be expressed through an extension mechanism of the common API.
I feel like something like that would need to be discussed at the standards level; a common API spec could maybe be issued as an extension of the current ActivityPub standard. Call it “CommonSocial”, or something.
I’d really like to see some client-API consolidation. A common client API that could efficiently handle both “microblog” style and threaded discussions (lemmy etc) and leave the door open for other discussion formats too. This would allow for clients/frontends to flourish even more and backends could compete on features and efficiency. The backend specific features could be expressed through an extension mechanism of the common API.
I feel like something like that would need to be discussed at the standards level; a common API spec could maybe be issued as an extension of the current ActivityPub standard. Call it “CommonSocial”, or something.