Difference between revisions of "1963: Namespace Land Rush"
(gmail / garfield)
(→Table: When compared to the line immediately below, it's clear the quotes in this line are typographic)
|Line 287:||Line 287:|
|<nowiki>@ é |
|<nowiki>@ é | </nowiki>
Revision as of 22:46, 11 March 2018
|Namespace Land Rush|
Title text: You can also just mash the keyboard at random, but you might end up with a gibberish name no one can pronounce.
| This explanation may be incomplete or incorrect: Expand the explanation. Do NOT delete this tag too soon.|
If you can address this issue, please edit the page! Thanks.
When a new web service starts, such as a forum, a social media server or an email portal, the people who sign up get to choose their username on the service, which, in most cases, blocks future users from using those usernames. Common names such as "john" are likely to be taken quickly. This is analogous to the way that land was distributed in America, with the first to claim able to choose the best land.
This comic is a list of usernames Randall suggests should be used if they are available.
The title text is a self-reference to "xkcd", the name of the comic is a purposefully unpronounceable phrase created by Randall.
| This explanation may be incomplete or incorrect: Add explanations of the names. Do NOT delete this tag too soon.|
If you can address this issue, please edit the page! Thanks.
|Straightforward (Usernames that a person would use under typical circumstances)|
|<Your usual username, if any>||Most internet users will have settled on some unique handle that they try to use across all platforms. Even if this wasn't a new service, most people would try this first.|
|<Your given name>||More rare is using one's nickname or first name as their username, since the amount of common names will mean many users share a name. Thus, if you can get your given name, you will have a simple username that many others wanted, and without resorting to prefixes or numbers (i.e. Xx_MyName00_xX)|
|<Your full name>||Similar to your given name, but slightly more unique since a last name and/or middle name is added.|
|<Initial><Surname>||A common second choice if a given or full name is already in use.|
|<Surname>||Possibly available if your last name is more uncommon; names like "smith" or "kim" will probably be taken faster than even given names.|
|Recognizable (Usernames that would make it look like the email came from an official source within the organization named)|
|Registering the name "Google" would allow for communicating on the site (or even outside of it) with a name that appears to be an official Google account. For any of the examples in this section, you would select the names for the same reason. This has been done in the past with both humorous and nefarious results.|
|iPhone||Many services would mark messages sent from an iOS client on iPhone as "sent from iPhone".
This could make people believe that your messages are sent from an iPhone even if you don't own one.
|Similiar to Google above.|
|Obama||Impersonating a president, supposedly to send messages as them to make them seem bad (or not).|
|Garfield||In the original "GMail" service on the Internet, the G stood for "Garfield"|
|<Name of person who runs the service>|
|Causing Trouble (Usernames that might cause errors when mixed with the service's back-end code)|
|You||Many services display "You" as the signed-on user, so naming oneself "You" makes users think that they are you/they are signed on when they aren't.|
|Guest||Attempts to fool users into thinking that they have a guest account.|
|Causing More Trouble|
|Admin||Impersonating to be a system administrator will let someone fool people and cause a lot of trouble. In particular, it could be used to obtain SSl certificates by demonstrating ownership of a supposedly internal address.|
|System||Pretending to be a system-controlled account - might give permissions if the server checks by name.|
|<Name of service>||Pretending to be the official account of the service.|
|Help||Pretending to be the help account. This could led to many questions from new users.|
|Impossible to Say|
|Hyphen-Emdash||Could be read "Hyphen hyphen Em dash" or "Hyphen dash em dash"|
|Dash-8hyphen-8||Could be read "Dash dash eight hyphen dash eight" or "Dash hyphen eight hyphen hyphen eight". "Hyphen eight" sounds like "hyphenate".|
|Zero0ne2numeral2||Could be read "Zero zero one two numeral two" or "Zero zero ne two numeral two" or "Zero oh ne two numeral two".|
|KrisasinHemsworth||This would be confusing to say out loud, as it would sound like the user was saying that their username was "Chris," spelled the same way that famous actor Chris Hemsworth spells his name. However, the actual username uses the name "Kris," spelled a completely different way than Chris Hemsworth's name, and the phrase "as in Hemsworth" being also part of the username, rather than a clarification of the spelling of "Kris" as would be assumed.|
|TheWord&Ampersand||This would also be confusing and difficult to communicate, as anyone trying to read the username to someone else would say "The word ampersand ampersand" which could be interpreted as "ampersand&" or "ampersand ampersand". Having the phrase "the word" in front of a symbol makes it quite difficult to communicate which variation of ampersand (word or symbol) is actually being referred to.|
|ZettaWith3Teees||Read aloud, this would lead the listener to expect a username of 'Zettta'. Clarifying that "with three tees" is text and not description would in turn make it difficult to explain the spelling of 'Zetta' with two 't's, and 'Teees' with three 'e's.|
|<SQL/JS Injection>||Codes such as "Drop Table" intended to cause errors or even damage the service's back-end code. (See Comic 327)|
|Bot||Pretending to be a bot.|
|Deleted||Some services like Reddit keep up user posts and data after account deletion, marking the content as submitted by the user "[Deleted]" or "Deleted".|
|Permissive Character Sets|
|@ é | " "|
|\ . # " '|
|<RTL override>||The right to left override is an Unicode character which forces text after it to be laid out right to left. Thus, in left-to-right locales, it flips everything after it. This can be rather amusing if permitted. (See Comic 1137)|
|<Any emoji>||Current databases are not set up to store emojis as characters.|
|","||In CSV files this separates one column or data item from another. This could cause bugs if the usernames are used as part of a CSV file since the next column on the row could be left blank filled with other data.|
|&NBSP;||The special entity in HTML (web page language) for a non-breaking space, or a space that prevents an automatic line-break at its position. When rendered as part of an HTML page without sanitization, this would only display a space.|
|</HTML>||This is trying to inject code for the web page using the user name. If the user name is not sanitized and does not have special characters encoded, this HTML end tag could end the HTML document, leading to page errors.|
|</HTML>||< and > are special character entities in HTML that represent < and >, repectively. So all together, when rendered as part of an HTML document, this would print "</HTML>" Although this would look similar to the previous </HTML> entry, it would be unlikely to cause problems as the symbols are not interpreted if encoded as special entities.|
|OkThisIsKindOfConfusingButIt's <LessThan\ForwardSlashHTML GreaterThanActualGreaterThan Symbol>Yes,ThatWasAllPartOfThe Name,ButSoIs...Ok,LetMeStartOver"|
Namespace Land Rush Cheat Sheet
When a new service appears that lets you register a name, here are some you may want to try and get first:
|<Your usual username, if any>||iPhone|
|<Your given name>||BitCoin|
|<Your full name>||Obama||Canada|
|<Surname>||(Bold & Slightly
|<Name of person who|
runs the service>
|Impossible to Say|
|You||<Name of service>||KrisasinHemsworth|
|Misc||Permissive Character Sets|
|<Single Letters>||<Space>||@ é | “ ”|
|<Single Numbers>||<NBSP>||\ . # " '|
|<Common Words>||<RTL override>||– - _ / ` ' `|
|<SQL/JS Injection>||<Any emoji>||","||&NBSP;|
add a comment! ⋅ add a topic (use sparingly)! ⋅ refresh comments!