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

My first problem with AJAX

I was using Callback (AJAX) to retrieve a page i had developed . Lets start all over, I was using AJAX to retrieve a part of the contents of a web page. Cool, simple, it downloaded without a pain, then I innerHTMLed it to a span tag. Worked fine, successful, clapped my hands etc.etc. Clicked on the button which had seemed to appear out of nowhere. And then, it all fell apart. The feared exclamatory symbol appeared on the status bar.... And for the newbies, thats an indication of a JavaScript error in IE. Of course, as usual i was all curses at my IE window......Anyway to make a long story short (i AM quite sleepy u know). the scripts which i seemed to be innerHTMLing to the span tag are not executed. And what i mean is anything between the script tags which have been innerHTMLed to that span tag are not executed. Of course i can see a ray of hope in the distance. I mean the distance till tomorrow morning. And just for kicks, check out a hi-fundoo flash file titled EPIC 2004 . And for...

Imagine...an internet based world

Was reading "The Google Story", when i got this wierd idea. Consider a stripped down version of Linux, meant only for doing simple things such as browsing the internet, to read from the various drives (which is primarily meant only for storage of personal data), to play music and some single-player games. All the rest provided by the internet. Information searching/Chatting/Mailing/Documentation editing/journal maintenance/daily schedule maintenance/news/rss/shopping, etc. What else will you use for your computer for? Ok, actually i have been working on mainframes for some time now and am getting adjusted to the "dumb terminal" concept. Then i started associating the concept with scenario we are observing all over the net. As a matter of fact this will reduce the power of processing required on the client side also!!! Looks like the world is changing.... for the bettter, yup, i am sure. technorati tags: New internet age , dumb terminal , internet based world

So you have your website deployed in PROD ... now what ??

Posting on behalf of Usr.Web.Speed - My previous job had been to architect and develop websites for various customers. During that time my team and I have architected and developed various web applications mainly for enterprises. (But below info is not restricted to enterprises) Other than the usual development and testing tasks involved, our focus area was to abide by multiple SLAs. One of the primary SLAs was to provide the users of our websites a very low (usually subsecond) response time (or page load time). To adhere to this SLA, we did multiple activities, in code, process as well as infrastructure. These include (but not limit to) - Using best practices including (http://developer.yahoo.com/performance/rules.html) Determining the optimum number of calls to the databases, open connections, etc. Providing the fastest mechanisms to download associated content (such as stylesheets, JS files, etc. over CDN) And debugging the reason for the slowness of the websites, when ...