keybase / keybase/keybase-issues
Twitter detecting proof post as spam and suspending account
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
After posting my proof, I received an email from Keybase that my proof was broken and the following message from Twitter:
Twitter has automated systems that find and remove multiple automated spam accounts in bulk. Unfortunately, it looks like this account, @ewzimm, got caught up in one of these spam groups by mistake.
We apologize for this inconvenience. It’s possible your account posted an update that appeared to be spam, so please be careful what you tweet or retweet. You might also want to review our help page for hacked or compromised accounts: //support.twitter.com/entries/68916. You will need to change your behavior to continue using Twitter. Repeat violations of the Twitter Rules may result in the permanent suspension of your account.
Contributor guide
No contributing guide indexed for this repository
Research direction
The report names no repository files, tests, or entry points. Start by reviewing the proof-posting flow and the quoted Twitter suspension notice, then establish a reproducible acceptance case for a proof post that is not classified as spam.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100