I was at Macworld yesterday — but I’m in the same group as Doc’s committed Mac-friend – I require a PCMCIA slot on my Mac laptop for, among other things, and EVDO card and some other stuff. I was also very disappointed to see Apple move on to some new PC card standard I’ve never heard of and removing the standard PC Card slot from the new 15-inch MacBook. Yup, I’m feeling a bit left behind by my favorite partner – sigh!
Category: Web/Tech
Xbox Curiousity
I found it curious yesterday in the Sunday newspaper supplements that all of the front page Xbox ads from the big box and other major retailers featuring the Xbox branding — without any mention of Microsoft. Similarly, check out the Xbox web site.
Obviously, this is a very conscious decision — Microsoft spends a fortune on PR, strategy, etc. — but also a curious one. Frankly, I never understood the Xbox branding to begin with — other than the fact that Nintendo and PlayStation were already taken! 😉
Days of Our Lives: FolderShare
I’m a Mac user, having given up on Windows almost exactly two years ago and never looked back. Oh, how I wish that were completely true.
The dirty little secret is that up until a few weeks ago, I need to continue to run Windows (under Virtual PC on my Mac) mostly to use a piece of collaboration software – called Groove – that we had come to depend upon. Oh, how I wish that were completely true.
The other dirty little secret is that I’ve also needed to run Windows to be able to use Intuit’s Quickbooks Online – which, most unfortunately, was written to require Windows and Internet Explorer as a result of its use of an unfortunate technology, ActiveX. One of these days Intuit might get with the program and shed such an unfortunate technical dependency, what with AJAX and all.
Anyway, Microsoft bought Groove a while back, picking up now CTO Ray Ozzie in the process. For a number of reasons, we concluded earlier this year that it was time to abandon Groove, a thick client in every meaning of that word and way too thick for us. We moved to it in a terribly weak moment a couple of years back. Basically, all we need is a nifty cross-platform file sharing mechanism and we thought we’d found that in FolderShare.
So what happened today? Microsoft bought FolderShare, saying how it was going to become a part of Windows Live. Jeez, just what we’ve been waiting for.
Anybody out there interested in starting another cross-platform file sharing company? I suspect we’ll be looking for a new home relatively soon. Or, maybe I can just sign up for Flickr Pro and just make my files look like JPEG’s instead? Or, wait for GoogleBase?
Walled Gardens
Reading Dave Winer’s rant this morning got me off my duff and posting again. Things have felt really hectic on the day job front and, as a result, essentially all of my posting activity has been over on my day job blog Payments News, not here, for the last three weeks. Indeed, I was even too tired to make it to Mike Arrington’s latest Friday night bash where Dave provided some words of encouragement to the assembled clan.
To me, Dave’s post is all about inclusion and about not working in walled gardens. Indeed, it’s about not even thinking of erecting walls around the gardens we build. Yet, we have walled gardens all around us. Sometimes the walls come down (e.g., the Carterfone decision); mostly new walls go up (e.g., eBay’s just announced Safe Payments Policy that appears designed to keep any new PayPal-like entrant outside the eBay garden or when the New York Times moved some of its choice content behind a new Select wall). VCs have historically looked for big walled gardens — called barriers to entry — although even that seems to be changing.
Seems like walls tend to go up a lot more often (and easily) than walls come down. Then, once you’ve built a wall, you seem to invest a lot of energy in tending to the wall itself perhaps even to the detriment of the garden blooming inside. Indeed, you almost never will tear that wall down of your own volition — even if the garden inside is dying or has already died. It’s only when you’re forced to tear the wall down that it actually falls.
One of the great things about the web to date has been a relative lack of wall building, even by those who could easily have done so. For example, Netscape (with some excellent friends) developed SSL – the key protocol enabling secure communications on the Internet — and gave it away to the community. Dave himself did the same with RSS, enabling all manner of new forms of information distribution to emerge and new millions to be made by others.
This could be changing — or maybe not. Maybe it’s just the usual ebb and flow of business?
There was a Wall St. Journal story last week about how the wireless carriers and telcos were working on plans to restrict the Internet network pipes they sell to customers from being able to support voice over IP telephony traffic — because of the threat it represents to their core business. We’ve got a big set of walls surrounding the cellular carriers — where a Carterfone 2.0 decision is sorely needed. And, the already mentioned the eBay example of limiting payment choices and the New York Times locking up content. Indeed, theres some irony in these examples: limitations on Internet telephony would impact the success of eBay’s recent acquisition of Skype!
Most of us really enjoy the gardening, not the wall building or the wall tearing down, and Dave’s clearly a gardener, at least much of the time. Some great fortunes have been made by those wall builders who knew just where and when to erect their walls. Some great reputations have been earned by gardeners who chose not to erect new walls but who propagated their plants and encouraged others to stand on their shoulders. Do you toil for money or for love?
Which are you? Hoe in hand, or brick? New mantra: “Do no evil, build no walls”?
Pondering Digital Identity
Identity is a very noisy space, but, sadly, one in which little actually gets done beyond all the blather. And, oh, is there blather.
For the last couple of years there’s been a fall conference on digital identity stuff. Phil Windley and others are holding an Internet Identity Workshop in Berkeley later this month. Kim Cameron has his Laws of Identity – but he’s overlooked the law of lack of progress! Sxip’s Dick Hardt has a beautiful presentation on Identity 2.0 that’s sweeping the web. Sixapart developed TypeKey to simply deal with comment spam. InfoCards are coming in Window Vista, whenever that might be ready for primetime.
In an earlier post today, I closed by asking whether the emergence of a viable digital identity system for the web might be Web 2.0’s parallel to what SSL enabled for Web 1.0.
Recently, when Google opened up Gmail for general enrollment, they required you to provide a mobile phone number as part of your personal registration information. They send you a text message with a code in it that you need to bring back to their site to complete registration. They say they’re using the phone number as a mechanism to limit the number of Gmail accounts (10 max) that any one person can sign up for, but in the future they could be doing other things too.
I bring this up because Gmail is a great example of a web application that could have (*would love to have*) relied on an existing, trusted digital identity infrastructure for new user enrollment – if such a digital identity infrastructure actually existed.
And that’s the basic problem: getting something that’s trustable, reliable, and user controllable into the user’s hands — the electronic equivalent of my photo ID driver’s license or my passport. There are so many relying party wannabees…yes, maybe even Google. That side of the digital identity “chicken and egg” certainly isn’t the problem.
So, what is it that Google really wants to know about me before they give me a Gmail account? How is what Google wants (actually, needs) to know about me different from what my bank or brokerage or mortgage company needs to know?
They all want to rely on someone else (who they trust) to step forward on my behalf and declare that, yes indeed, this interaction is being driven by the person they know as Scott. But why would anyone want to provide such a service to others on my behalf? Said, perhaps more bluntly, what’s in it for them?
With a driver’s license, my state’s DMV doesn’t take any risk if some arbitrary third party (the local liquor store) decides to sell me a bottle of vodka based upon the credential the DMV issued to me literally years ago. There’s nothing in my booze purchase transaction for the DMV — no upside but, perhaps more importantly in terms of liability concerns, also no downside.
An analogy (always dangerous!) comes to mind. If I apply to open a credit card account, who does the card issuer rely on to make the decision whether to issue me a new credit card? As part of the application process, I supply the issuer with lots of personal information about me. But, of course, they can’t know whether it’s right or not. So, what do they do? They ask somebody else – specifically, a credit bureau – what they know about me. Am I a good guy? Do I have a history of paying my bills? Based upon what the credit bureau tells them about me, they just might issue me a new credit card.
If, subsequently, I turn out to be a dead beat and stiff them for the credit they’ve granted me, do they have any recourse to the credit bureau who sorta vouched for me during the application process? Let’s be very clear: NO! Similarly, if I was an identity thief and just impersonating another identity, does the credit bureau bear any risk of loss? Nope.
Why do we need credit bureaus? Because they provide a broad view of consumer behavior that’s very useful in making decisions to grant credit. And, let’s face the music, because for some things (like extending more credit) you just can’t trust what the individual says about themselves!
Back to digital identity…who’s my identity bureau on the Internet? Who’s willing to vouch for me to arbitrary third parties?
[More to come…]
Seems to me that Tim O’Reilly’s look at what he (and others) are calling Web 2.0 overlooks perhaps the most important contribution that Netscape (and others) made during the 1.0 era:
SSL.
Initially developed by Netscape (beginning just eleven years ago) and contributed to the Internet standards process and the public domain, SSL enabled users to trust the security of their browser sessions. Without SSL (or, perhaps even worse, with an SSL developed and held captive by an intellectual property hungry company), the web’s first ten years of evolution would have been very different indeed.
So, what’s the right way to complete the metaphor: SSL is to Web 1.0 as ??? is to Web 2.0? Is that missing link identity-related?
A Call In Time
I’ve had my frustrations with Verizon Wireless, but it’s great to see them participating (along with NeuStar and the other major wireless carriers) in the Hurricane Katrina disaster relief effort using their network and systems.
A Maturity Model for Privacy
Kim Cameron links to Toby Stevens and his new blog on privacy, identity and security. He discusses a maturity model for privacy which is very much along the same lines as the notion of personal data stewardship that I discussed earlier.
Flock and TiddlyWiki
Let’s hope that Flock works tightly with TiddlyWiki, avoiding the need to separately save changes and just enabling local user TiddlyWiki’s with built-in persistent storage.
You must be logged in to post a comment.