Upon2020 (archive)

Hmm, so that’s what I am… an interesting combination ;-) Here’s today’s quote: The very skeptical and well-informed Johannes Ernst (of LID), whose opinion means a lot to me, thinks it makes sense, but when he says "InfoCard will be anchored pretty deeply inside the Windows OS in a secure process space," I worry how…

The beginnings of a definition for a future LID 2.0 are in the Wiki at http://lid.netmesh.org/wiki/index.php/LID_2.0. Apart from a number of housekeeping items (clarifying, further simplifying the spec …) the fundamental new idea is to break LID into profiles. Anybody implementing LID thus can pick and choose which profiles they like to implement. That way,…

Migrating from C to C++ back then, we all had to get used to the this pointer. The this pointer, of course, identifies the object that is supposed to perform the service that we requested. It must have been a good idea, because these days, it’s pretty much in all programming languages (even in Perl!).…

He says: Some folks over at LiveJournal have come up with a single sign-on system called OpenID. It’s a lot like a subset of LID, and I’m not terribly excited about it because it seems to be a big step backwards in many ways, To which I might add: it also seems more complex to…

How does single-sign-on (SSO) look for a representational state transfer (REST) architecture? I began asking myself that question a couple of months ago when people started pointing out to me that LID was very REST-ful. The SSO idea is typically defined in terms of "applications": sign-on once, use many applications without having to sign-on again.…