250,000 English words currently available as Twitter handles
peticol.as
peticol.as
grep -P '(phobe|phile|ist)\s*$'
@categorist or @pantywaist, anyone?
Edit: Equally fortunate: abdominohysterectomy.com is available.
http://www.whois.com/whois/abdominohysterectomy.com
Jokes asides, it would be useful to cross check this with domain availability and username availability on other _popular_ social sites.
1) Find the verified Twitter account followed by minimum number of users - This is easy, since Twitter maintains an official list of verified accounts at https://twitter.com/verified/following . We could iterate over this list, and find the minimum.
2) Find the maximum-followed non-verified Twitter account. Now this is a harder problem. Does anyone have any ideas apart from brute-forcing Twitter handles?
10 million followers. Not verified.
Pretty sure they win. They're in the to 50 on the followers list, and the rest are basically singers or really famous.
Besides their developer-relations problem, namespace pollution and stagnation is a big problem for Twitter going forward. Who wants to join and use a service when the closest thing they can get to their desired username is a second-class moniker like @ffffirst_last1 or @L4stF1rst88 ?? I've heard this complaint from several of my friends who were late to the Twitter scene. The name availability issue is the main reason I think app.net has any chance of succeeding.
all me leave events resources myself post status pages accounts positions discuss administrative remove root join session statistics phone friendship blocks focused links responsibilities administered explore suspended sessions receptors discusses characterization practised translate ensuring frontiers stationed industrialization telecommunications distinguishes occurrences condensed resembled rapidity legislatures misunderstanding gastrointestinal administering discharges ensued characterizes
perl -e 'print sort{length $a <=> length $b} <>' english-words.txt > sorted.txtCan you explain what's happening there?
What it's doing:
One of the call types of the sort function takes a block as its fist parameter and a list as its second. When called this way, the block should operate on two special variables ($a and $b), returning a -1, 0 or 1 depending upon whether $a should be placed before, beside or after $b in the sorted list. The "<=>" operator does this comparison on numbers, the numbers in question being the lengths of the two variables.
The second parameter here is a read of a file handle (the syntax for this is "<filehandlename>"). When the file handle read is used with no named file handle, it reads the the contents of each parameter the script was passed in turn (or STDIN if none). Perl reads files as lists of strings, with each string being a line in the file.
The sorted list is then printed to STDOUT.
There's some, but they're all nonsense. Nasty ones like 2q4 for the most part.