BoycottSony.us

I decided to keep the Boycott Sony thread alive and well by moving it to its own blog. My intention is to use BoycottSony.us to aggregate information about the Sony DRM brouhaha, other boycott efforts, and maybe a little bit about DRM in general.

I should emphasize one thing: I started this thread from the perspective of a boycott, of totally cutting Sony off until they start treating us with respect. But what this blog will really be about is conversation: people talking to people about what Sony is doing to them and their rights. If Sony wants to join the conversation and talk in earnest to us about what they think they’re doing with their DRM, and more importantly listen to our concerns and take action on them, then I will count that as a victory for this effort.

Incidentally, it’s boycottsony.us because boycottsony.com and boycottsony.net are owned—by Sony.

Thanks, Trend Micro, for your overzealous blockage.

Today’s definition of frustrating is finding out that your company’s new antivirus software considers the eMusic Download Manager to be a “virus” (ok, adware). Especially frustrating since I pay for that service and now can’t use it. The download experience in Firefox is dramatically worse without the download manager, as you lose the option to download a whole album at once; instead you have to click on each song, one at a time.

Emusic is a great service. It’s too bad that someone there made the poor decision of bundling the promo for their service in such a way that it hurts their image and worsens the user experience for their legitimate customers.

Blogging to Manila from Flock.

If this works, I will have successfully blogged from Flock. To get posting to my Manila site working, I had to bypass Flock’s blog autosetup and hand-edit the configuration file, which on my Windows machine is saved in my Documents and Settings directory under Application DataMozillaFlockprofiles[default]blog_alpha.rdf.

The problem with Flock’s autodetection technology is that both the Blogger and Metaweblog API attempt to use the GetUsersBlogs API call, which is not implemented on Manila. All I had to do to get it working, though, was to save a profile that called Blogger using the Metaweblog API, then edit the RDF file to set all the correct user ids and URLs based on my RSD file.

A few things I like about the blog editor—the built-in Flickr topbar is cool, cool, cool. And the UI for the actual editor is pretty nice. I especially like the option to show me the HTML of my post. I have used enough “WYSIWIG” editors that end up generating nasty HTML that I don’t really trust them anymore. —Flock is no exception to this rule, btw; rather than wrapping paragraphs in <p></p>, it ends a paragraph with a <br /><p>. Bad bad bad, particularly if your blog is HTML 4.01 Transitional. But once you drag up the splitbar to get to the raw HTML you can edit to your heart’s content. Which is good, because Flock totally mangles HTML entities. I put a curly quote in the HTML view with & rsquo;, which turned into the proper ’ in the preview; I then went and copied and pasted that into another place in the preview, but it pasted as a high ascii character rather than an HTML entity. Bad, bad, bad. And when you hit Italics in the preview, it formats it as <span style=”font-style: italic;”></span> rather than the more semantic <em></em>. Bad, bad, bad, bad. Forget what I said about the blog editor; it needs work, and I will be posting some bug reports.

Also, the draft functionality is weird. When you save as draft, your post window closes, and you have to open a new blog window, switch to the Draft account, open the Blog topbar, and click on the saved post to get it to open. Then you have to mouse down in the text field to enable the Publish button. Not intuitive.

Flocking, almost.

Flock has launched its public Developer Preview. Congrats to Sloanie Geoffrey Arone and the rest of the Flock team.

I’m playing with the release, but it’s living up to its designation as a developer preview release. For one thing, it doesn’t appear to work with my Manila blog; though the release notes state that it works with Blogger, it doesn’t appear to know how to talk to Manila’s Blogger or Metaweblog APIs, and there’s no UI for blog configuration aside from an autodiscovery engine that doesn’t work for my blog. I will be digging into the developer section and the pref files to see if I can figure out how to get around the autodiscovery feature and make this work with my blog. At a minimum, I would think the web services support would let me talk to the Manila API directly.

We are ALL not consumers.

