From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] off topic: full unicode support isn't easy
Date: Wed, 24 Jul 2013 01:09:41 -0400 [thread overview]
Message-ID: <e2fb870296da3e564ea1eea95700bd08@kw.quanstro.net> (raw)
In-Reply-To: <201307240259.r6O2xWGj003062@skeeve.com>
On Tue Jul 23 23:16:14 EDT 2013, arnold@skeeve.com wrote:
> FYI
>
> Creative usernames and Spotify account hijacking
> http://labs.spotify.com/2013/06/18/creative-usernames/
i took a different lessons.
0. uncode support isn't binary. one might reasonably support a subset.
(i wonder if they'd let me have “0021bf upwards harpoon with barb leftwards”
as a user name? would it serve any business purpose?)
1. it's important to write down what the requirements really are especially
when relying on external code to get it done. better yet, have the code check the
requirements are met.
- erik
next prev parent reply other threads:[~2013-07-24 5:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 2:59 Aharon Robbins
2013-07-24 5:09 ` erik quanstrom [this message]
2013-07-24 21:38 ` Steffen Daode Nurpmeso
2013-07-24 23:55 ` erik quanstrom
2013-07-24 14:12 ` Kurt H Maier
2013-07-24 15:07 ` Steffen Daode Nurpmeso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e2fb870296da3e564ea1eea95700bd08@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).