You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RT EPWashingtonDC
🧵 1/2 Support to Ukraine, sanctions, security and stability, trade and technology and NATO enlargement were among topics discussed in the latest meeting of the Transatlantic Legislators' Dialogue led by @radeksikorski and @RepNateMoran. More details: https://europa.eu/!mRRgC9https://t.co/ADbqcF0nGt
Re -We agreed on the need for new elections. We discussed modalities & way ahead
-Arbitrary arrests or mistreatment of prisoners is unacceptable. @EULEXkosovo will play a more robust role in monitoring
The 3 policemen held in Serbia need to be released urgently & unconditionally https://t.co/8xXGUFVAtN
If the & is correctly escaped in the RSSHub XML, then maybe we need to parse the XML differently (with a different library which handles escaping automatically?).
That "Re " is also something added by RSSHub, suggesting replies aren't handled as such.
The text was updated successfully, but these errors were encountered:
Another improvement with RSSHub (and probably Nitter, too): when a single request get more than one tweet per user, the display order has to be inverted.
Currently the tweets are displayed from newest to oldest. Expected is from oldest to newest, especially for the threads.
Importing an RSSHub RSS feed works very well, but there are a few issues.
Quote tweets are posted with a literal div and a link to the original tweet (though rewritten if nitter_base_url is configured)
Example: https://respublicae.eu/@danutahuebner/110604120830026002
t.co links aren't always converted. Example: https://respublicae.eu/@danutahuebner/110604122030104574
Retweets use the display name instead of mentioning the
@username
, for example:https://respublicae.eu/@danutahuebner/110604122554679766
Retweets don't convert t.co links, for example:
https://respublicae.eu/@danutahuebner/110604122444876527
Escaped
&
are left lingering, like:If the
&
is correctly escaped in the RSSHub XML, then maybe we need to parse the XML differently (with a different library which handles escaping automatically?).That "Re " is also something added by RSSHub, suggesting replies aren't handled as such.
The text was updated successfully, but these errors were encountered: