Shortly after Jun 2, 2023 · 10:35 PM UTC my twitter RSS feeds went dark.
Looks like /1.1/statuses/user_timeline.json is returning "Sorry, that page does not exist".
Yet Nitter continues to work, so they can't have cut off the access to these things entirely.
And until the website goes logged-in-access-only, there's always scrapers.
Can I be arsed to fix it? Or will the last tweet I read be Ian Dunt saying "This is spot on" about some Brexit thing?
Wednesday night is the earliest possible time I could try.
Maybe it's just Twitter's bug and they'll fix it by then?
Did anyone hear of any changes to the Twitter API this weekend?
One thing I won't be doing, is letting Twitter's algorithms decide what I see there or logging in or visiting the website or installing their app.
if I don't fix the RSS converter, I just stop reading it.
Already have the no-posting rule.
Wow, can you really no longer search twitter at all without logging in?
There's no search icon and search dot twitter dot com just redirects to the login flow.
If you have to log in to search twitter does that mean it's part of the deep web now, the inaccessible dark-net of private networks?
Like Facebook already is.
@pre Still looks like it has a search feature...
@pre https://twitter.com/search?q=This%20quote%20that%20Elon%20Musk%20retweeted%20is%20not%20actually%20from%20Voltaire%2C%20it%27s%20from%20neo-Nazi%20and%20white%20supremacist%20Kevin%20Strom.&src=typeahead_click
@denny Are you you logged in?
I am never logging in there again, and I just get redirected to login page.
The preview on this mastodon page says "Log in to twitter" as the title of the page.
@pre Yeah, I am.
@denny Are there any recent mentions of /user_timeline.json and changes to the API?
@pre Because he's always been so good about advance notice?
@denny I was just intending to check if anyone else also had their robots break this weekend, or if it's just me.
If it's just me it might be network issues or broken caches on my end or something.
But if everyone else's robots broke too then I'm looking for a work-around not a fix.
@pre Searching for timeline.json got no relevant results, but also looked like it wasn't temporally sorted, so