Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Try ?authuser=2 instead of /u/2, that works with some Google products where /u/x doesn't.

edit: doesn't seem to work, it just redirects to /u/2 anyway



sort by: page size:


I set up \/ to be ¯\_(?)_/¯ on my iPhone and laptop via a dictionary replacement. Non technical and persists across multiple devices.

You can also just use Unicode values. See the icons on the blog page.

So something like "ģ" or "\0123" will also work.


Maybe >(Unicode 0xFF1/>) would be a good substitute?

Side by side: >>



https://github.com/google/open-location-code/wiki/Evaluation...

One of the design decisions was to avoid ambiguous characters, so that cuts out at least 9 (I1L 0OB8).



In default it doesn't work well with non-ASCII characters.

https://ed-von-schleck.github.io/shoco/#how-it-works



I'm disappointed we didn't use ASCII-separated values.

https://news.ycombinator.com/item?id=7474600



The so-called-better-way of doing this using Unicode substitution can be found at http://smartdata.cs.unibo.it/watermark/

wouldn't you end up with the 'xn--' ascii expansion in the url window?

Let's use UTF-16: http://en.wikipedia.org/wiki/UTF-16. Problem solved.

thanks, tried it, but it has a problem with Unicode URL's unless there is some setting I'm missing.

Reminds me of the Spotify unicode username issue[1]. Where a function assumed to be idempotent (think tolower(username)) actually wasn't with certain unicode inputs. Allowing account takeovers.

[1] https://labs.spotify.com/2013/06/18/creative-usernames/


https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...

Long story short use a text field that takes UTF-8.



You could, of course, also use the hex representation of the ascii url to obscure it: http://www.google.com/finance/url?sa=D&q=%68%74%74%70%3a...
next

Legal | privacy