Low surrogate char without a preceeding high surrogate char at index: 9. Check that the string is encoded properly.
It seems like Unicode support is still broken in many places.
Chrome 43.0.2357.130 on Debian Sid. You'd think this sort of thing was rare but IME it's commonplace, not least because the average user doesn't really understand font rendering. For example I have no clue where in the stack the error that's causing me to see two rectangles is, and no motivation to sift through arcane documentation to try to sort it out.
i made http://👿.shizz.it
Original url : https://www.youtube.com/watch?v=dQw4w9WgXcQ
Linkmoji url : http://🍕💩.ws/🍍📦🏂🎈🎾🔑
After following the link : https://www.youtube.com/watch?v=dqw4w9wgxcq
And then you get a 404 not found
you have rick astley!
http://🍕💩.ws/🎉🐴🌊🍔💣🍊 should redirect to http://🍕💩.ws/
"Check out my website http://🍕💩.ws/ Got problem typing it? Scan QR code!".
Maybe I can still prank someone by emailing them the link and telling them to msg it to me? ...
i wrote this link shortener... similar idea, but you actually get to choose your emoji mix... which i call a shizz
lemme know what you think! try it out... i think its a little buggy.. i had major challenges getting utf-8 stream encoding working properly on my AWS image with MySQL, but it mostly works :)
i just created http://👿.shizz.it
try going there!
eric, would you like to collaborate?
Like, andrew.💩 ?
There's nothing technically stopping an emoji TLD - after all, .香港 exists.
and so you saw http://💩.la
that was my inspiration for http://shizz.it
shizz.it allows people to create http://👿.shizz.it or any other emoji character mix, as a subdomain, which is then redirected to any other URL. Thus link forwarding.
By making use of emoji in subdomains, you can get around the restriction of no emoji in domains or TLDs.
If the domain is what surprises you, that's not new. Internationalised Domain Names have been around for a while now, and support any Unicode character (with registrar restrictions to prevent phishing etc.)
More importantly, shortened URL's are harmful.
They are brokered through an intermediate site which could disappear or otherwise exhibit amnesia.
They can also be used to cloak links to harmful sites.
If criminals buy the domain, they can re-write the database of shortened links to go elsewhere, like to their harmful sites.
You mean that if I know of a malicious URL, I somehow cannot shorten it using this website, because it is contrary to its "intent"?