I’ve been getting an unusually high level of linkage to a post I wrote in July, called “I am not a consumer. I am a human being,” after Doc Searls linked it (and my recent rant about the crippling effects of the c-word) on Saturday. The attention is flattering, but I’m not the first person to express this sentiment. In fact, the web is boiling over with it. A brief survey yields these variants:

  • “I am not a consumer. I am a person. Start treating me like one.” — michaelw
  • “I am not a ‘consumer,’ a ‘recipient’ or any other abstraction. I am I. I am a person, I am a self.” — Harold A. Maio
  • “They do not see us as disabled. They see us as able. I am not a consumer who consumes government aid at exorbitant costs and never improves. My crew and I are producers…” — Bruce Ario
  • “To refer to citizens as ‘consumers’ indicates a pro-business bias.” — Christopher Palms (comment to FTC on Do Not Call registry)
  • “…being American means I am NOT a Consumer above all else.” — Roger Born
  • “I am not a ‘consumer’, I am not a number. I am not a walking wallet for companies and government to fight over. To the corporate heads and government rulers I say ‘HEY! You F**kers work for ME! Remember THAT!’” — “Phugedaboudet”
  • “I am not a consumer of your political products, I am a citizen!” — David Weinberger, cited at Blogads and at GreaterDemocracy
  • “I will not spend my money with a company whose CEO thinks I am nothing but a consumer (I despise that word) of useless media crap from Hollywood and the Copyright Cabal. I am not a consumer. I am a customer. And I will not be treated like a criminal.” — Terry Frazier
  • “I am not a consumer but a reader of books…” — Katherine MacNamara

Point? While there is certainly a fair amount of consumer-label-resentment directed towards the broadband providers, the same backlash is appearing against the music industry, the retail industry (through Amazon), Hollywood, marketers (tele- and otherwise), and the political establishment. That’s a lot of minds to start to shift.

So it’s time to start shifting them, to take the power back.

Update: Doc points out that I missed a very important variation on this, from Cluetrain: “we are not seats or eyeballs or end users or consumers. we are human beings – and our reach exceeds your grasp. deal with it.” Doc: I missed it because that’s written as an image with no alt text, and thus was not turned up in the Google search!!! Irony is alive and well.

Consume, consume, consume

As I’ve mentioned before, I want a moratorium on the word consumer—both because it is disrespectful and because it builds bad thinking habits in companies that sell to “consumers.” Doc Searls’s experience with his local Internet providers today is a case in point:

The bottom line: I can replace my 3Mb/300Kb $49/month Cox home Internet account with a 3Mb/768Kb $29/month Verizon home Internet account. The business account won’t be so easy. First, I have to get a Verizon business phone account, the person on the phone said. Then I have to call a number to see if static IP addresses are available. The number “is experiencing extremely high call volume.” So I gave up.

In the course of talking, way too much, to Verizon and Cox representatives the last few days, it’s clear these kinds of companies simply cannot imagine a world where consumers also produce, where demand also supplies, where the Net is anything other than a new way to deliver the same old crap.

Least of all can they imagine that there is real business in real service to individuals working out of their homes.

It makes me think: First, where is the service offering for geeks? Second, how insidious is this C word that there are not even product offerings to meet the needs of real people for symmetric download/upload speeds? No, all “home users” (my other favorite condescending euphemism for real people) need to do is download other peoples’ stuff.

Easy email to SMS gateway service

This is old news by now, but I found this useful: rather than remembering a multitude of special email addresses to send text messages to friends and colleagues, there is now a service to do it for you: Teleflip. Just send an email to your friend’s phone number at teleflip.com: for the cell number 508-555-1212, that would be 5085551212@teleflip.com.

Why is this easier? For completeness’ sake, here is a list of all the other ways you would have to address said email messages depending on the carrier, assuming you can remember who your friend has for mobile service:

  1. Verizon: 5085551212@vtext.com
  2. Sprint: 5085551212@messaging.sprintpcs.com
  3. Former Nextel: 5085551212@messaging.nextel.com
  4. Cingular: 5085551212@cingularME.com
  5. Former AT&T Wireless subscribers: 5085551212@mmode.com (which used to be 5085551212@mobile.attwireless.net)
  6. T-Mobile: 5085551212@tmomail.net
  7. Virgin Mobile: 5085551212@vmobl.com

Particularly useful, I think, in automating messaging to mobile customer service representatives—all you have to know is the person’s mobile phone number.

The other Weblogs(.com) Acquisition

Congrats to Dave Winer on the acquisition of his groundbreaking weblog ping service, Weblogs.com, by Verisign. This is a Really Big Deal, on a number of levels. Kottke articulates the value to Dave — or rather the liability that is avoided by having someone with deep pockets take on the task of keeping the infrastructure updated.

I think the value to Verisign is the more interesting story. First off, buying into Weblogs.com gives them an instant and important set of data about the blogosphere that includes growth rates, language usage, and a piece of the puzzle in fighting spam blogs. Second, though, there are a ton of services that are built on Weblogs.com and many more that might benefit from knowing which blogs are being updated. I can see (and Verisign acknowledges) that there is a business-to-business transaction model in which Verisign charges for access to things like changes.xml, or charges for aggregated data about participants in the blogosphere. Particularly important is the access that this gives to information about podcasters.

