4 ms·
It was not XML previously. I will write a blog post soon explaining, but I wanted people to have a look first. I believe it's totally newsworthy, but of cours
by jacob_riis 16y ago
It was not XML previously.
I will write a blog post soon explaining, but I wanted people to have a look first.
I believe it's totally newsworthy, but of course YMMV.
- Groxx 16y agoThe blog post I'll probably end up reading if it makes it to the front page of HN. I don't often look at the new stuff (sorry, but it's true). But as-is? It's a 1-1 duplicate of the main page (though it does separate by source) in a different format, and a strange extra layer in the JSON: { updatedFeeds:{updatedFeed:[{feed item}]}, metadata:{} } Why updatedFeeds.updatedFeed[]? There's nothing else in updatedFeeds. edit: There's also the inconsistency that updatedFeeds.updatedFeed[x].item may be an array or an object, depending on how many items are by that source. Inconsistency == increased edge-case code == less happy users of the data. It seems a barely-thought-out representation of the data, nothing I'd want other people to see.