All attempted blocks return errors.

[cristynhoward]

The Chrome extension is completely non-functional, now. Every attempted block gets reported as an error.

I noticed it a few days ago.

EDIT: someone else has noticed this issue as well, see screen cap below

[ceceradio]

Still works for me. Additional info? Browser? Can you provide screenshots of web inspector? network tab? error'd out request responses?

[Phrobbert]

Looks like Twitter may be blocking the extension, it returns a 403 error.

[ceceradio]

it's possible you are being throttled. have/had you been using the extension extensively before the errors started happening?

the web API calls our tool uses have relatively high API call limits since it's intended to be used by the twitter app and not our extension. that being said, those API call limits are undocumented, so i have no idea when that throttling starts to occur.

you may have luck trying the extension on another computer or waiting out out the throttling if that's what's happening. if its still broke after 24 hours, checking the request response in the network tab would be my next ask to try and figure out whats going on

[kmkm0408]

Rotating the block chain will continue to produce an error that was not in the past. You could just a few months ago, if you ran over a thousand people around a block chain, you could get a block. Now, if I turn on the current program, I keep getting errors. It looks like a program error. Please look at it and fix it.

[ceceradio]

Folks I need a bit more info if I'm going to be able to help. Can you please open the Network tab in your web inspector, type "block" into the filtering menu, and then select a block request that was got an error. Select the "Preview" or "Response" tab and copy the results into a message here.

[kmkm0408]

This is how the error will occur. I think it's a program error. Apparently, a few months ago, I turned around this program to spin blocks with more than 1,000 accounts. And then I said, " Well, it's a mistake, but I just switched it today for the first time. I always don't want to create an account. I used this program without any errors. Therefore, please check. There is no problem with the computer at all. because I've been using this program on my own computer.I am very sad. I would like to use this program without any errors.

[ceceradio]

@kmkm0408 can you please click one of the "block" entries in the list from your screenshot. Then, copy+paste the text from the "Preview" or "Response" tabs?

[kmkm0408]

If you press it as you want, I will be Korean. Is it okay?

{"message":"해당 작업을 실행하실 수 없는 계정일 수 있습니다. <a role=\"button\" class=\"js-reload\" href=\"#\">이 페이지 새로 고침 을 하신 후에 다시 시도해주세요."}

A brief description would suggest that the account is not capable of running the task. Then, I would like to refresh the page and try again. But if it's a simple error, every account I want to use a chain block has this error.

[ceceradio]

@kmkm0408 thank you! that's very strange. I am unsure if this is a problem with the program or with twitter. I'm trying to debug it...

[kmkm0408]

You mean it could be an internal stream of Twitter?

[ceceradio]

@kmkm0408 yes, its possible that twitter's servers are preventing the addition of blocks either due to throttling (artificial limit of the number of blocks) or due to server overload...

[kmkm0408]

But if you search, you'll also find some people who can run programs.

[ceceradio]

@kmkm0408 yes i am aware. i am included in that group. however, twitter is known to throttle certain IPs/browsers when too many requests are made. Additionally because twitter is a network of servers, some regional servers may be overloaded while others may not. it's hard for me to debug with twitter doesn't give me enough information.

[kmkm0408]

If there is any error in the program, please correct it and let me know because I desperately need to write the program.

[kmkm0408]

I would like to use this program for a long time. Please, it is just a program error.

[ceceradio]

@kmkm0408 have you tried signing out and signing in again, then trying to use twitter block chain again?

[ceceradio]

@cristynhoward @Phrobbert could you two both give me response bodies similar to how kmkm0408 did? thank you.

[kmkm0408]

Yes, of course I've logged out and run the program, but it hasn't run. I think there is a kind of a reaction like this @Phrobbert

[kmkm0408]

Please let me know exactly what I need to tell you. I'll give you my best answer.

[kmkm0408]

@satsukitv Isn't this a program error?

[ystros]

