Wednesday May 26, 2004

In the Picture's application, if you go into the menu and flip the "Picture Size" option in the preferences from "Small" to "Large" you get a little jump in quality (and "Large" is hardly big at all -- I think it's only a .3 megapixel camera anyway).

So, check out this sign I spotted downtown for a lost dog, sad but true! But at least you can read it! ( May 26 2004, 11:23:52 PM PDT ) Permalink

Monday May 24, 2004

That might not be a bad thing per se but when I first wanted to setup my blog with a little procmail magic to post pictures, I was stymied by the limitations of PictureMail. Well, it turns out that Buzznet's moblogware supports fetching the fetching the PictureMail content and posting it!

So I'm gonna give it a go, I'm posting stuff from my Treo 600 there in separate blog simply named Pictures on my Treo 600 (hey, who says these things have to have clever names?).

( May 24 2004, 01:08:36 AM PDT ) Permalink

Sunday May 23, 2004

Google already has a lot of Secret Sauce in their page rank heuristics. Presumably they've already got some automated Google bomb detection but I sure would be interested in knowing the specifics of how they accomplish that. ( May 23 2004, 01:47:00 PM PDT ) Permalink


Further Ruminations on Blog Index Spam Every time I think of easy ways to squash blog index spam, I can think of countermeasures that They Who Eat Their Young might employ to circumvent those efforts.

Perhaps the Vote Links is a bad idea after all (sorry, Kevin). It would be trivial for blog index spammers to catch on and merely add their thumbs-up vote in the links in the content they're clogging the ping stream with. Perhaps there's a sunnyside to this issue, in the same way that comment spam can provide fodder for anthropological amusement, maybe there's something valuable in blog index spam.

Well, no. All spammers should deserve to be treated to a merciless onslaught of pain. Period. ( May 23 2004, 10:54:38 AM PDT ) Permalink

Saturday May 22, 2004

If you want to have the appearance of having lots of attention on the net, the barrier to entry is not terribly high. Install some blog software, setup a five or six blogs that link to your site about lonely, sexy milfs in your area, octane booster for your libido and deals-of-the-century for mortgages and [badda-bing!] make a thousand DNS entries for each of these blogs. Then, whenever you update your handful of blogs with your wonderful content, programmatically ping all of the wonderful recipients of update notifications and.... [drum roll]

Ta-da!

You've spammed the blogosphere.

It's my considered opinion that this problem is going to continue to swell as more spammers catch on. As anyone who's had a friend descend into a Mister-Hyde's-gone-AWOL-on-a-heroin binge dirtball can attest, low life scumbags are often quite resourceful. We've already seen that demonstrated contending with comment spam. The underlying problem is that the event capture engines promiscuously accept anything into the stream. It's as bad as having an open relay in the SMTP universe... millions of mail servers in Asia and Eastern Europe can't be wrong!

Blog posts can be fingerprinted and checked for duplication but next thing you know, we're going to require bayesian filters -- I can easily imagine how to defeat the duplication checks; to catch a criminal, you have to have the capacity to think like one, I suppose. Weblogs.com already makes sure it doesn't take a ping for the same blog too frequently within a duration of time, but that doesn't address any issues concerning authenticity.

Anyway, the underlying problem with SMTP is that you can pretty much claim to be anyone and send mail to everyone when the SMTP server is an open relay. By extension, the ping stream suffers from the exact same problem.

I propose that the ping services become a network of trust. Pings should be identified with secure tokens; one way cryptographic hashes with regularly expiring keys would keep just about everyone except the NSA from anonymous pinging. Those found abusing the ping stream could have their ids revoked. That way, the only events making it into the ping stream would be known and identified entities. I believe that the earlier this is put in place, the sooner the blogosphere can wall itself off from purveyors of canned pork by-product products. ( May 22 2004, 05:32:34 PM PDT ) Permalink

Friday May 21, 2004

Bill Gates stood before a crowd of top CEO's and waxed on about where he see things going. Now, if you'd read any of his drivel (like The Road Ahead) where he positions himself as a technocaster, you know that at least half the time, he's full-o-crap. But that doesn't matter when you're the richest schmuck on this rock, does it?

"Another new phenomenon that connects into this is one that started outside of the business space, more in the corporate or technical enthusiast space, a thing called blogging. And a standard around that that notifies you that something has changed called RSS."

What would Bill blog? Posts about how great SCO is? How much he hates Mac OS X cause it's so much better than anything he'd come up with? ( May 21 2004, 02:21:27 PM PDT ) Permalink

Thursday May 20, 2004

Does the blogosphere need a "report this url as spam" service where any blogs that link to it are immedately suspect? Perhaps a points system... if a blog has legit URLs than the links to spam that have managed to get inserted into the content will should score as strongly. Perhaps this is case for Vote Links as my colleague Kevin Marks will assert. ( May 20 2004, 11:50:08 AM PDT ) Permalink


Blog Index Spammers Must Die! What will they think of next? I wrote a little application to keep an eye on what's under discussion in the blogosphere on a particular topic and next thing ya know, some bozo has posted hundreds of clone blogs to stuff the search index.

Last night at the Technorati Developer's Salon I showed off something I wrote that uses Technorati's API, Who's Talking About The San Francisco Giants, Powered By Technorati. It uses Technorati's search and bloginfo APIs and orders the most recent results by the blog's rank. Lo and behold this morning, there's some bastard who owns the mooseblogs.com domain who has hundreds of aliases pointed to the same blog postings for buying/selling tickets. Among the events mentioned are tickets for the San Francisco Giants, thus killing the usefulness of the search index. The whois specifics for this bastard looks like this:

Registrant:
   WAI
   10105 W. 126th Terr
   Overland Park, Kansas 66213
   United States

   Registered through: GoDaddy.com
   Domain Name: MOOSEBLOGS.COM
      Created on: 02-Apr-04
      Expires on: 02-Apr-05
      Last Updated on: 04-Apr-04

   Administrative Contact:
      Walls, Tom  twalls@kc.rr.com
      WAI
      10105 W. 126th Terr
      Overland Park, Kansas 66213
      United States
      9134848289      Fax -- 
   Technical Contact:
      Walls, Tom  twalls@kc.rr.com
      WAI
      10105 W. 126th Terr
      Overland Park, Kansas 66213
      United States
      9134848289      Fax -- 

   Domain servers in listed order:
      NS1.ABAC.COM
      NS2.ABAC.COM

Tuesday May 18, 2004

But it's still funny to see it captured in a snapshot. Wondering what he's thinking about, "Maybe if virii were written with a portability layer, these suckers would get infected too... hrm" ( May 18 2004, 03:36:35 PM PDT ) Permalink