The real question is: is it too late? As I pointed out last year, services like Ping-o-matic have centralized access to the exploding multitude of ping services that are out there (up to 22, from 12 last July). I can see a scenario (particularly the one above) where Verisign makes the wrong move in charging for a formerly free service from Weblogs.com and people (and blogging platforms) stop pinging.

Note to anyone who is interested in the growth of weblogs in general: check my historical record, which spanned from 2001 to 2003. Unfortunately, a recent move of the Weblogs.com server (around August 22) seems to have blown away the historical data on that server for the high water marks.

Redesigns 2: CNet’s News.com: ho-hum design, good blogs

The second notable redesign today is at News.com. Reviewing this design is a little more difficult, because it’s harder to spot what has changed. The yellow is still there, now actually looking a little orange. The front page is still a total mess, and it’s still impossible to find an individual headline there. The URLs are still impossibly long and impossible to remember.

But there are three killer features. The treemap view of the hottest stories on News.com is brilliant, as is its placement as a sidebar on every story. It’s interesting to watch popularity change in real time, too, as the current hottest story (Network feud leads to Net blackout) gets hotter. I hope that CNet thought about the effect that this treemap has on their most viewed statistics, or they might just be getting into a self reinforcing loop here.

The Big Picture is even cooler, at least at first. This moving relationship map between stories is fun to use to explore the Related Stories that CNet has long featured at the bottom of every article. Two things are keeping me from being hyper-enthusiastic about the feature, though. I don’t always understand why the connections are drawn the way they are, or what popularity has to do with the relationship between the stories. Second, like all such spider graphs, the relationships are really hard to read once too many of them appear on screen.

The third feature has the potential to be the most controversial among bloggers. That’s because it’s yet another Top 100 list of blogs that are “worth reading.” The results are interesting, especially the Blog 100 Stream (recent posts from all 100 blogs in river of news format). Even if Fark.com is flooding that river right now. I’d like to see more interactivity though. Agree or disagree? What would have been cool would be if CNet partnered with Bloglines or Kinja to allow readers to build their own lists, not just talk about them.

Final note: I wholeheartedly approve of News.com’s shift in focus from Tech News First to News of Change. In 2005, focusing on technology means focusing on law, politics, and the sciences as well.

In fact, the only obviously dumb move I see from this redesign is the My News feature. I’m not going to take the time to customize my view of News.com, folks. I’m putting that time into my RSS reader instead, because the payback is better.

Overall score: Intentions A, execution B+. Great features, but the basic page design, particularly on the home page, could still improve to make finding information easier.

Redesigns Part 1: Salon misses an opportunity

Two big sites unveiled new designs today. Salon (as pointed to by BoingBoing) and CNET’s News.com both rolled out new user interfaces. I’m a little mixed on the design effectiveness of both, but there are a few interesting corners in the mix too. I’ll write a quick post on CNET but want to focus on Salon’s moves now, because frankly they annoy me more.

First the graphic identity. It’s cleaner, but some of the elements, particularly on the front page, appear unanchored and somehow floating—as though the former black boxes of the design were containing the content and it’s now just kind of drifting around the page. There’s not a good sense of an underlying grid. Take a look at the community sidebar for an example—it seems to bear little relation to what’s going on around it. I’m also getting lost in the headlines on the left—too much bold text, not enough visual separation or something. It’s hard to scan. Finally, the new design and branding doesn’t carry through to all the content, particularly Audiofile. Visual design: A for intentions, B- for execution.

I also don’t appreciate the “ghetto-ization” of Salon’s blogs, which are now (especially Audiofile and War Room) the major daily draw for me. While they’ve moved into the main column and feature updated headlines, they’re only small text links in a mass of illustrated spots and thus easy to overlook. Don’t get me wrong, I enjoy Salon’s other articles. I still click through on the RSS feed for some other articles, such as today’s Fall of the Rovean Empire by Sidney Blumenthal and last week’s article on the implications of the Vatican’s crackdown on homosexuality in seminaries. But for me Salon’s steady, unglamorous RSS feed (OK, it’s actually RDF) is much better at making their content findable than the redesign. And the link to the RSS feed is now gone from the front page! It’s not even in the meta tags, so you can’t use autodiscovery. This is brain dead. Discoverability: intentions A, execution D.

Finally, functionality. I like the addition of the font size controls and the print and email links. But they aren’t on pages that don’t have the new design. Intention B+ (page tools are ok but not revolutionary, really. How about telling us about your most emailed articles with those stats you’re collecting through Hotbox?) and execution A-.

Overall score: intentions A, execution C-. Not a good way to start your next ten years, folks.

CSS bonanza

