Generated RSS/Atom Feed parsing issues

[colinmahns]

Observed behavior:
Loading the atom and rss links in browser displayed an error that one of the feed sources had a malformed character:

Location: https://feed.dsausa.org/global/atom.xml
Line Number 509, Column 49:
    <id>https://www.dsausa.org/?post_type=blog&p=11440</id>
------------------------------------------------^```

Links:
https://feed.dsausa.org/global/rss20.xml
https://feed.dsausa.org/global/atom.xml

Expected behavior: 
RSS should load in browser and/or be downloaded locally as an .xml file. 

[colinmahns]

Looks to be related: feedreader/pluto#5 (comment)

[colinmahns]

@victoria-riley-barnett was able to fix this in #25 and #26. One line fix! Thank you so much.

Both feeds are now generating and displaying without this issue, going to close this out
https://feed.dsausa.org/global/atom.xml
https://feed.dsausa.org/global/rss20.xml

[ryantimjohn]

Hmm, still getting some errors on validation in Atom:
https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Ffeed.dsausa.org%2Fglobal%2Fatom.xml#l27

And some recommendations for RSS 2.0:
https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Ffeed.dsausa.org%2Fglobal%2Frss20.xml

Worth reopening @colinmahns?

[colinmahns]

On 8/29/23 08:35, Tim Ryan wrote: Hmm, still getting some errors on validation in Atom: https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Ffeed.dsausa.org%2Fglobal%2Fatom.xml#l27 <https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Ffeed.dsausa.org%2Fglobal%2Fatom.xml#l27> And some recommendations for RSS 2.0: https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Ffeed.dsausa.org%2Fglobal%2Frss20.xml <https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Ffeed.dsausa.org%2Fglobal%2Frss20.xml> Worth reopening @colinmahns <https://github.com/colinmahns>?

Not sure if this is something we can fix and will have to accept just since this is repackaging upstream feeds, but it's definitely worth looking in to. The warnings presented are all pulled from chapter feeds, things like no iframes in content fields aren't something I think we can or should dictate as requirements to chapter feeds. The recommendation for the atom feed to fix validation is also something that came from an article passed up to us looking at the recs on that page.