If you haven't already, you should take a look at the Friend of a Friend project.
While it does define a simple "knows" relationship for bootstrapping, it's all about implicit relationships like coauthorship, codepictions and colocations.
Instead of the data itself - biometric or otherwise - how about just a digest of some sort?
You wouldn't need to have your data in a central registry, just go to, say, your doctor or another trusted intermediary, have your essentials scanned and the checksum/digest computed. This would then be put on the card and into a central database.
Should you be required to identify yourself to someone, they would have to scan you and compare the digest to the one on the card and checking for existence in the central database.
Nothing to lose, and identity theft would be impossible (although kidnapping wouldn't).
Re:This is a pretty good book
on
Perl & XML
·
· Score: 1
> Another small gripe was that it covered parsing XML in far greater detail than generating XML (which was my task at the time I bought the book). I haven't read the book, but that is also my concern (also at the moment).
Why is it that libxml2 has several parser options, including DOM and SAX, but only on writing option - generating a complete tree in main memory before writing it out to a file?!?
Like XML::Writer can, it must be possible to create an interface that, while still validating stuff like closing the correct elements, doesn't have to keep it all in memory.
This reminds me of one of my first experiences on the Internet. This was before Web took off, and e-mail was (still is?) the killer application.
It was a service called "The Internet Oracle".
You mailed a question to a specific address, and in return you would first get a question from *someone else*, which you would then have to answer before you would get your own answer.
I think there was some moderation and/or meta-moderation, to not let people answer questions with dummy answers.
The idea is almost like having people categorize your image collection. Maybe that would be a new "open-like" access model / license - you contribute one description for which you get to do one search by description?
Actually, this might not be as stupid as it sounds.
If the keyboard picture had the keys swapped to new positions every time, it would be impossible for anything but a camera to deduct the password (as opposed to the vulnerability that makes snooping passwords possible because of the timing between keytrokes).
Of course, it would still be vulnerable to attacks from the person standing behind you...
"Caucasians, Mongoloids and Negroids interbreed more prolifically than any other group of species." I believe the mentioned groups are not different species, otherwise there wouldn't be a need for the word 'race'.
I guess 'race' might be the common word for subspecies.
Even so, our species' name is Homo sapiens sapiens, so that actually indicates that the different races are sub-subspecies...
I don't know what technology ION was (planning on) using, but a company in Denmark, DixaNet, recently folded, after trying to offer the same kinds of service, phone, DSL, fax and various monitoring services.
In Denmark all (including local) calls are metered, and they were trying to offer DSL and non-international calls at a flat-rate, along the tune of $60/mo. - something like half price, even when not making a lot of phone calls.
Apparently they went the dot-bomb way and failed to get second round financing, but it would have been sweet.
Almost everybody could see the fall coming though, it just didn't seem to be a concept that would be able to make ends meet.
While the principle of using ants is hardly news - Dorigo started his more than a decade ago - the use of ant colonies is not suitable for all problems of distributed nature.
I have worked on using ant colonies, basically a variation on Dorigos work, on problems related to floor planning and bin packing (those with danish capabilities could have a look here).
It seems as though the ants are very good at solving the "basic" problems of finding a shortest path, but that the method does not lend well to other optimization problems, even though it may seem that they over time should be able to figure out the best solution.
Routing on the Internet might be a problem that's worth attacking with this method, but aside from the similar issues, I can't see how this would benefit P2P networks.
Attention on the issue rised some years ago, when the parents of a boy wanted to have him named "Christophpher", as opposed to the standard spellings "Christoffer" and "Christopher".
In Denmark the law specifically says that you cannot join two separate sources of data, and the sources themselves are subject to a clause of nescessity, that is, unless you can't do business without, say, the phone number of someone, you can't collect it.
There are no "default" exceptions, not even for the police and such, although it's possible to apply for one, and usually only a one-time permit is given.
And this goes for government agencies as well, which sometimes can be a problem for scientists - just recently it took somebody years to compile a correlation between cancer and the use of cell phones...
This is actually not just something to speculate about - it's already a problem!
Archiving services and institutions have problems with 5 1/4 inch floppies, old cassettes (can YOU still read that old code from your C64?) and tapes from extinct drives.
By now they also have problems with the multitude of different text formats (WP 5.1 anyone?).
Maybe platform independent formats like XML will be the cure...
Slashdot Mirror
If you haven't already, you should take a look at the Friend of a Friend project.
While it does define a simple "knows" relationship for bootstrapping, it's all about implicit relationships like coauthorship, codepictions and colocations.
.. yet he does apparently like trademarking RSS.
Yep, that's a good idea.
Instead of the data itself - biometric or otherwise - how about just a digest of some sort?
You wouldn't need to have your data in a central registry, just go to, say, your doctor or another trusted intermediary, have your essentials scanned and the checksum/digest computed. This would then be put on the card and into a central database.
Should you be required to identify yourself to someone, they would have to scan you and compare the digest to the one on the card and checking for existence in the central database.
Nothing to lose, and identity theft would be impossible (although kidnapping wouldn't).
> Another small gripe was that it covered parsing XML in far greater detail than generating XML (which was my task at the time I bought the book).
I haven't read the book, but that is also my concern (also at the moment).
Why is it that libxml2 has several parser options, including DOM and SAX, but only on writing option - generating a complete tree in main memory before writing it out to a file?!?
Like XML::Writer can, it must be possible to create an interface that, while still validating stuff like closing the correct elements, doesn't have to keep it all in memory.
So, does that mean that Mozilla 1.0 will identify itself as "Mozilla/5.0 (compatible; Mozilla/1.0)"?
That's completely straightforward and reasonable, and will never confuse anyone...
This reminds me of one of my first experiences on the Internet. This was before Web took off, and e-mail was (still is?) the killer application.
It was a service called "The Internet Oracle".
You mailed a question to a specific address, and in return you would first get a question from *someone else*, which you would then have to answer before you would get your own answer.
I think there was some moderation and/or meta-moderation, to not let people answer questions with dummy answers.
The idea is almost like having people categorize your image collection. Maybe that would be a new "open-like" access model / license - you contribute one description for which you get to do one search by description?
Same here. I saw the headline, and thought: Wow!
Does that mean that we're not REAL nerds?!?!?
Actually, this might not be as stupid as it sounds.
If the keyboard picture had the keys swapped to new positions every time, it would be impossible for anything but a camera to deduct the password (as opposed to the vulnerability that makes snooping passwords possible because of the timing between keytrokes).
Of course, it would still be vulnerable to attacks from the person standing behind you...
"Caucasians, Mongoloids and Negroids interbreed more prolifically than any other group of species."
I believe the mentioned groups are not different species, otherwise there wouldn't be a need for the word 'race'.
I guess 'race' might be the common word for subspecies.
Even so, our species' name is Homo sapiens sapiens, so that actually indicates that the different races are sub-subspecies...
will it be relayed live to /.?
broadcast on some live video feed?
ppv?
I don't like this.
Any system that can't spell "42" is not worth it.
I don't know what technology ION was (planning on) using, but a company in Denmark, DixaNet, recently folded, after trying to offer the same kinds of service, phone, DSL, fax and various monitoring services.
In Denmark all (including local) calls are metered, and they were trying to offer DSL and non-international calls at a flat-rate, along the tune of $60/mo. - something like half price, even when not making a lot of phone calls.
Apparently they went the dot-bomb way and failed to get second round financing, but it would have been sweet.
Almost everybody could see the fall coming though, it just didn't seem to be a concept that would be able to make ends meet.
While the principle of using ants is hardly news - Dorigo started his more than a decade ago - the use of ant colonies is not suitable for all problems of distributed nature.
I have worked on using ant colonies, basically a variation on Dorigos work, on problems related to floor planning and bin packing (those with danish capabilities could have a look here).
It seems as though the ants are very good at solving the "basic" problems of finding a shortest path, but that the method does not lend well to other optimization problems, even though it may seem that they over time should be able to figure out the best solution.
Routing on the Internet might be a problem that's worth attacking with this method, but aside from the similar issues, I can't see how this would benefit P2P networks.
Actually it is (also?) the case in Denmark.
Attention on the issue rised some years ago, when the parents of a boy wanted to have him named "Christophpher", as opposed to the standard spellings "Christoffer" and "Christopher".
They didn't get permission...
Another way is to NAT the traffic through, possibly to an unused IP - that's what I'm doing on a 677.
I put it through to my webserver though, so I can run all of those nifty little stat scripts...
mortenf
In Denmark the law specifically says that you cannot join two separate sources of data, and the sources themselves are subject to a clause of nescessity, that is, unless you can't do business without, say, the phone number of someone, you can't collect it.
There are no "default" exceptions, not even for the police and such, although it's possible to apply for one, and usually only a one-time permit is given.
And this goes for government agencies as well, which sometimes can be a problem for scientists - just recently it took somebody years to compile a correlation between cancer and the use of cell phones...
--
This is actually not just something to speculate about - it's already a problem!
Archiving services and institutions have problems with 5 1/4 inch floppies, old cassettes (can YOU still read that old code from your C64?) and tapes from extinct drives.
By now they also have problems with the multitude of different text formats (WP 5.1 anyone?).
Maybe platform independent formats like XML will be the cure...
--