When
· Naughties
· · 2003
· · · September
· · · · 01 (2 entries)

Millennial C · Re­cent­ly it be­came ob­vi­ous that the Visu­al Net data-prep and index-build sub­sys­tems need­ed refac­tor­ing, and I took on the job. So I’ve been up to my el­bows in heavy C cod­ing for a week now—my first such ex­cur­sion this mil­len­ni­um. Here­with some ex­treme­ly tech­ni­cal low-level notes on the sub­jec­t, prob­a­bly not of in­ter­est to non-professionals, ex­cept per­haps for a para­graph on the world-view of the ag­ing coder. There is some dis­cus­sion of XML and scal­ing is­sues ...
 
Spam Snapshot · My spam fil­ter is rea­son­ably well-trained against SoBig now, such that on­ly a dozen or two forged-To bounces a day get through; the price be­ing that I am un­like­ly in fu­ture to no­tice when my own emails bounce. Al­so, the end­less in­ven­tive­ness of the spam mer­chants is alarm­ing, and they man­age to get a few past Mozilla’s Bayesian de­fens­es. Two items of note in this space in re­cent days: First, the ever-inventive Paul Gra­ham sug­gests that fil­ters au­to­mat­i­cal­ly deref­er­ence ev­ery URI in each in­com­ing mes­sage; this is re­al­ly clever be­cause it means that any­one who sends spam is go­ing to in­cur a re­al tan­gi­ble ex­pense, since no­body gets band­width for free. Se­cond, Bill Wein­man pro­pos­es AMTP, for Authen­ti­cat­ed Mail Trans­fer Pro­to­col; a quick read­ing of the draft re­veals no ob­vi­ous fa­tal flaws but I’m no ex­pert in this space. Know­ing who sent ev­ery email would very like­ly make the prob­lem go away, though.
 
author · Dad · software · colophon · rights
Random image, linked to its containing fragment

By .

I am an employee
of Amazon.com, but
the opinions expressed here
are my own, and no other party
necessarily agrees with them.

A full disclosure of my
professional interests is
on the author page.