💾 Archived View for rawtext.club › ~sloum › geminilist › 002589.gmi captured on 2020-10-31 at 14:38:44. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
Ranf Dev ranfdev at gmail.com
Mon Sep 7 18:55:30 BST 2020
- - - - - - - - - - - - - - - - - - -
These are in response to James' original proposal for a new feedformat, but in your responses both of you seem to propose anothernew one, in gemtext and CSV respectively.
Indeed in my previous email I made a poor choice of words.I will try to better explain my proposal here.
RSS, (and atom, json...) feeds are easily parsable by machines and arealready supported byfeed readers, but they aren't readable by gemini clients. Also they are
fairly verbose and Allow[s] for things like embedding images
Introducing a completely new feed format with its own new syntax would requirewriting more code to parse it, so I don't agree with that decision.
Considering the above, and taking Spacewalk(gemini://rawtext.club:1965/~sloum/spacewalk.gmi) as an example, I'm proposingto use a format that doesn't require writing any new code, so that itcan be displayed by alreadyavailable gemini clients.```=
link1 date1 title1Description1...=
link2 date2 title2Description2...```(ISO-8601 date).Indeed, it's a new format and has its quirks, but we don't need tochange anything touse it.Advanced clients can implement special features by taking advantageof this format: for example they can aggregate multiple feeds, or notify usersof new items.Older clients can still fallback and show the feed as nice simple gemtext.