search

eviltester / blogcomments

1 stars 0 forks source link

blog/eviltester/2019/11/25-automating-twitter-interests/ #32

Open utterances-bot opened 4 years ago

utterances-bot commented 4 years ago

Automating Deselection and Unchecking of Twitter Interests - EvilTester.com

Twitter has automatically collated a list of interests for each user, you can uncheck these if twitter has them incorrect, or possibly too correct, and you do not want twitter knowing your interests.

https://www.eviltester.com/blog/eviltester/2019/11/25-automating-twitter-interests/

Cassolotl commented 4 years ago

I'm getting stuff like this (copied as it flew by in the console):

main.7ab0ea14.js:1 Uncaught (in promise) Error: ApiError: https://api.twitter.com/1.1/account/personalization/p13n_preferences.json HTTP-500 codes:[131] traceId:undefined at De (main.7ab0ea14.js:1) at main.7ab0ea14.js:1 at main.7ab0ea14.js:1 Show 41 more frames main.7ab0ea14.js:1 POST https://api.twitter.com/1.1/account/personalization/p13n_preferences.json 500 (anonymous) @ main.7ab0ea14.js:1 d @ main.7ab0ea14.js:1 errorFilter @ main.7ab0ea14.js:1 etc.

eviltester commented 4 years ago

That can happen eventually when running, if there are a lot of items selected. I think the back end doesn't like so many changes being made.

You could try changing the timer amount to a higher value and see if it is the speed of making requests that makes a difference. e.g. 5000 for a 5 second gap between messages.

Or... what I do. Refresh the page at that point to stop the script. Then run it again later.

You may notice, when you get to that point. If you stop the script by refreshing the page. That any attempt to uncheck the preferences manually also shows that error. This is why, when people do the entire page by hand. They see that not all preferences were unselected them, even though they unselected them all. Because they didn't notice that half way through the process, the backend started throwing errors on the console.

Cassolotl commented 4 years ago

Ahh, thank you! :)

mcmahonsport commented 3 years ago

Thanks for this, it's very useful. I started getting 503 errors about halfway down a list of about 350. I'll try your, wait and try again approach.

rpresser commented 3 years ago

You may notice, when you get to that point. If you stop the script by refreshing the page. That any attempt to uncheck the preferences manually also shows that error.

Indeed, this is what happened to me after it got to the "I's" in the alphabetical list. I find it astounding that Twitter is so greedy about ad revenue that it won't let you uncheck all your preferences, even if you do it by hand. Seriously considering deleting my account, again.

carchrae commented 3 years ago

thanks for this. they seemed to spray me with suggestions today. i modified your code so it would not fire all the timers at the start. https://gist.github.com/carchrae/e44403aa0995c1aa23b8f27347db050e

Canzandridas commented 3 years ago

I didn't even realize you could just type stuff on the console and it would run the code as soon as you hit enter. But of course, I know nothing about programming so why should I lol this is awesome, thank you very much!

I had to make it 10 seconds in between steps but so far it's working like a charm!

jeski commented 3 years ago

made no adjustments at all, worked seamlessly. thank you!