Blue-Blocker: Stopped Queuing New Accounts to Block/Mute

OK, I have established it kinda now, managed to figure out:

• It succesfully queues users to block and blocks them if they appear in my feed. Looking at the “For You” timeline instantly queued 10 more users and blocked them.

• It does not queue users when I browse replies for tweets like these: https://twitter.com/elonmusk/status/1654972024203223041 - no queueing at all.

v0.25 seems to be working, thank you!

chrome has been published and is live

thanks for the help everyone, it was invaluable

No way buddy, your plugin is invaluable!

Fully working now, thanks!

firefox has been published and is live

I’ve pushed the new version to both web stores. it could take a while for them to be approved, and even longer for your browser to automatically update. I’ll keep this thread updated for when they are fully published so you can manually update, if you want

ok. I figured out the issue and the solution. it’s very irritating. they changed the graphql used by these two endpoints. [twitter’s] graphql works by compiling a query and saving it’s id and invoking it via a url in the format https://twitter.com/i/api/graphql/<query id>/<query name> the query for TweetDetail (which serves individual tweets and tweet replies) was updated and the new query id (base64 encoded) contains a -. the magic regex used to check urls only allowed alphanumerics and periods. adding - (and _ because url b64 encoding and also =, just to be safe) fixes this issue. I’ll push an update asap, the new version will be 0.2.5, all bugs and features already labelled 0.2.5 will be pushed to 0.2.6

@neonharbor please check this comment and see if this is your issue as well. I will attempt to confirm myself asap

Yep, same behavior!

if anyone on this thread has some free time and wants to double check these that would be very helpful

Just chiming in to say I’m experiencing the exact same thing. Going into replies doesn’t sweep anybody up, but it still seems to work elsewhere. Just started happening today. I ended up here trying to figure out what was going on.

Here it is! No sign of “authorization” so I should be good:

{ “BlockCounter”: 172, “BlockCounterCriticalPoint”: null, “BlockQueue”: null, “BlockQueueCriticalPoint”: null, “MultiTabEvent”: { “headers”: null, “reason”: 0, “type”: “UserBlockedEvent”, “user”: { “has_nft_avatar”: false, “is_blue_verified”: true, “legacy”: { “blocking”: false, “followed_by”: false, “followers_count”: 15771, “following”: false, “name”: “Sterling Crispin 🕊️”, “screen_name”: “sterlingcrispin”, “verified”: false }, “rest_id”: “65498425”, “super_following”: false }, “user_id”: “65498425” }, “QueueConsumerCriticalPoint”: null, “blockCounterCriticalPoint”: null }