rss format difference with nitter rss results
Closed this issue · 3 comments
rss from nitter:
<title>The Exp 68 crew started the new week investigating astrobiology and keeping up with cargo operations and equipment maintenance. https://go.nasa.gov/3n9KoOA</title> dc:creator@Space_Station The Exp 68 crew started the new week investigating astrobiology and keeping up with cargo operations and equipment maintenance. [go.nasa.gov/3n9KoOA](https://go.nasa.gov/3n9KoOA)]]>
Mon, 20 Mar 2023 22:02:01 GMT
https://twitter.com/Space_Station/status/1637937566308528128#m
https://twitter.com/Space_Station/status/1637937566308528128#m
rss from nitter-rss-proxy
The Exp 68 crew started the new week investigating astrobiology and keeping up with cargo operations and equipment maintenance. content:encodedThe Exp 68 crew started the new week investigating astrobiology and keeping up with cargo operations and equipment maintenance. [go.nasa.gov/3n9KoOA](https://go.nasa.gov/3n9KoOA)
]]></content:encoded>
@Space_Station
https://twitter.com/Space_Station/status/1637937566308528128
Mon, 20 Mar 2023 22:02:01 +0000
There are many extra characters while rendering the results. I tried with all the 3, "atom", "json", "rss" and its not as same as nitter. Can we have the same results as nitter rss gives ?
This is what visible from nitter rss:
<?xml version="1.0" encoding="UTF-8"?> <rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
May be the version differs.
If you change this code:
Lines 177 to 180 in 233cf82
to this:
w.Write(b)
does it do what you want?
If so, I can add a flag to request this behavior.
If this is really what you want, I'm not sure why you're using this proxy instead of calling Nitter directly. If you describe your use case so I can understand what you're trying to do, I may be able to suggest better alternatives.
No response, so closing.