Conversation

Replying to

@allgebrah

and

test4

Replying to

and

test5

Replying to

and

Btw some of shadowban phenomena are in fact app api generated. Twitter app developer support deals with a lot of it

Replying to

I was going to debug that later, it's rare to have such a fine test case

Replying to

I read back in your Tweets & realised you might be using an app that could be causing it. For developers: support.twitter.com/articles/79901

Replying to

thanks! but no, web twitter only, I suspect it was the linking of a once-spammy domain that did it

Replying to

Try filing a support ticket and reasoning with the Twitter Overlords?

Replying to

yeah I suppose - if it doesn't expire by itself

Replying to

it did - just now. You showed up in my mentions. Did you by chance change pass yesterday? Might have done it.

Replying to

a-hah, and it works again! Yeah, I expected it to run out based on the information in scifiwright.com/2016/02/twitte

Replying to

and

and no I did not change my pass - assuming the system thinks I've been hacked, changing a password would be a bad sign

8:02 PM · Sep 16, 2016Twitter Web Client

Replying to

actually changing password is one of their recommended methods for lock-out in their help forums :-)

Replying to

what kind of "for" is it though? helping lockout of helping against lockout?

Show replies