Fediverse

28511 readers

415 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Posts must be on topic.
Be respectful of others.
Cite the sources used for graphs and other statistics.
Follow the general Lemmy.world rules.

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 2 years ago

MODERATORS

ruud@lemmy.world

Xylinna@lemmy.world

MrCenny@lemmy.world

TragicNotCute@lemmy.world

automodbeta@lemmy.world

woelkchen@lemmy.world

... (programming.dev)

submitted 1 year ago* (last edited 9 months ago) by CoderSupreme@programming.dev to c/fediverse@lemmy.world

9 comments fedilink hide all child comments

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

[–] donio@lemmy.world 5 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] drbluefall@toast.ooo 2 points 1 year ago

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.