Post ASBnkdJROPmTK6e8Su by apparentlymart@mastodon.online
 (DIR) More posts by apparentlymart@mastodon.online
 (DIR) Post #ASADST7YktY6zhAUsq by gabriel@mk.gabe.rocks
       2023-01-30T08:59:30.694Z
       
       0 likes, 0 repeats
       
       What's considered best practice for #RSS?1. Minimal content (such as a description) but include all entries?2. Entire content but only include the latest N entries.3. All content, on all entries?For some reason I'm biased against 2.
       
 (DIR) Post #ASAFn6nR9W57kGj3aa by mro@digitalcourage.social
       2023-01-30T09:06:35Z
       
       1 likes, 0 repeats
       
       @gabriel I do paged #atom feeds https://www.rfc-editor.org/info/rfc5005 in https://l.mro.name and will so in https://seppo.social.
       
 (DIR) Post #ASAFs2xcqC3FITqVxA by gabriel@mk.gabe.rocks
       2023-01-30T09:26:32.778Z
       
       0 likes, 0 repeats
       
       @mro@digitalcourage.social Fascinating! #TIL!
       
 (DIR) Post #ASAUxtP6mfgyhuwkGO by Ikel@mstdn.starnix.network
       2023-01-30T12:08:00Z
       
       0 likes, 0 repeats
       
       @gabriel Care to explain me ?
       
 (DIR) Post #ASAUxtvMqjUqJy2VXs by gabriel@mk.gabe.rocks
       2023-01-30T12:15:39.575Z
       
       1 likes, 0 repeats
       
       @Ikel@mstdn.starnix.network An RSS feed can include every post ever made or just N recent ones.As well I can just include the description or embed the whole article in the feed, which means the whole post can be read directly from the reader.The downside of this is that suddenly instead if your RSS feed pulling a few KB to fetch the latest articles if you throw them all in at once (nobody misses the old ones) it can grow larger and larger. For anyone who uses a reader for many sites I assume they'd prefer either small complete updates or a complete list with only descriptions and the link.I prefer completeness all else being equal.
       
 (DIR) Post #ASBcr4Hmv87nDmjtIG by mathew@universeodon.com
       2023-01-31T01:18:15Z
       
       1 likes, 0 repeats
       
       @gabriel 4. Use Atom, because RSS doesn't have a proper place to put the actual content, whereas Atom has a content element with associated data type information as well as a summary element, so people can (at least in theory) choose for themselves whether they want the full content or not.
       
 (DIR) Post #ASBd0lyRrILvK8JwjA by jbond@mastodon.social
       2023-01-30T22:58:42Z
       
       1 likes, 0 repeats
       
       @gabriel I'm in favour of 2. - Readers typically cache entries from feeds they follow. So you don't need to provide all entries. Convention is to limit by time or number depending on frequency of posting.- Provide all or some of title, abstract, full content. Usually, title+full content is the best answer assuming both exist. Otherwise you're forcing the reader to click through.
       
 (DIR) Post #ASBd4fQS9Ax4AmHDKy by vertigo@hackers.town
       2023-01-30T22:56:49Z
       
       1 likes, 0 repeats
       
       @gabriel I am personally biased towards option 1.  I think having the same code that generates a blog's index and its RSS makes a lot of sense, as they basically serve nearly identical purposes.If I may add an additional, fourth possibility, you can also implement minimal content (abstract only) and finite number of entries.I implemented that approach on my blog engine a decade ago; however, I received many complaints about that approach.  (This is just one of many things I'll be fixing in days to come.)So, for the purposes of documentation, I thought I'd include that option here, along with the warning that if used, you might get some negative feedback.
       
 (DIR) Post #ASBd6ZkkD1IR9sg5Lc by ajroach42@retro.social
       2023-01-30T22:56:17Z
       
       1 likes, 0 repeats
       
       @gabriel I would call 3 best practice, but it can get unwieldy. I am strongly biased against minimal content/descriptions or latest N entries because they both kind of break the thing that makes RSS great. 2 is forgivable in the event that you're dealing with a multi-MB full feed, but if it's not exposed programmatically *at all* I'm usually disappointed.
       
 (DIR) Post #ASBnkccXxtTBB4Zsbg by teleclimber@social.tchncs.de
       2023-01-30T23:26:14Z
       
       0 likes, 0 repeats
       
       @gabriel I don't know but I guess you just made me realize RSS doesn't support paging? 🤨
       
 (DIR) Post #ASBnkdJROPmTK6e8Su by apparentlymart@mastodon.online
       2023-01-31T01:42:09Z
       
       1 likes, 0 repeats
       
       @teleclimber @gabriel It's not for want of trying! Many times there have been proposals for things resembling "pagination" for feeds, including an IETF Standards-Track RFC: https://www.rfc-editor.org/rfc/rfc5005.htmlThe problem is that implementations rarely support them. 😖
       
 (DIR) Post #ASDIDTVm6TUx6g2oZk by david@social.thecrow.uk
       2023-01-31T20:04:22.978578Z
       
       1 likes, 0 repeats
       
       @gabriel Full content on everything.
       
 (DIR) Post #ASNOUqNLt6VLGBE2Wu by awoodsnet@phpc.social
       2023-02-05T17:33:36Z
       
       1 likes, 0 repeats
       
       @gabriel Option 2 is perfectly fine if you’re very prolific. 15 < N < 30 is a good place to start IMhOThe best is Option 3 - Include all content for all entries. Let people read the article in the RSS Reader. Include links to your site content and let *that* pull people into your website.  Don’t think you’re going to “drive the user to your site” by using an excerpt and a read more link. The opposite will likely happen and they’ll unsubscribe from your RSS feed.
       
 (DIR) Post #ASNOeY3eqaRtLQdoPY by gabriel@mk.gabe.rocks
       2023-02-05T17:36:10.971Z
       
       0 likes, 0 repeats
       
       @awoodsnet@phpc.social Thank you!