Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×

Comment Re:Graffiti? (Score 1) 140

graffiti is nice (there are graffiti keyboards for android), but not as fast as good swiping. You want to try swiftkey, then you will never want to use swype again. Swiftkey beats them all at swiping and at good predictions, typos and next word based on previous word. Have a typo in your sentence? Do not bother to set the text mark correctly (which is annoying on android). Just keep backspace pressed (swiftkey goes into "delete whole words" mode), type the word correctly, then touch the correct suggestions instead of typing the rest of the sentence (swiftkey remembers them in a type of markov chain biased to recently typed words). And swiping is just more accurate there.

Comment Re:Not surprising (Score 1) 140

Because you do not type faster, if all the most frequent letters are in the home row. Just try it, type some Text only consisting of the homerow letters, then type some english text. If you are a good typist, the english text will be much faster.

There are several reasons, but for example see typing st, the fingers are one finger away from each other (stopping irritation when the t-finger returns to the home row) and you need to move your finger for the t, which makes it more distinct (try typting stststt and then typing asasasas).

Comment Re:Bullshit detector: ALERT (Score 1) 765

I guess there are some projects full of infantile jokes. Some may be funny, some may be annoying. But if dick jokes are sexist, then against men. But strangly most men are less fanatic about "(s)he's insulting me, i am offended", even when someone jokes about their dongle.
But i think most women are balanced and with a sense of humor, too. The problem is, the annoying ones are the loud ones. Maybe some men are annoying as well ... then the "tasty male tears" reflex of the annoying offended women kicks in and silences them.
Yes, i am annoyed and offended ;).

Comment A Warning should be connected with actual ... (Score 1) 79

consequences.

This means, if i get a TLS-Warning, it's mostly safe to click it away. Usually its a browser to stupid to ship the CACert Certificate.
This is no problem, because the warning is not neccessary, as the site is secured and the access does not need to be encrypted anyway, because i just want to read something. Nevertheless, the browser panics.
Now i come across some confidential page, which wants me to enter my credit card number. Now i need to awake my brain "hey, maybe i do not want to ignore the warning this time".

We need no bigger warnings. Imagine a TLS-Warning with pictures showing somebody robbing your bank account. Okay, you will get used to it and click away the warning anyway. You know the consequences. But you know the ACTUAL consequences, too. And they are "last 1000 times nothing bad happened".

So the answer is: We need less warnings. Do not warn me, that my connection is insecure with CACert. Have a decent notice, that the CA is not trusted, but the connection is encrypted. Warn me, when it's on a bank. Maybe a bank could indicate in DNS, "hey, strong check please", while my homepage which should be encrypted without much authentication can indicate "hey, maybe you do not know my CA, encrypt anyway if somebody reads the request nothing bad will happen".

Slashdot Top Deals

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?

Working...