Automatically logged out from Blue Blocker usage

[jaredtjahjadi]

Every now and then while using this extension, I get automatically logged out from Twitter. Usually it starts with some replies not being able to load: the page would say "Something went wrong. Try reloading." with a blue Retry button under it. Then I would refresh the page and the website would either work as usual or log me out and ask me to sign in again. About a week ago my account was also temporarily suspended, probably because of my Blue Blocker usage. Is there a way to bypass these random logouts?

[alanpaone]

best fix is to turn your block interval up. Blocks are severely rate-limited, and also we're technically breaking the rules and abusing the site. it helps, anecdotally, to actively be using the site, if they only thing you've done since logging in is load your Following Feed and then sit and block a blue check every 15 seconds for 6 hours, that'll be pretty obvious

[kctipton]

Wait, abusing the site? By blocking checks? I do that manually all the time. I don't understand the issue Munsk would have with this.

[alanpaone]

he has actually publicly complained about large blocklists being bad, both from his weird version of free speech, and because of the way the site has to do extra work when loading but not displaying blocked tweets. once you block a few tens of thousands of people, you start to notice that big tweets load slowly, which is very funny. Obviously i think its cool to do this, but using automated tools and web scraping the site to find paid users and then blocking them, is not really something we should expect to be a supported use case. We're getting caught using the same techniques that bots use to make spam posts and send those weird DMs. in my opinion, its what they get for taking away the API, using a service like Blocktogether or the Blockbot was more efficient for both us and them, but now, just think of it as a cat-and-mouse type thing. every time you get logged out its because you blocked so many checkies you made a computer notice.

[pyxfluff]

never been detected with 20k+ blocked

[sekoku]

Wait, abusing the site? By blocking checks? I do that manually all the time. I don't understand the issue Munsk would have with this.

It's automated by the extension, that's why. He wants you to manually block.

I was suspended yesterday because of this extension (and blocking at 3seconds each) despite having a locked/non-public account. So anyone using this should be careful or don't give a *bleep* about their Twitter account anymore because you will possibly get banned eventually.

[kheina]

in order to avoid getting banned/suspended/logged out, you should set your block interval to at least 15 seconds, maybe even 20 to be safe

[christopheml]

This policy from Twitter has nothing to do with Musk, they had server-side detection of automated behavior dating back several years before he bought the site. Basically Twitter wanted you to automate through proper API usage.

[Anyasia]

I'd just like to note that I'm still being logged out even with the block interval maxed out to 60 seconds. While I'm sure it's unavoidable to some degree—the site's designed to detect the behavior, after all—it would be nice to be able to extend the block interval to even longer in order to mitigate this somewhat, as it definitely happens less at 60 seconds than it was at lower intervals.