jae

i am actually probably going to deprecate the RSS feed (Atom and JSON feed unaffected) because it TURNS OUT RSS's <author /> field only accepts an email address, something i had missed while implementing it, which means that shares render completely incorrectly in all readers.

side note why the fuck is RSS like this

#cohost meta #devlog

jae @jkap12/19/2022, 9:12 PM

the change to deprecate RSS 2.0 specifically has gone live. this just means we removed the autodiscovery link for it; existing subscriptions will still work fine.

i also did the stupid hack a few people suggested of making up an email address to put in the author field. i hate it. hopefully it works correctly.

#cohost meta #devlog

You must log in to comment.

in reply to @jkap's post:

eblu @eblu12/19/2022, 7:19 PM

that's awful. is there no workaround?

jae @jkap12/19/2022, 7:20 PM

not really! the general answer for "how do you handle author fields for UGC in standard RSS" seems to be "you don't"

iliana @iliana12/19/2022, 7:20 PM

atom is just so much nicer

graham @graham12/19/2022, 7:20 PM

Can you use "rss+[page name]@cohost.org" or something so you can still have an email without having to expose the user's email and while still indicating who published it?