-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nitter RSS: Handle over-processed links and metadata #131
Comments
Example output: https://respublicae.eu/@EURLex/110603986431571007
(Also shows an |
And for usernames, https://respublicae.eu/@EURLex/110603985985909102 :
|
Also I'm not sure it's useful to prefix "RT by <current_user>" rather than just "RT", as in https://respublicae.eu/@EURLex/110603985605674224:
|
Some of the issues were already reported at #122 and fixed in the test version, will need to check again. |
The current state can be seen at https://respublicae.eu/@EURLex (using 1.1.1rc58). |
The
|
Should probably also drop the HTML markup in posts like https://kolektiva.social/@pyorapajahelsinki/111443408564161235 (but this is from a Telegram feed: https://rsshub.app/telegram/channel/pyorapaja ). |
This is no longer needed as I switched to FeedToMastodon. Thank you for the long service! |
Using the RSS import option with Nitter works quite well, but the resulting posts are hard to read because every hashtag
Also, the
nitter_base_url
isn't applied because the links to the original post go to the URL provided by the RSS feed rather than to the original.An example RSS feed from an instance running 2023.05.30-38985af is:
The text was updated successfully, but these errors were encountered: