Skip to main content

A System to reduce personal data redundancy

I have a problem. A simple problem. If I am allowed to sit tight in a corner with nothing to do, I start thinking of new ideas. Now the problem is I dont know how to continue working on those ideas.
The idea I got this time is quite a neat one, I mean it, a seriously neat one.


How many times do, you, as a net-aholic type in your personal details. Your name, address, DOB. etc. Of course this time could have been saved to do something more useful (like reading more blogs :-) ). Now imagine you shift to a different place of residence..... Further, you decide to give up your christened name and decide to rename yourself, after being inspired by that guy/gal you saw in the theatre. How many sites do you have to update??? How many days do you have to spend????? (Unless of course you still use that old style of shopping, I mean the manual one, which includes walking). The number of days you spend can be considered to be down time(as in the time wasted on a computer while installing maybe an OS).

What if this time could be saved after all.
What i a solution to all this was found. What if a system was designed which does this for you. No, I am not talking about robots which manually change the address at each and every site.
I am talking about a system brought about by a company which stores all the required information in a single central repository. All other systems which require it (meaning banks, shopping sites,etc.), would have to just securely connect to the system, retrieve the data(which it is authorized to have) whenever required.
Imagine the redundancy and associated problems that is reduced. All the user will have to do will be to update this central repository when he changes his name, address etc.
To authorize a site to have certain data all he should do will be:
2 options over here
1. Login to the central repository, and command the system to give only certain details to the site.
2. Login to the central repostiory, and generate a key which when passed to the site authorizes it to retrieve certain contents, from the repostiory.
Of course in both cases the Login will have to be done securely.
Sounds good???? Sounds good to me. Guess the world is waiting for me to come up with the company to manage this central repository. But who knows..........................



Comments

Rakesh Pai said…
This is what the Microsoft's Passport does. But, for good reason, it is not such a great idea if you look at it under the surface. How much information are you willing to put on a central repository? Who gets the rights to scan these lists? What about privacy issues? Will you be comfortable putting your credit card number on a central repository?
The Internet as we know it today was born out of decentralization of hardware, processing and data-storage. We should respect that, and infact further it. Centralizing data is not only tedious (data redudancy is not always a bad thing), it is also very risky.
That said, your problem is a genuine one, and a solution is probably the need of the hour, considering that we seem to be filling endless forms online and we ourselves are responsible for the "freshness" of this data. It's only that maintaining a central repository is not the solution. There has to be some other solution to this problem. I think this solution will come in the form of some sort of local browser-level password/information management, and not some server/service based technology.

Popular posts from this blog

Theming in Whidbey using CSS

Continuing my blog titled Themes in Whidbey . I would like to mention some great points I did find out today about Whidbey featrures. How many times have you got sick of developing Sites which have themes???? I mean every page u create has to have, maybe in ASP, something like <link href="<%=Session["ThemeFile"]%>.css"/> I have been doing since a long time. Do mention if you have a simpler method of defining a variable CSS for your page!!! Whidbey simplifies this further. Now in ASP.NET, all you will have to do is Create Themes directory, if not aldready present, Create a directory for each theme required, maybe Black, Gray,etc. Dump your CSS files into this directory. in Page_PreInit method define the Theme as Page.Theme="<Theme directory Name>". Further can be made into Page.Theme=(string)Session["ThemeType"] and viola, your theme management is take care by ASP.NET When you want to change the theme, the...

B.O.F.H.

Was browsing the net, and found some old link to BOFH. Not sure as to how many used to read PCQuest some time back when it used to come, but i remember reading them, with of course re-reads and re-re,etc...i can go on you know. Anyway, it's about a system operator who is bugged by no-brainers asking silly computer related queries, and this guy repling with wierd answers. I had never known the origin of this character, until i saw this . Anyway for those who have never read BOFH, here are two of them.