By "encrypted filenames" what people are clearly talking about is making it so unauthorized people can not infer from the filename of a password file what website that password is for.
For instance, to store the password for www.example.com, the filename could be derived by encrypting the website name (www.example.com) with AES using the user's master password, base 64 encoding the output, and using that for the filename.
Filenames readable in cleartext is a security issue. This means whoever has access to your files knows you have accounts on certain websites they are looking for.
I was about to say it may have something to do with the fact that they're separate letters in other languages, like in Polish ą is a different letter, as are ć and ź. It may have something to do, though, with the fact that the ą sounds very similar to a, but ć and ź sound much different from c and z. (I'm only speaking from my very limited knowledge of Polish, I'm not sure about other languages.)
Nope, ą is more similar to 'o' than 'a', and this is seen very often in how kids write words like 'mówią' as 'mówio'
From wikipedia:
Originally ą was a nasal a but in modern times the pronunciation of this vowel has shifted to a nasal o sound. It is most commonly pronounced as /ɔw̃/, /ɔn/, /ɔm/.
Very cool. However, many times it doesn't work well for HN. I've gone straight to a site from an HN post (like this post's[0] site[1]) and it doesn't show the HN post.
Touch-typing on any little keyboard like that is near impossible. On a normal keyboard, you're moving multiple fingers short distances. While on a little keyboard you're moving two fingers longer distances (key-wise, not actual distance). This makes it much harder to touch type since it's harder to judge where your fingers have to go.
This is at least my experience with little cellphone hard-keyboards, maybe it's different for others.
Regardless, braille would be really cool. Assuming the screens were high enough resolution (that is, could raise itself up accurately enough to make small dots) to display it.
I've taught myself to type without looking on my Android (holding it portrait too, not landscape). I do rely pretty heavily on the auto-correct feature to help prevent gibberish, though.
Braille would be easy to implement too, both Android and iOS control fonts at the system level (well, usually on Android) so all you have to do is add a Braille font and you're done.
A brain____ macro language and interpreter[0]. I've always really liked Brain____ and I wanted to make it easier to program in, and this is my attempt at that (still pretty early release, kinda buggy).