I started seeing this issue as well earlier today. Running Twitter Block Chain on a list of followers results in 403 Forbidden errors for each follower it attempts to block, each with the response:

{"message":"Your account may not be allowed to perform this action. Please <a role=\"button\" class=\"js-reload\" href=\"#\">refresh the page</a> and try again."}

Using block directly through the twitter.com web interface continues to work properly, so if it's a rate-limiting issue, the official web interface doesn't seem to be affected.

I also attempted signing out of Twitter and back in, which did not fix the issue.

I do notice a difference in the request form data for the web interface vs TBC. I'm not sure it's significant, but I'll provide it. Sensitive info such as auth tokens and user IDs redacted, but they remain identical between the two requests. Both requests seem to be hitting the same URL (https://twitter.com/i/user/block).

Block request via twitter.com web interface (works correctly):

authenticity_token: [REDACTED]
challenges_passed: false
handles_challenges: 1
impression_id: 
user_id: [REDACTED]

Block request via TBC (403 error):

authenticity_token: [REDACTED]
block_user: true
impression_id: 
report_type: 
screen_name: [REDACTED]
user_id: [REDACTED]

Let me know if there's additional info that would be helpful tracking this down!

EDIT: If relevant, these results are from Google Chrome 65.0.3325.181 on Mac OS X.

[kmkm0408]

Hello! Then, do you think it is an internal problem on Twitter or an error on this program? @ystros

[shinglesnowbeam]

Hi. I use this and "Twitter One Click Block" extension, and both could not be used at the same time from some day before. So I guessed that there was any change on Twitter. "Twitter One Click Block" error is fixed yesterday. maybe they have some hint to fix.

[Phrobbert]

Late returning to this thread but I get the same results as Ystros.

message:"Your account may not be allowed to perform this action. Please refresh the page and try again."

[ceceradio]

hi folks. if i get time this weekend i will try and release an update that may help. without experiencing this issue myself it's going to be difficult to provide a quick solution, though.

[jay-visitseattle]

I am seeing this issue as well today (though I haven't tried running this extension in a while).

I am using a Asus Laptop running Windows 10.

Request Headers:

Request URL: https://twitter.com/i/user/block
Request Method: POST
Status Code: 403 
Remote Address: 104.244.42.129:443
Referrer Policy: no-referrer-when-downgrade

Response:

{"message":"Your account may not be allowed to perform this action. Please <a role=\"button\" class=\"js-reload\" href=\"#\">refresh the page</a> and try again."}

None of the blocking actions succeeded for the initial run, or the run I did a little later to make sure I wasn't being throttled. I hadn't used this plugin in at least a month previously.

Let me know if I can offer any more information or do anything to help debug. This is an excellent plugin!

[cicifluff]

I am getting the same errors. No one I block actually gets blocked. It used to work for me.

[kmkm0408]

Have you found the cause of the error yet? Or are you in a situation where you can't solve the error because it's internal to Twitter? I want to know.

[ceceradio]

Currently Chrome has a bug where the content_scripts injected into a page, from an extension, are not considered to be on the same site as the page itself. So sites that utilize SameSite cookies will not be able to send requests with those cookies attached. https://groups.google.com/a/chromium.org/forum/#!msg/extensions-reviews/SoLuNWUCvnA/d8aAhyxzAAAJ

Fortunately, Firefox doesn't have this problem. I have updated the Firefox plugin to the latest version (thanks @gaeulbyul for putting in the work on that code).

https://addons.mozilla.org/en-US/firefox/addon/twitter-block-chain/

For now I am going to leave this issue open while I weigh options for trying to get the Chrome version working again.

[ceceradio]

Update: Chrome Beta (67) has the code to fix the issue. When Chrome 67 hits stable the extension will be usable again on normal Chrome installations. Closing the issue since there two workarounds and a fix will eventually be delivered through standard Chrome updates.

[ceceradio]

6 more days :^)

[ceceradio]

chrome 67 is rolling out! please check for updates in chrome and report back if there are any issues on chrome 67! Thank you!