Netcraft Toolbar Catches Phish

One in 20 people fall for phishing scams and provide their account information to bogus versions of PayPal, EBay and other ecommerce sites, according to a study by Rachna Dhamija of the Harvard Center for Research on Computation and Society.

The study presented real online banking and fake phishing sites to subjects to see if they could tell the two types apart. ... The most sophisticated site caught out 90 percent of the 22 people participating.

I began using the Netcraft Toolbar in October, which works on Internet Explorer and Mozilla Firefox and detects known phishing sites and other suspicious pages. I've tried some of the phish links to see how well the toolbar works, and it has warned me about all of them.

Security · 2006/04/05 · 2 COMMENTS · Link

Movie Downloaders Pay a High Price

Six studios have begun selling movie downloads this week on Movielink. Purchased movies can be kept forever for computer viewing and burned to DVD but can't be watched in DVD players. There's also a limit on the number of computers that can view a movie, and the service and site require Internet Explorer and Windows Media Player.

Prices for new movies are higher than DVDs -- Nicolas Cage's The Weather Man sells for $27 on Movielink and $22 on Amazon.Com. So you're getting less convenience at more cost, though no one had to package, ship or stock the movie.

Though Movielink might be worthwhile for rentals and hard-to-find movies, I'm having trouble seeing the value for major releases. Current customers appear to agree -- aside from The Weather Man, the best-selling downloads are obscure sexually themed movies and foreign films. The No. 1 seller's currently Sappho '68, a "deep, penetrating piece of artful vintage erotica" that rated only one customer review on Amazon.Com:

This is a very poorly made, cheap, nudie film. No story or characters to speak of. It is practically a silent movie ...

Movies · 2006/04/03 · 3 COMMENTS · Link

Mobile developer Russell Beattie likes the new .mobi top-level domain:

... something what we've been desperately needing in the mobile web: A standard navigation scheme. Now users can guess "cnn.mobi" or "yahoo.mobi" or "amazon.mobi" and KNOW that their phone isn't going to barf at them, and the companies will have a standard name to rally around as well. I would imagine that very soon, the handsets themselves will incorporate this, so instead of having to type in .mobi at all, that will be the default navigation scheme like it used to be in browsers for .com.

Domains · 2006/04/01 · 7 COMMENTS · Link

RSS: I'd Rather Switch Than Fight

Jason Young posed a question on Workbench recently:

I have followed the whole RSS soap opera from even well before Mark Pilgrim was writing snarky posts about Winer numbers. I've actually taken more than one opportunity to call it "Internet Jerry Springer" among my IT colleagues and others that I was evangelizing syndication (and RSS) to -- and that was prior to the 2006 events with the Advisory Board and what I feel is inexplicable behavior from Winer.

The whole hullabaloo has the group of people I work with (a National web effort targeting information coming out of the US land-grants and the cooperative extension system) thinking of solely Atom, and where we say RSS -- we really are referring to Atom. Our web apps are going to encourage Atom, produce Atom, consume Atom, etc. Almost entirely after watching the continued craziness surrounding its use.

I admire and respect your work, your tenacity, your continued evangelistic zeal in what you do here, and elsewhere in the things you write about. So I guess this whole rambly comment is to ask - why are you even sticking with this RSS thing? Why not take that energy and put it behind something with what seems far less "Springer Factor"?

This isn't a troll. It's a serious curiousity on my part.

As we work through the long-unresolved issues in Really Simple Syndication and spark up long-smoldering flamewars, people keep asking me why I don't just switch to Atom. The format's an Internet standard that has a well-established framework for resolving disputes, unlike RSS, and the developer community isn't mired in more old grudges than a Van Halen reunion tour.

I have switched.

I chose Atom for a recent programming project and will continue using it exclusively unless the RSS Advisory Board succeeds in clarifying the RSS specification. I'm no longer evangelizing RSS, because I think the problems with podcasting and HTML create huge hassles for implementers and make interoperability impossible.

Not long ago, I spoke with a technology journalist about syndication, and he predicted that a frozen specification will ultimately render RSS a legacy format. He expects Atom to eclipse RSS completely within five years.

That's not a bad outcome. Atom's a nice piece of work created through an exhaustive public process -- Tim Bray said recently that 17,000 messages were posted on its mailing list during development. I don't know Atom well yet as a programmer, but I've been pleased with the results so far.

Though I no longer pimp RSS, I'm still serving on the RSS Advisory Board. A recent post to the group's mailing list demonstrates why. Sean Lyndersay, a member of Microsoft's Internet Explorer team, needs to know the preferred MIME type for RSS documents. He's looking for a recommendation so they can follow the advice and check an item off the team's to-do list.

Like many subjects involving RSS, this is a long-standing issue that lacks resolution because there isn't a clear authority over the format. Mark Nottingham made an effort in 2001 to register an official RSS MIME type, but it failed:

application/rss+xml isn't registered, because the IESG wanted a "stable reference" for the spec (it being in the standards tree). So, it's technically incorrect to use it now; this is one of the reasons this is still a confusing issue.

