3 ms·
http://jerf.org is my OpenID, and will be until I no longer have the domain. This is precisely my problem. I don't want to commit to maintaining a webpage at
by mechanical_fish 16y ago
http://jerf.org is my OpenID, and will be until I no longer have the domain.
This is precisely my problem. I don't want to commit to maintaining a webpage at a given domain with a given set of headers for the rest of my life.
Imagine if OpenID had been designed in 1991. Perhaps it would have been called "GopherID". And I might still have my GopherID from 1991, provided I had kept up the Gopher server that was delegating it, and could find another (trustworthy!) person on this Earth who would bother to operate a reliable GopherID server eighteen years after it mattered.
You see the problem? The web is barely old enough to vote. Any identity that ties me to some web standard of 2010 is as ephemeral as the morning dew, eight-track tapes, and the Commodore 64 floppy disk.
Meanwhile, I just visited Slashdot for the first time in years. My user ID is only three digits, but my login still works. It's a username and a password, it's built out of text, the protocol is obvious, and it's going to work as long as Slashdot works.
- vog 16y agoand it's going to work as long as Slashdot works This would be true as well if you'd use OpenID. OpenID dies when HTTP web services die, but then Slashdot will die, too.