4 ms·
To your first question: The list in question, has 50 items actually. [1] To second one: we're avoiding having to get authorisation from users to read/write fro
by nevi-me 9y ago
To your first question:
The list in question, has 50 items actually. [1]
To second one: we're avoiding having to get authorisation from users to read/write from their accounts.
Twitter also won't hesitate to revoke our API access when we start automatically blocking accounts on behalf of hundreds/thousands of users.
Also, imagine if the Russian botfare targets us, they're more sophisticated. We would have to keep users' tokens somewhere, in the wrong hands that's one propaganda machine. We think their time's coming, because our delinquent president is pushing through a nuclear deal that's going to cost our grandchildren dearly.
I use their API a lot, and would love to do that, but at this point it might not be the most practicable option for us. Perhaps @Twitter staff could advise us ...
[1] http://blocklistza.000webhostapp.com/ http://blocklistza.000webhostapp.com/
- tedmiston 9y agoThat makes sense. What's the issue you're seeing with a list of 50? There's a guy @levelsio on Twitter who made a similar project but for crowdsourcing block words at https://mute.life/ https://mute.life/. I'm not sure whether he's tried to automate any of it yet. So you don't want to use the API but you do want to keep the list up-to-date for all users kind of like sources for an ad blocker. Am I understanding your use case right? I've been looking for / to make a Twitter blacklist service for companies that get too spammy.
- nevi-me 9y agoThe list wasn't 50, my mistake. It's a few hundreds. I saw mute.life, thanks for that. Yes, don't want to use the API. We can set up a small script as part of our workflow, that updates the latest blocklist, and then people can download it and import it. The blacklist service would be interesting, although I think Twitter would 'crack down' on it if it becomes too successful.