A trifecta of interesting CSS links in my aggregator this morning. First, Luke Melia points to an interesting post about maintainable CSS, and proposes modular CSS and Dave Hyatt’s rules for CSS use in Mozilla skins as possible solutions. For myself, I lean toward the former approach; I separated structural markup (the definition of header and sidebar boxes) from presentation markup (type and colors) within different sections of my stylesheet when I was doing the first round of design improvements. Other interesting solutions in the comments to Simon’s post, including this article from Digital Web Magazine about Architecting CSS.

Second, A List Apart provides six methods, of varying degrees of semantic correctness and coolness, for achieving multi-column lists with various combinations of XHTML, CSS, and JavaScript.

Third, ALA also talks about the multi-column module in CSS3, and introduces a Javascript parser for the CSS syntax that helps bootstrap the new capabilities in browsers that don’t yet support the extensions. You have to see some of the examples, particularly numbers 2 and 5, to get why this is so cool, but once you do it’ll make you swear off long scrolling layouts forever.

God(casting) Part II: Old South sermons

Following up on the Godcasting meme, my church, Old South in Boston, has started making MP3s of sermons available for download. No RSS feed—the website has no back end publishing system aside from an overworked webmaster—but the content is there.

In fact, I went ahead and scratch-built an RSS file for the content using FeedForAll, so subscribe away: XML. If/when the file moves off this server to Old South’s, I’ll post a standard RSS redirect there instead.

Update: As of 4 pm on Monday afternoon, there’s a big ol’ XML link on the Sermons page. My feed now redirects to the official one. Cheers to Evan, the Old South webmaster, for acting so quickly.

On tech support and 240-volt shorts

As I noted this morning, my luggage didn’t accompany me across the Atlantic yesterday—in fact, the Lufthansa representative at the baggage claim noted unapologetically that “more than half the bags on this flight didn’t make it aboard.” I’m not entirely sure how that happens, but in my case it might be because I checked into Terminal 1 at the Flüghafen in München rather than Terminal 2 where my flight departed. In my defense, I had no idea that I was in Terminal 1 at the time—there was no signage indicating the fact when I came up from the S-bahn.

At any rate, my luggage is here now, and about damned time as my only cell phone charger is in the suitcase. On to other problems: my laptop.

As previously written, my work laptop let its smoke out last week owing to an accident with a high-voltage outlet. Today Dell’s tech support came to fix it—as I watched, the guy took apart the laptop screw by screw, removed the CPU and all other removable parts, put in the new motherboard, and booted it up. It worked, except for the video, which was screwy—black bands across the bottom, image spanning off the right side and wrapping around to the left. But otherwise, I was able to boot the machine, get files off to a USB drive, connect the network—pretty much everything.

After he left—having ordered some additional parts for tomorrow, I thought to check the laptop connected to an external monitor. Sure enough, the image was completely normal. So despite having been immersed in a magnificent high voltage short circuit, the laptop was working after some fairly straightforward fieldwork—no damage to the RAM or the hard disk.

The point is this: before today, I don’t know that I would have given you 2 cents for Dell’s tech support. After today, they get big points from me. The guy, from a local subcontractor, was knowledgeable, funny, experienced, and personable—we compared notes about local singing groups, as he’s in a barbershop group in Worcester. It might have been that I was re-reading The Cluetrain Manifesto before his visit, but the difference between Dell’s tech support line, which gave us misinformation about the international support policy and showed no common sense about how to solve the problem—proposing to take three to six weeks in Germany to fix the problem when I was going to be there only a week—and the hands-on brilliance of the support guy I met today could not be more pronounced. It is, in fact, all about the conversation.

Google Blog Search: No keywords on referrals

Does this bug anyone else? It’s possible with referrals from major search engines to get the search keywords that were used to find the page, which helps you to understand why people read your blog. But referrals from the Google Blog Search strip the keywords off.

A referral string from a regular Google search for “tim jarrett” looks like this:

http://www.google.com/search?hl=en&q=%22tim+jarrett%22&btnG=Google+Search

However, if you run the same search against Google Blog Search and click through a result, the referrer just shows what page was targeted:

http://www.google.com/url?sa=D&q=http://www.www.jarretthousenorth.com/

This is annoying for me, because I like to know why Google users find my site interesting. I understand technically why it happens—the redirect page, google.com/url, causes it because it loads in the user’s browser before loading the destination. But why does Google use the redirects on the search results in the first place? Is it to gather click statistics? If so, there are other, less intrusive ways. Or are they doing something else with the redirects, maybe something to do with stopping blog spam?

Some input from Google would be welcomed here.