I like RSS as a standard because it is:
- well understood
- well supported
- extensible via namespaces
But it should be used for so much more than just blog posts and statuses – especially when paired with rssCloud for (virtually) instant updates.
Wikipedia defines RSS as:
a web feed that allows users and applications to access updates to websites in a standardized, computer-readable format.
It is this type of definition, however, that holds RSS back. Why does it just have to be updates to a website? RSS can be used to distribute all sorts of information. Once you start adding custom namespaces the possibilities are amazing.
There are way too many over-complicated protocols developed to do essentially the same things and the complexity excludes so many people. If we want true open communication and interoperability then things should be as simple as possible.
It's almost like people inventing new 'standards' are deliberately trying to make them hard so they can be the de facto gatekeepers of the new tech – all while decrying the web's current gatekeepers. If something is too hard for the average person to implement then they are forced to use an existing solution, often that created by those who designed the standard.
RSS may not be the answer to a lot of things, at least not in its basic form, but so much more could be achieved with a bit of lateral thinking and clever use of namespaces.
Some might think 'artcasting' is a bad use of RSS but is there really such thing as 'bad use' if it achieves its goal of getting information from one place to another in a simple, reliable manner that doesn't require a computer science degree to achieve?
Addenda A couple of clarifications:
- this post is about RSS as a standard and not as a byword for feed
- I am not getting involved in the RSS v Atom debate, my personal preference is RSS
- "over-complicated" protocols doesn't reference anything in particular but ActivityPub is a good example. Insert your own OCP here