Kotaku is one of the feeds I follow and, honestly, the website is nearly unusable. You know the kind: video ad on top, banner ad on the bottom, teeny-tiny close buttons on the ads that require laser precision to close, only 40% of the screen readable, constant lazy loading of more ads in the content that lose your place by jumping the scroll around… Truly awful.
Full text feeds would make the content bearable. (Alas not available for Kotaku.)
i like full text way more but the TelemetryDeck blog has so many custom elements that I can’t translate into pure text, so the feed is just the first paragraph and a „read more“ link.
@silverwizard (Basically I'd like to ask your question again about podcasts, which I am today writing a paper on the (in)efficiency of feed handling for!)
I am way more likely to not bother reading something, if it forces me to exit the comfortable feed reader environment. I use miniflux, and I just don't like to leave that interface.
@silverwizard I feel far more confident with getting accessibility (a11y) right in a full spec-conformant browser than whatever each RSS reader is. (I put a fair amount of effort into a11y, though don't know if I am doing it right or not!)
Profesor de Ciencia de Datos en la Escuela Superior de Administración Pública. He trabajado en investigación en mecánica estadística de fracturas, método numéricos en dinámica de fluidos complejos y educación matemática.
@gabriel not all Hugo blogs have full text RSS though - the theme I use only does a snippet. Although the same theme has actually been updated now and does do full text feeds, given I have e.g. added some image galleries driven by JavaScript, I haven’t looked at merging that back in, as I’m just more confident of what people will see if they go to a browser.
@DamonHD @silverwizard Show notes and chapters and such are fully supported by many podcast apps, so I'd want them in the RSS feed. Not AI-generated ones though. One podcast I follow uses (slightly edited) auto-chapters and they are complete garbage.
It's unfortunate that RSS doesn't seem to provide a way to specify both a full version and a summarized version. Clients can do something like show only the first paragraph (giving users control over whether they want to read full posts or just a bit), which seems like the best of both worlds, but it means that authors can't control the summary. A hybrid approach might be for clients to fetch OpenGraph data from the source link itself as a summary.
I was a little bit surprised at how many prefer to get what I consider an incomplete body (in my use case for blog subscription). But there are different use cases.
Also a reason why a short summary may be preferred: Some blogs include so much unnecessary HTML in the description field, with "related content" and stuff like that. In that case I'd prefer a short text summary or cut-off first paragraph to let me decide whether I want to load the full page.
I would love it if the standard allowed for a link which clients could use to download the full text (and safe HTML), allowing you to keep it out of the feed to keep it small.
Aggregators could pre-fill the content if they wanted.
I’m all in favour of full-text but some feeds are gigantic, and crawlers are almost never polite (as rachelbythebay demonstrated recently).
it has always boggled me why most RSS feeds offer just a summary with a link to the "full version". Why can't they just have all the content in the RSS feed article?
If they're going to the length of offering RSS anyway, why not instead of just teasing those who obviously prefer RSS over other means, give them everything. It must be more effort to give just a summary than to have the content already made, available in the RSS also.
Tondoni
in reply to Neil Brown • • •Though I must say that has changed. In the early days of #rss I preferred fullfeed.
I'm not sure why it changed. The post has me thinking about that.
Daniel Fisher(lennybacon)
in reply to Neil Brown • • •Eric Kolb
in reply to Neil Brown • • •Kotaku is one of the feeds I follow and, honestly, the website is nearly unusable. You know the kind: video ad on top, banner ad on the bottom, teeny-tiny close buttons on the ads that require laser precision to close, only 40% of the screen readable, constant lazy loading of more ads in the content that lose your place by jumping the scroll around… Truly awful.
Full text feeds would make the content bearable. (Alas not available for Kotaku.)
Daniel 🏳️🌈 Jilg
Unknown parent • • •Eric Kolb
Unknown parent • • •InsertUser
in reply to Neil Brown • • •silverwizard
in reply to Neil Brown • •@Neil Brown I want to read in my reader, so full text
unless of course, it's a webcomic or something where the text isn't the purpose
DamonHD
in reply to silverwizard • • •gabriel
in reply to Neil Brown • • •DamonHD
Unknown parent • • •DamonHD
in reply to DamonHD • • •silverwizard
in reply to DamonHD • •DamonHD reshared this.
silverwizard
Unknown parent • •DamonHD reshared this.
liebach; ++ungood; // 🏳️🌈
in reply to Neil Brown • • •DamonHD
in reply to silverwizard • • •silverwizard
in reply to DamonHD • •DamonHD reshared this.
gabriel
Unknown parent • • •to add a feed to my website.
Context, I have a website using Hugo, which allows me to write in markdown; because I don't want to learn css Java or anything of that sort.
gabriel
Unknown parent • • •🤔
It may be the case.
Or maybe depends on the configuration.
This is my website:
gavox.srht.site/
Gabriel Villalobos Camargo
Gabriel Villalobos CamargoAMS
in reply to Neil Brown • • •Clare Hooley
Unknown parent • • •gabriel
Unknown parent • • •Qazm
in reply to DamonHD • • •Jonathan Yu
in reply to Neil Brown • • •It's unfortunate that RSS doesn't seem to provide a way to specify both a full version and a summarized version. Clients can do something like show only the first paragraph (giving users control over whether they want to read full posts or just a bit), which seems like the best of both worlds, but it means that authors can't control the summary. A hybrid approach might be for clients to fetch OpenGraph data from the source link itself as a summary.
rssboard.org/rss-specification…
RSS 2.0 Specification (Current)
www.rssboard.orgsteeph 🎆 ٩(˘◡˘)۶
in reply to Neil Brown • • •I was a little bit surprised at how many prefer to get what I consider an incomplete body (in my use case for blog subscription). But there are different use cases.
Also a reason why a short summary may be preferred: Some blogs include so much unnecessary HTML in the description field, with "related content" and stuff like that. In that case I'd prefer a short text summary or cut-off first paragraph to let me decide whether I want to load the full page.
samir, stack-based
in reply to Neil Brown • • •I would love it if the standard allowed for a link which clients could use to download the full text (and safe HTML), allowing you to keep it out of the feed to keep it small.
Aggregators could pre-fill the content if they wanted.
I’m all in favour of full-text but some feeds are gigantic, and crawlers are almost never polite (as rachelbythebay demonstrated recently).
Kevin Marks
in reply to Neil Brown • • •It also has a way to include HTML without guesswork
MeaTLoTioN
in reply to Neil Brown • • •it has always boggled me why most RSS feeds offer just a summary with a link to the "full version". Why can't they just have all the content in the RSS feed article?
If they're going to the length of offering RSS anyway, why not instead of just teasing those who obviously prefer RSS over other means, give them everything. It must be more effort to give just a summary than to have the content already made, available in the RSS also.