78
Nitter is Dead
(github.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 01 Feb 2024
78 points (100.0% liked)
chapotraphouse
13538 readers
1063 users here now
Banned? DM Wmill to appeal.
No anti-nautilism posts. See: Eco-fascism Primer
Gossip posts go in c/gossip. Don't post low-hanging fruit here after it gets removed from c/gossip
founded 3 years ago
MODERATORS
the telegram Q might be better answered in the news mega, they seem to know all that stuff in great detail
But yeah, I'm kinda in the same boat but I will never sign up for twitter lmao. I'm holding on to nitter.privacydev.net and any other working nitter as long as I can (I don't browse but sometimes its nice to be able to follow links from here). Someone in the github seems to think privacydev is using tokens from real twitter accounts so it might not be affected by the end of guest accounts. If the crypto spammers can farm accounts, then nitter can too, right? lol
maybe I'll see if I can't browse tweets with archive.org when/if that fails
If there's a way to automate account creation and deletion maybe it's possible to use real accounts in the way that guest accounts are currently being used. Just rotate out every 30 days?
no reason to rotate them out unless they get banned tbh, older accounts are probably more trusted
I think automating account creation will be challenging, but you could probably automate activity that keeps them from getting instabanned (apparently even genuine accounts can get banned for lurker behavior basically) but I do wonder how many accounts you really need to run an instance. If its not that many and they don't get banned that often you could have actual humans do the captchas and legwork to register them and then hand the tokens off to nitter/activity bots.
Rotation would just be for privacy measures as that way any analytics tied to the account get dumped.
I wonder how the bot farms automate it, there's clearly a way they do it unless they actually have teams of people manually creating accounts. Even then based on user load there's only so many that would actually need to be made.
for a public instance I don't think that measure is needed, since dozens or hundreds of random people's traffic is aggregated together, and ideally each user would also have a bunch of public instances and use a different one each time (thats what Libredirect does) further diluting the pool
That's the approach the Ad Nauseam extension takes, I guess at scale on a public instance it could work well enough