I recently added support for JSON feed in my feed reader and blog. After playing with it for a while, I doubt it will be a wildly supported standard.
- It is really just RSS/Atom wrapped in JSON. Sure it changes a few names, makes some elements mandatory and other elements optional but overall it does not attempt to fix core problems (consistent item IDs to avoid reruns, embedding messy HTML with relative links...).
- Besides a dozen of JSON feeds mentioned in the documentation or in the Github repo, there are very few feeds published in the wild.
- Its authors seem to have kind of given up already, a lot of open issues and PRs but not much happening.
Don't get me wrong, I'd like a successor to come and fix the issues that RSS and Atom have but this successor would need much more traction than what JSON feed has.
- It is really just RSS/Atom wrapped in JSON. Sure it changes a few names, makes some elements mandatory and other elements optional but overall it does not attempt to fix core problems (consistent item IDs to avoid reruns, embedding messy HTML with relative links...).
- Besides a dozen of JSON feeds mentioned in the documentation or in the Github repo, there are very few feeds published in the wild.
- Its authors seem to have kind of given up already, a lot of open issues and PRs but not much happening.
Don't get me wrong, I'd like a successor to come and fix the issues that RSS and Atom have but this successor would need much more traction than what JSON feed has.