1,074 karma · joined July 2, 2016
http://www.art.net/studios/Hackers/Hopkins/Don/hyperlook/ind...
i.e. 1. e4 e5 2. Qh5 Ke7 3. Qxe5#
When visiting the page (at least on Firefox), the location bar displays the intended characters, but when copying it you get the percent-encoded form. If the reason for percent-encoding was just to make scams more obvious, shouldn't the form shown in the browser interface also be URL-encoded?
By the way, it seems like that is a much stronger argument when applied to domian names than when applied to the part of the URL after the slash.
Which just goes to show that many Americans aren't really aware of how the Soviets were crucial to winning that war.
- If the same domain name but with a more popular TLD exists, people might accidentally go there instead.
- Some outdated validation code (such as a regex to match valid email addresses) might not recognize the TLD, especially if it's one of the long ones. I'm not sure if this problem actually exists, but it could.
Hwæt, weardmann! Hwæt is sēo ġedrēfednes?
http://hn.algolia.com/api/v1/search?query=bar&restrictSearch...
Maybe it's something related to Base58 format, which seems to be common for bitcoin keys? If it's Base58, then it should not contain the characters 0, O, 1, or I.
I'm assuming it works the same way as for errors involving fiat currency, but I'm not clear on what the law says in that situation either.
For the full discussion: https://meta.wikimedia.org/wiki/Wikimedia_Forum#Freenode_(IR...