3 ms·

Oh, no ! The cat should have stayed in a box, if this gains too much popularity, HN will read like MySpace back in the days. And top HN news will be: "A brows

• shaunpud 12y ago
  𝓒𝓸𝓸𝓵 𝓼𝓽𝓸𝓻𝔂 𝓫𝓻𝓸
• ceejayoz 12y ago
  Expect subsequent uses of this to get flagkilled into oblivion.
• errnoh 12y ago
  The problem is that this doesn't stop here. This method works everywhere and it will spread. We'll need a plugin to reverse this, anyone up for it?
  • peterwwillis 12y ago
    Go to your browser's menu bar, click 'View', go to 'Character Encoding', and select 'Western (ISO-8859-1)'. Now it's just garbage characters. (It's not reversed, but at least it's not bold?)
• deleted 12y ago
  [deleted]
• floatrock 12y ago
  I saw a thing recently where a unicode encoding trick was used in an oauth phishing scam -- using unicode characters, a scammer was able to make an oauth connector that looked like the real company but passed through the company's "if (oauthConnector.name.toLowercase().contains('our name')) { throw new DenyError();}" check. The user though the oauth app was legit because it was the "same" as the company name, accepted the connection, and promptly had their account emptied: https://www.reddit.com/r/Bitcoin/comments/2lt76n/warning_coinbase_oauth_phishing_attack_allows/ https://www.reddit.com/r/Bitcoin/comments/2lt76n/warning_coi... Now, it's up for debate whether any (psuedo?) financial institution should offer full oauth access (at least without having a human review possible oauth connectors), but the point is, decorative hackernews submissions are the least malicious use of this trick.