http://sprout.rupy.se/feed?rss
http://sprout.rupy.se/feed?atom
Now that I look at them they are equally bad.
That said ActivityPub with JSON does not strike me as better.
Seriously considering getting into the fray...
http://sprout.rupy.se/feed?rss
http://sprout.rupy.se/feed?atom
Now that I look at them they are equally bad.
That said ActivityPub with JSON does not strike me as better.
Seriously considering getting into the fray...
• RSS 1.0 – the RDF/XML serialisation.
• JSON Feed
• h-feed/hAtom – embedding the “feed“ as Microformats markup inside the HTML.
• schema.org/Blog – embedding the “feed“ inside the HTML, either with RDFa or with JSON-LD or with Microdata.
• If you want to annoy the most people at once, there is a great solution: The data model from RSS 1.0 is of course RDF-based. The modern serialisation of RDF is JSON-LD – simply use the RSS 1.0 vocabulary in a “JSON-LD-Feed”.
May be worth making a jsonfeed while you're at it, if you just want to make more options.
JSON I use in my distributed DB (http://root.rupy.se), it's less verbose but XML to me is also a development tool that gains with human readability.
The bottleneck is almost never bandwidth on small solutions.
What I'm considering now is making my own ActivityPub, adding Reddit like features and Email.
I would like to make the format pipe (|) separated instead of XML/JSON...
The social protocol to end all social protocols. XD