19 lines
2.1 KiB
Markdown
19 lines
2.1 KiB
Markdown
|
+++
|
||
|
|
title = "thinkin bout dropping RSS (and some thoughts about jf2)"
|
||
|
|
summary = "there are a lot of versions of RSS and they all suck [...] most feed readers anyone cares about seem to accept Atom equally as well [...] tangentially, jf2 seems like a decent format as any, but one thing i find confusing is [...]"
|
||
|
|
date = 2024-10-18T09:32:00-05:00
|
||
|
|
source = "https://mastodon.social/@trwnh/113331744143221451"
|
||
|
|
+++
|
||
|
|
|
||
|
|
thinkin bout dropping RSS from my website's alternate output formats
|
||
|
|
|
||
|
|
- there are a lot of versions of RSS and they all suck (and none of them are even a Real Standard, there isn't even a consistent media type, it could be served as xml, rss+xml, or even rdf+xml???)
|
||
|
|
- most feed readers anyone cares about seem to accept Atom equally as well as RSS variants (so why bother with RSS at all? it's basically a legacy format)
|
||
|
|
|
||
|
|
so basically i'm looking at currently outputting atom, jsonfeed, jf2, as2?
|
||
|
|
|
||
|
|
i'm honestly not sure about outputting jf2 either, since you can just parse the html... but it would be an ahead-of-time optimization and it's basically "free" because i'm using a static generator (hugo specfically). so i don't have a reason to remove it, do i?
|
||
|
|
|
||
|
|
tangentially, jf2 seems like a decent format as any, but one thing i find confusing is that it seems to be linked-data-lite with the way that references work... which is actually pretty awkward because you can never tell when some property's value is a string literal or if it's a reference. and then the spec tells you that you SHOULD be fetching that data and parsing it from the authoritative origin anyway? so what's the point of including references if you're just encouraged to ignore them???
|
||
|
|
|
||
|
|
interestingly there is some attempt at jsonld compat with jf2, there's a context document at https://www.w3.org/ns/jf2 which you can implicitly inject into any jf2 document. which you can't easily identify because there is no jf2 media type btw, only jf2feed+json which is a restricted profile for feeds only. also the context document is wrong -- none of the properties which can be or are "references" are identified as such with type:id. so it's at best a "starting point" and nothing more.
|