questionsdoes anyone else have trouble accessing the…   You
would think that Woot would be clever enough to at least
redirect you to a cool page, not just some error screen.   It's
apparently a problem for everyone now. :(   @xarous: Let me
explain again why that workaround is problematic in my specific
instance.  When using Google search, adding the restriction
"Site:x.y.TLD" restricts searches to that domain. That will
certainly reveal who has posted messages on Woot with that user
ID. However, lots of Wooters have never posted a message; they
would not show up in search results. You can also use the Woot
search box to effectively get the same results.  In my case, I
was testing to see if there was anyone using a specific Woot
user ID to determine if it was available. While a Google search
for postings would get a hit on many Wooters, it does not cover
the whole namespace. The only way to test for an ID is to try
and create it. Tedious when trying several possibles.  I realize
that would be a rarely needed