You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
If you *must* do this (and understand the risks), either use full legal names to maximize entropy and a very strong salted hash, like say bcrypt/scrypt tuned to take 5 seconds per hash on a CPU, or similar...
... or use a very *weak* hash, like the 6-digit prefix of the SHA1 (24 bits), to guarantee collisions and thus make it a probabilistic filter and not something you could brute force usefully.
none of which helps if someone knows you and your likely abusers
Exactly.
Real abusers will search for their hashes (no tech skills required). So posting hases non-anonymously poses risk!!!1 Such hashes can be widely abused (against names of all genders). Anyway the last stage will be report to police (so trusting police is still required).
Keeping there names a secret is not the point. Its against it actually. It just about getting some time to find others, without dropping a plaintext Google spreadsheet.
I know. And I'm saying that won't work after someone writes a Twitter bot to reverse the hashes in seconds for the lulz, turning the approach into the equivalent of a plaintext Google spreadsheet.
If a weak hash is used, can't you easily filter out collisions that don't look like a real name with a few heuristics?
You set up the hash so that you get collisions with *real names*. For example, for a target population of 1,000,000 names, you'd perhaps want a 16-bit hash that would yield ~16 expected collisions per hash.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
