Digging in the Mud
There’s something about the Diggbroglio that has left me scratching my head: how is it that so many people are up in arms about the DiggBar when they’ve had nothing to say about the framing bars of StumbleUpon, FaceBook, etc. etc.?
Now, please note that I’m not saying the DiggBar, or any other framing bar, is cool and we should all love it. I’m not. I absolutely, completely, totally get all the reasons why framing bars are bad for breaking bookmarking and navigating and search engines and copyright and hijacking content and so on. But that’s precisely why I’m so confused, because we’ve known for years now that framing bars are bad mojo—and yet StumbleUpon, for example, is based on bars. There is a browser extension/plugin StumbleUpon thingy you can install, but there’s also a web-based framing bar thing (see this link, for example) that they offer, and I bet people use. You don’t have to be a member to use it: I hit that link in a browser that allows cross-site frame loading and I get the bar and the page it’s framing, and I’ve never been a StumbleUpon member. The source shows it’s using iframes to make it happen. So far as I can tell, it’s not really different from the DiggBar.
So why do we have people writing JavaScript and PHP and Ged-knows-what-else that specifically busts out of the DiggBar framing, instead of busting out of all framing? After all, site framing is universally agreed to be objectionable; even yet-to-be-discovered life forms orbiting distant stars think it’s a bad idea. So why is one instance of it being targeted while the rest are tolerated? Why are we all not just using if (top != self) {top.location.replace(self.location.href);} and other-language equivalents? Yes, I know, some of you do just that, but why isn’t everyone?
Perhaps because I have yet to eradicate a stubborn streak of faith in the rationality of my peers, I assume that there’s some technical difference here that I’m missing and that, once understood, would let me understand the source of the outcry. So can someone please explain to me, or point at an explanation that states, the technical ways in which the DiggBar is worse enough than already-extant framing bars that it’s triggered this outrage? Again, nobody has to enumerate the complete list of the DiggBar’s sins; I understand. A list of any different and more egregious sins would be just fine, though.
Also, if anyone comes up with a way to bust out of the frames while still preserving the bar—that is, correcting the problems framing bars cause while preserving their functionality for the people who want to use them—that would be extra-cool. After all, people who use those services like the bars. If we could let them browse the web the way they prefer while fixing bookmark/SEO/etc. problems framing bars can cause, that would be a win all the way around.
Update 14 Apr 09: looks like Porter’s trying to keep the bar without the framing.
Update 16 Apr 09: in his post about Digg changing the way the DiggBar will work, John Gruber lists (by way of quoting Digg VP John Quinn’s post about it) the two things that made the DiggBar extra-objectionable (at least in his eyes). Thanks, John!
