Troy Whiteley
Troy Whiteley
Also started getting this too, maybe twitter made a change? logs: https://gist.github.com/dawnerd/74c234ee3b1b386bdfc45322485f24c6
With the api officially dead can we look at this again? I switched over to nitter rss and having this issue too but my nitter is behind an ip whitelist...
Looks like it's finally here https://tapbots.social/@paul/110109551743991074
We just saw our access revoked overnight :/
I switched to using rsshub, tried nitter but that was _very_ buggy. I think adopting the full graph endpoints would be the best path forward.
rsshub isn't perfect either, html ends up being embedded:
I have ~50 accounts in my config and run an pleroma-bot every 15 minutes against a nitter rss feed right now as a workaround. The guest accounts last for 30...
With these changes a lot of nitter instances have either turned off rss or asked people not to scrape them. I run my own so I'm not eating up guest...
looks like rsshub is dead for twitter feeds :\
Had similar (not using archives), try the version in #113 it helped reduce the timeouts for me