have the same atom:link and link tags (<atom:link href="https://nitter.catsarch.com/brooke2valley/rss" rel="self" type="application/rss+xml" /> and <link>https://nitter.catsarch.com/brooke2valley</link>).
I'd expect them to point to the same RSS feed and the corresponding web page respectively, instead of the user's normal list of tweets. For example, /brooke2valley/media/rss would have <atom:link href="https://nitter.catsarch.com/brooke2valley/media/rss" rel="self" type="application/rss+xml" /> and <link>https://nitter.catsarch.com/brooke2valley/media</link>.
Just a heads up #1137 is now being used on my instance so anyone looking at those URLs to see the bug should replace nitter.catsarch.com with another instance.
All these URLs:
have the same
atom:link
andlink
tags (<atom:link href="https://nitter.catsarch.com/brooke2valley/rss" rel="self" type="application/rss+xml" />
and<link>https://nitter.catsarch.com/brooke2valley</link>
).Additionally, the search RSS feed (for example, https://nitter.catsarch.com/search/rss?f=tweets&q=test) doesn't have query parameters for its
atom:link
andlink
tags.I'd expect them to point to the same RSS feed and the corresponding web page respectively, instead of the user's normal list of tweets. For example,
/brooke2valley/media/rss
would have<atom:link href="https://nitter.catsarch.com/brooke2valley/media/rss" rel="self" type="application/rss+xml" />
and<link>https://nitter.catsarch.com/brooke2valley/media</link>
.