3 ms·
I just came to this thread to say that indieweb considers RSS outdated and suggests hFeed/hEntry instead.
by aboardRat4 2y ago
I just came to this thread to say that indieweb considers RSS outdated and suggests hFeed/hEntry instead.
- sapphicsnail 2y agoThanks for showing me this. I had no idea it existed.
- benoliver999 2y agoI feel like this should be using data- attributes instead of classes? I'm not a frontend guy really but aren't classes more for styling
- BoingBoomTschak 2y agoWell, then it can go to hell, even if the idea isn't necessarily bad. Atom/RSS are fine formats that work with countless small clients, what about hFeed?
- aboardRat4 2y agoIn both cases you need an xml parser. Atom is very easily desynchronized with the main content, whereas hentry is in sync by construction.
- BoingBoomTschak 2y ago> In both cases you need an xml parser. If only that were true! XHTML is basically dead and HTML5 is the murderer. Something that leaves RSS/Atom intact. > Atom is very easily desynchronized with the main content, whereas hentry is in sync by construction. I know, and no need for XSLT magic to fix browsers having made RSS/Atom persona non grata. Still, "deprecating" RSS/Atom is completely wild, people should be happy to find blogs with usable feeds in the first place.
- aboardRat4 2y ago>XHTML is basically dead and HTML5 is the murderer Tell me more. https://html.spec.whatwg.org/dev/introduction.html#html-vs-xhtml https://html.spec.whatwg.org/dev/introduction.html#html-vs-x... Doesn't firefox ship a built-in translator between plainHTML and xHTML?
- Timwi 2y agoYou sound like we need to work out which technologies to allow or ban. A true Indie web would just let technologies exist side by side, see which ones get implemented by popular clients or which clients become popular due to their implementation, and let it all exist organically. That's how RSS happened in the first place.