When blocking at max threshold, signs twitter user out

[dr0cx]

Test on a large twitter account with more than one million followers. Max threshold reached at 35000. Twitter api max on that, fine. Attempt to block chain again, and your Twitter account is now signed out.

[roycewilliams]

If this is happening to you as well, please use the "thumbs up" reaction above to add your vote. (I've done so)

[dr0cx]

Update, The signout occurs when "There was an error retrieving more accounts. Please refresh the page and try again." At this point, you are signed out, after the OK button, the error count climbs. This is due to being signed out.

[dr0cx]

Update 2: Performing block chain on a relatively small account, < 4500 followers, twitter is signed out upon completion of blocking the followers.

[Ludwig777]

18K accounts group. it's doing like 500 blocked actions or less and it signs you out. It's hard to come back and redo it again, it gives also usually errors retriving the list again so you can't complete the task even when signed in back.

[amosnet]

My twitter account got restricted yesterday by twitter for automated functions.

The threshold for me was down to 500 due to a heavy block-list I already have.

I kept signing back and continue blocking after I got signed out for some rounds, until bang! a reCAPTCHA and SMS verification code was required, I found my account was restricted.

The SMS was never been received by my phone number which I've been using it for 10+ years.

[JeffreyBai]

Same thing here, got logged out after blocking 500 accounts. Then account restricted and reCAPTCHA + SMS verification. Unfortunately my instinct is that it's very likely to be a new policy in Twitter API.

[amosnet]

Same thing here, got logged out after blocking 500 accounts. Then account restricted and reCAPTCHA + SMS verification. Unfortunately my instinct is that it's very likely to be a new policy in Twitter API.

Same thing here, got logged out after blocking 500 accounts. Then account restricted and reCAPTCHA + SMS verification. Unfortunately my instinct is that it's very likely to be a new policy in Twitter API.

Sorry to hear that, did you eventually get the SMS? It's been 15 days for me, never received any SMS and my appeal seems to fall on the deaf ears.

[JeffreyBai]

I received the verification SMS immediately, so there's no problem for me.

[ShaggyDemiurge]

After trying to block a large amount of followers (Glinner 60k) it started showing errors, then logged out of twitter. After that twitter breaks completely: page itself is loading, but any data, absolutely any data does not. Ctrl+Shift+J shows that every single internal request returns error 403 (without any message, empty brackets where this message I guess is supposed to be)

Thing is, this is browser-related and not account-related: after this happened in Vivaldi I was able to freely look at page without any problems in Chrome (on same computer) and twitter mobile app

[amosnet]

After trying to block a large amount of followers (Glinner 60k) it started showing errors, then logged out of twitter. After that twitter breaks completely: page itself is loading, but any data, absolutely any data does not. Ctrl+Shift+J shows that every single internal request returns error 403 (without any message, empty brackets where this message I guess is supposed to be)

Thing is, this is browser-related and not account-related: after this happened in Vivaldi I was able to freely look at page without any problems in Chrome (on same computer) and twitter mobile app

Clear your cookies pal, we've been there.

[amosnet]

My twitter account got restricted yesterday by twitter for automated functions.

The threshold for me was down to 500 due to a heavy block-list I already have.

I kept signing back and continue blocking after I got signed out for some rounds, until bang! a reCAPTCHA and SMS verification code was required, I found my account was restricted.

The SMS was never been received by my phone number which I've been using it for 10+ years.

Update:

Account has been suspended just now.

[gaeulbyul]

Just FYI, Currently I developing another blockchain-like extension using block_all API called Red Block. Unfortunately, it has another issue that not all followers block immediately, but at least it doesn't have a force-logout problem. (Note that its main language is Korean and English translation is not completed yet.)

• Firefox: https://addons.mozilla.org/en-US/firefox/addon/red-block/
• Chrome/Chromium: https://chrome.google.com/webstore/detail/red-block/knjpopecjigkkaddmoahjcfpbgedkibf

[tylerarnold]

Block Chain sleeps 100 ms between API calls, which comes to 600 API calls/minute. The twitter API does not allow anywhere near that for almost API call I see here: https://developer.twitter.com/en/docs/basics/rate-limits . Block Chain probably needs to throttle itself better via querying https://developer.twitter.com/en/docs/basics/rate-limits to avoid getting throttled or flagged.

[xxdvazxx]

Test on a large twitter account with more than one million followers. Max threshold reached at 35000. Twitter api max on that, fine. Attempt to block chain again, and your Twitter account is now signed out.

Sorry for my poor english, but the process bellow worked to me.

Do the following steps: 1 - Go to the followers page of the profile that you want 2 - Left Click on the extension button 3 - Click "Run Export Chain" 4 - Wait finish the process. Maybe, near the final process it seem stoped. Just wait. 5 - It will generate a large text. with the text mouse (text selector) just click once before the first caractere. Roll to the final of the list, hold "Shift", click just after the last letter (character, I dont know the word lol). All the text will be selected and this is the only way to select everything in this box. 6 - click "done" 7 - left click in the extension button 8 - Click "run import chain" 9 - paste all the text that you just copy to this text box 10 - click "start import" 11 - Click ok and thats is. No troubles with twitter restrictions

[xxdvazxx]

Test on a large twitter account with more than one million followers. Max threshold reached at 35000. Twitter api max on that, fine. Attempt to block chain again, and your Twitter account is now signed out.

Sorry for my poor english, but the process bellow worked to me.

Do the following steps: 1 - Go to the followers page of the profile that you want 2 - Left Click on the extension button 3 - Click "Run Export Chain" 4 - Wait finish the process. Maybe, near the final process it seem stoped. Just wait. 5 - It will generate a large text. with the text mouse (text selector) just click once before the first caractere. Roll to the final of the list, hold "Shift", click just after the last letter (character, I dont know the word lol). All the text will be selected and this is the only way to select everything in this box. 6 - click "done" 7 - left click in the extension button 8 - Click "run import chain" 9 - paste all the text that you just copy to this text box 10 - click "start import" 11 - Click ok and thats is. No troubles with twitter restrictions

IT DOESNT WORK PERFECTLY AND IT ACTIVATE TWITTER RESTRICTIONS, BUT YOU CAN LOGGIN AND TRY AGAIN NEXT WEEK TO BE SURE THAT TWITTER "FORGET YOU"

[rpardee]

I bet @tylerarnold is right about blowing the rate limits. What I've found necessary (regardless of how many accounts I've used TBC to block) is go into the browser settings & clear twitter.com data. Then I can immediately log back in to twitter.

I wonder if twitter changed those rate limits recently.

[rpardee]

Just for a goof (b/c I don't really know what I'm doing) I tried out this change: The rate of block operations shown in the dialog was noticeably slower (updated in chunks of 5 accounts at a time it looked like) but at the end of it my session was still invalidated. :(

[digitaldraco]

Update, The signout occurs when "There was an error retrieving more accounts. Please refresh the page and try again." At this point, you are signed out, after the OK button, the error count climbs. This is due to being signed out.

Two years later... same problem.