There needs to be a place where the organizations and individuals with the most invested in RSS, both in financial and personal terms, can come together to resolve matters like this. The board works in the open, favors no vendor and is eager to bring in outside viewpoints. If that remains true, it should eventually gain the trust of the RSS community.

I think it's worthwhile to fight for that, even though I'm no longer interested in fighting for RSS.

Rss · Atom · 2006/03/31 · 33 COMMENTS · Link

RSS: The Joy of TextInput

I've written 21 computer books in the past decade, documenting thousands of subjects in tree-killing detail. One of my pet peeves as a technical writer is covering something that readers are unlikely to need and should never, ever use, like the discussion board component in FrontPage 2000. I devoted an entire chapter to it in Sams Teach Yourself Microsoft FrontPage 2000 in 24 Hours, a mistake I rectified in subsequent editions.

(Buy a copy of the book on Amazon.Com for 92 cents!)

FrontPage 2000 supported discussion boards with FrontPage Server Extensions and a bland web site template that used frames, as you can see on this Pot Bellied Pigs forum. I can't find a single publisher running a discussion board successfully with this software.

I was reminded of this when I wrote the draft RSS specification and had to cover the textInput element.

Nobody uses textInput, even though it has been a part of RSS since the first version was published by Dan Libby in 1999. Aggregators don't support it and RSS publishers don't include one in their feeds.

Because I had to document it anyway, I decided that at least one person should support it.

I included textInput in all of my RSS feeds for the past two months, using the element to ask the question, "Your aggregator supports the textInput element. What software are you using?" I also wrote a PHP script to collect input from anyone who answered this question.

I had to take textInput out of my feeds because its title was being interpreted as the feed's title, causing My Yahoo and other RSS software to change the name of my weblog from Workbench to TextInput Inquiry.

Before I removed it, two RSS aggregators were found that take textInput: James Robertson's BottomFeeder and the Liferea aggregator for Linux.

In BottomFeeder, any feed that has a textInput element includes a right-click menu command: Feedback, Send Comment on Feed. Choosing the command opens a dialog box that demonstrates Robertson is either extremely detail-oriented or couldn't resist implementing the most useless feature in RSS.

Rss · Publishing · 2006/03/29 · 7 COMMENTS · Link

Who Keeps the Metric System Down?

In a Washington Post remembrance of the late Reagan Press Secretary Lyn Nofziger, longtime friend and political rival Frank Mankiewicz claims that they worked secretly to kill the metric system in the United States:

... during that first year of Reagan's presidency, I sent Lyn another copy of a column I had written a few years before, attacking and satirizing the attempt by some organized do-gooders to inflict the metric system on Americans, a view of mine Lyn had enthusiastically endorsed. So, in 1981, when I reminded him that a commission actually existed to further the adoption of the metric system and the damage we both felt this could wreak on our country, Lyn went to work with material provided by each of us. He was able, he told me, to prevail on the president to dissolve the commission and make sure that, at least in the Reagan presidency, there would be no further effort to sell metric.

It was a signal victory, but one which we recognized would have to be shared only between the two of us, lest public opinion once again began to head toward metrification.

That's a sorry milestone to be celebrating today, since the closure of the U.S. Metric Board helped keep the U.S. with Liberia and Myanmar as the only countries that won't go metric, but you should never judge a man until you've walked 1.609344 kilometers in his shoes.

Politics · 2006/03/29 · 24 COMMENTS · Link

Moving from Manila to Movable Type

Craig Jensen's long-running BookNotes weblog has fallen on hard times since the move from Weblogs.Com to Buzzword.Com in 2004. His site lost its Google pagerank and he's had trouble rebuilding his audience.

As the first step in retiring free Manila hosting on Buzzword.Com, I'm helping him transfer the weblog to Movable Type, because I have a five-user commercial license that's going to waste on Workbench and I'd like to encourage a fellow liberal and bibliophile to keep blogging.

Jason Levine's Frontier script converted all 3,064 BookNotes entries into Movable Type's custom import format and extracted several hundred images from the weblog's Frontier database into individual files.

When I tried to import the entries, Movable Type happily reported that "All data imported successfully!" but it wasn't true. No entries were imported, a common problem I've experienced before that comes up on the software's support forums.

The problem turned out to be a cross-platform issue with text files. Windows and Linux use different end-of-line character sequences, so the export file I created on Frontier (running on Windows) could not be imported into Movable Type (running on Linux).

On Linux, I used the text editor vi to convert the import file from Windows to Linux format with this command:

vi +"argdo set ff=unix" +wqa mt.txt

The entries imported successfully after the change.

Six Apart has the best weblog import functionality I've used, but the software shouldn't report success when an import has failed to add a single entry. If possible, the software should check for Windows end-of-line characters in an import file and either flag the error or offer to fix it.

BookNotes requires more work to finish the move, as you can see from the test site. The next step: Figuring out how to edit the weblog entries so that graphics are properly displayed.

Linux · Manila · Movable Type · 2006/03/29 · 9 COMMENTS · Link

Read More Entries