So it finally happened. The #TwitterAPI access used to update #ResPublicae was cut off, all requests get an HTTP 401 response. Some discussion at
https://github.com/robertoszek/pleroma-bot/issues/120#issuecomment-1593688412
#ResPublicae mirrors are catching up on the recent posts, using RSS input for the ever-wonderful #PleromaBot.
We're only able to get the 20 most recent posts from #RSSHub, so any account which posted more than that in the past ~2 weeks will have some posts missing. Some posts also get a bit messed up in the data conversion, so please be patient. (Most issues are already reported upstream.)
Please send patches or donations at https://pleromabot.robertoszek.xyz/pleroma-bot/!
Our source is broken again, we'll reconsider the alternatives. (Such as self-hosting or switching to a Nitter source.)
Since 2023-08-10, our mirrors almost always failed.
We're now trying the #Nitter instance by the excellent @nolog as source. (Trying to avoid excess load.)
Please support them and the Nitter developers if you can:
https://nolog.cz/en/support/
https://liberapay.com/zedeus
"#Nitter is dead", proclaimed the maintainer after yet more #TwitterAPI changes.
https://github.com/zedeus/nitter/issues/1155#issuecomment-1913361757
Some instances managed to survive a bit longer but now we're suspending updates of #ResPublicae accounts. We'll reassess in a little while.
Crossposting for the busiest ~50 accounts using the privacydev Nitter instance has worked surprisingly well for a few months. (Help welcome to fix the RSS rendering issues which fail to preserve mentions and hashtags: https://github.com/robertoszek/pleroma-bot/issues/131 .)
A few days ago, crossposting stopped as media retrieval fails. We're now crossposting without media.
To reduce truncation errors, we caved and increased the character limit for posts to 2000 characters.