2005-11-07

idea note - simple passwords, redundant information and interface


From: Caue Rego Mailed-By: optimumisp.com
To: caue.cavalheiro@gmail.com
Date: Sep 21, 2005 10:39 AM
Subject: idea note - simple passwords, redundant information and interface
Reply | Reply to all | Forward | Print | Add sender to Contacts list | Trash this message | Report phishing | Show original | Message text garbled?
Simple Passwords
Put in all passwords in one place on the computer desktop, or maybe a usb removable drive, with one specific password for each specific thing.
Then, you just need 1 global password and everything else you need will be already logged in as you.
Although this IS a tricky part to program / to do, it's also the most obvious.

Now the nice thing is once you remove the drive or if you click to lock passwords, the program don't know the passwords anymore.
So you'd have to type each specific password if you need to get in some restrict area.

This couldn't be a simple program. It might even require a new OS from scratch, and still be not complete, since I mean EVERY password.


Redundant Information
And the same idea could apply to ANY redundant information, like address and filling up some forms.
The default OS configuration will save most information you type in any place.
If you get to any similar place you'll be asked if you want THAT place to be filled with prior information.
If you choose yes, next time there's no question for any other time you need THAT information to be filled in (not only in the same place)
And then, if you don't want to be filled, you can choose to "unfill".

If you type a different data for the same kind of information, you'll have two profiles.

Now, this asking interface should be smooth, show relevant data about the information about to be filled in.
And it is a nameless profile, even when it's multiple, although a name can be filled if wanted.
This should apply not only to internet, but to anything in the OS.


Interface
It shouldn't be using TABs or Buttons with windows.
Each setting should be associated to words and to each other.
And it should be graphical like a web.

If you choose one word, you can see how many and which settings are associated to it.
Same thing goes for choosing a setting. And, since it's a web, you can also see all associated settings.
If there is one setting with no association with all others, that's just a different web.
If eventually one setting is not associated with any other, it can belong to the same web through a keyword.
The web graphical interface is important to visualize all this and how it's organized.
And this is so easy to think of how it's done inside a database.

And you can choose a categorized regular list if you want to. But the web is default.



--comming more soon--


-- caue.rego@gmail.com