Slashdot Mirror

but how can a touch interface differentiate between rolling over a button versus of clicking it?

They can't regardless of the choice of Flash or HTML5. But can you show a public example of an SWF where this distinction (hover with click vs. hover with no click) is necessary for navigation, other than a tech demo?

If most of them now need to be re-written to support an interface paradigm that is in essence incompatible with a touch interface

The fans of Flash on mobile would claim that not all existing SWF objects out there require hover. For example, the "play" button on a web cartoon does not: when the user taps the digitizer, just send the mouseover event followed by the click event and the SWF object will behave. Those existing Flash applications that do require hover at the moment can be tweaked, not completely rewritten, to support hover-free interaction, with the obvious exception of a tech demo of goal-crossing interaction.

this has been around for a little while already... http://www.dontclick.it/

Passwords can still play a role, the problem has always been user stupidity and convenience vs security. We always love to save time and anything that requires less effort = good for us, but at the expense of being less secure. Moving security to invisible layers is just asking for abuse by authorities, as if they didn't have enough power already via MAC address + ip binding in being able to track down and identify users by merely tooling around with the equipment right at the ISP end.

My bank uses multiple authentication using personal questions which I would only know the answer to and if you get the question wrong just once, it flags the account. The big problem is the amount of retries, you can't guess or brute force passwords on accounts that will lock after the first few failed attempts.

In my opinion it's probably best if we moved to gesturing, I find an interesting site here -
http://www.dontclick.it/

It could serve as an interesting basis for security, i.e. gesturing and opening the correct doors in a maze.

• Videos auto-running
• Random elements zooming around
• Mouseover actions that surprise (I still don't think mainstream WWW pages are ready for a http://www.dontclick.it/ - like UI)

Check out http://dontclick.it/

They have a pretty cool mouse interface that doesn't require any clicking, so (I think) it would avoid CTS.

http://www.dontclick.it/

Concerning (not) Clicking, reminds me of this flash-based demo interface:
http://dontclick.it/ (nomen est omen!)

Have a look here: http://www.dontclick.it/

So basically, we should eliminate the mouse clicks altogether. People who know dontclick.it know what I mean: You could just 'touch' the numbers with the mouse cursor for them to register. That way, the screen logger would have to record an entire video to get the password.

Of course, implementing such a thing without Flash and the likes will be a little more tricky.

Try http://dontclick.it/ The www didn't work for me

Like this...?

Here is the Institute for Interactive Research's example of clickless user interface that I hope more application developers espouse in the future.

this is nice, but requires the mention of http://dontclick.it/ [dontclick.it]

this is nice, but requires the mention of http://dontclick.it/