Simple

We can bring that into RSS by treating any interaction as content. If you post something, thats an entry in your feed (as before). If you comment on something, thats also an entry in your feed. If you like something, thats another entry in your feed. If you follow someone (which would mean subscribing to some RSS feed), thats also another entry in your feed. To mark that interactive nature of some feed entry, we can simple extend RSS a bit

Interaction as Content [archive]

Tout est dans le simple 🙃.

Rédiger une spécification comme Media RSS n’est déjà pas trivial mais alors faire en sorte que cela soit adopté et devienne un standard c’est une autre paire de manches.

RSS originated in 1999, and has strived to be a simple, easy to understand format, with relatively modest goals. After it became a popular format, developers wanted to extend it using modules defined in namespaces, as specified by the W3C.

RSS 2.0 adds that capability, following a simple rule. A RSS feed may contain elements and attributes not described on this page, only if those elements and attributes are defined in a namespace.

RSS 2.0 Specification [archive]

Beaucoup de personnes ont envie de faire davantage avec RSS, c’est la diffusion à une échelle non anecdotique qui est difficile. Peut-être qu’un acteur comme Mastodon pourrait peser dans la balance d’une telle initiative.

Another feature area I would think about is interactivity. I’m fascinated with Google’s work in Gmail around “Inbox Actions” – basically the one-click buttons to perform an email action like RSVP, or reviewing a bug. Here’s an explainer with some examples.

Let’s call it Feed Actions. Feed Actions could also be an RSS extension.

Three requests for the Google Chrome team as they experiment with RSS [archive]

J’ai deux communautés dans lesquelles c’est même devenu un running gag de créer un outil qui explorerait de nouvelles possibilités.

Suivez-moi et vous n’aurez plus jamais faim ! Gniarkgniarkgniark 🦁⚡️