0 sats \ 2 replies \ @cryptocoin 15 Jan 2023 \ on: Daily discussion thread
Looks like the nitter.at instance is down. Example, the following results in HTTP 502.
https://nitter.at/RoninDojoNode/status/1597300114200350720
nitter.it had gone down a couple months ago, then came back. However, it doesn't seem to work consistently -- sometimes I see "Tweet not found". (But then subsequent attempt to reload that same nitter.it link might render the Tweet properly).
The instances I sampled from the RoninDojoNode Tweet above seem to work, as does nitter.dark.fail, e.g.:
https://nitter.ronindojo.io/RoninDojoNode/status/1597300114200350720 https://nitter.dark.fail/RoninDojoNode/status/1597300114200350720
However there was a reply comment to one of my posts saying Twitter is messing with the API to prevent Nitter:
Just heard nitter is going away. [...]
#122637
I think that would obliterate many apps that use the Twitter API, so I don't know that is an accurate claim. Maybe it is just Twitter worsening the rate-limits on certain usage patterns that spam bots follow, and Nitter instances have similar usage and thus also are affected? Who knows.
Anyway, centralized social media is the plague, yo!!! I'm as guilty as anyone though.
Hoping to see nostr and such send Twitter for a long dirt nap.
write
preview
0 sats \ 0 replies \ @cryptocoin 15 Jan 2023
Update
Third-party Twitter clients stop working, no explanation #122718 https://www.theregister.com/2023/01/14/third_party_twitter_clients_stop_working
reply
0 sats \ 0 replies \ @cryptocoin 15 Jan 2023
I wonder if one or more links on SN that are for Nitter tweets (using a specific Nitter instance) that end up ranking high on SN results in a slashdot effect for that specific Nitter instance.
reply