Rather, Verisign responds to ICANN.

RE: ICANN Responds to IAB

] In particular, we recommend that DNS wildcards should not
] be used in a zone unless the zone operator has a clear
] understanding of the risks, and that they should not be
] used without the informed consent of those entities which
] have been delegated below the zone.

Internet Architecture Board tells Verisign no...

] Within three years, most bank machines that dispense cash
] will run on the Windows operating system, according to a
] study published last week.

Doh!

Wired News: Windows to Power ATMs in 2005

] Someone asked me this morning how to parse the
] MemeStreams RSS feed. So I present this. This is a simple
] Perl script which uses XML::RSS to parse the headlines
] from a number of news sites, including MemeStreams, and
] post them to a Prolite LED sign. There is a lot more in
] that RSS object then a title, but hopefully you can use
] this as a starting point for your projects.

LedNews -- Example RSS perl script

Decius wrote:
] bucy wrote:
] ] It built fine for me on debian after I installed the
] ] glut-devel packages. Pretty cute.
]
] Hrm... Cute? I ought to go through the rigamoral of
] installing debian on my laptop in order to play with it, cute?
] Or just cute?

Probably "just cute" at this point. It shows promise but doesn't seem terribly useful (to me) at this point.

RE: 3d file browser for linux

] WASHINGTON (Reuters) - A deal between television
] manufacturers and cable operators to replace digital
] signal converter boxes with a small card that slots into
] new televisions won approval from U.S. regulators on
] Wednesday.

I thought they should do this a long time ago ... finally!

Click here to find out more! FCC OKs Digital Cable Accord on TV Cards

] So, between spam, anti-spam blacklists, rogue packets,
] never-forgetting search engines, viruses, old machines,
] bad regulatory bodies, and bad implementations, I fear
] that the open Internet is going to die sooner than I
] would have expected. In its place I expect to see a more
] fragmented network - one in which only "approved"
] end-to-end communications will be permitted.

I agree that this seems to be happening now but I don't think it is by any means a foregone conclusion. Rather than throwing up our hands and giving up, we should try to squelch the sources of this noise traffic.

The end of the open internet...

Decius wrote:
] ] So, between spam, anti-spam blacklists, rogue packets,
] ] never-forgetting search engines, viruses, old machines,
] ] bad regulatory bodies, and bad implementations, I fear
] ] that the open Internet is going to die sooner than I
] ] would have expected. In its place I expect to see a more
] ] fragmented network - one in which only "approved"
] ] end-to-end communications will be permitted.
]
] I happen to think this is true. Who is doing the approval is
] the question. The fact is that if anyone can decide how things
] are approved, then everything is fine. I cut my whack account
] over to a challenge response system. Bang, its useable again.
] I get no spam there at all, and all the people I talk to are
] getting through just fine. I'm happy. I think it will work
] just fine... In fact, if the internet had more close knit
] communities I think it would be better off.
]
] Moving to the country side to escape the noise is not the same
] as censorship.

At CMU, my friend's boss has started talking about fixing spam via PGP; if your mail to me isn't signed with a key I know, you get a mail back saying it will be queued for a day or something before I'll look at it. If you reply to that mail, its sent on through immediately. We're talking about implementing it both in MTAs and also mail servers.

I will try to blog more about this as it develops.

RE: The end of the open internet...

] Most documents are the product of continual
] evolution. An essay may undergo dozens of revisions;
] source code for a computer program may undergo
] thousands. And as online collaboration becomes
] increasingly common, we see more and more
] ever-evolving group-authored texts. This site is a
] preliminary report on a simple visual technique, history
] flow, that provides a clear view of complex
] records of contributions and collaboration.

IBM | History Flow

] eWEEK: For its part though, SCO has said that there are
] so many lines of code, and a variety of applications and
] devices that use that code, that simply removing the
] offending code would not be technically feasible or
] possible and would not solve the problem. Do you agree?
]
] Torvalds: They are smoking crack. Their slides said there
] are [more than] 800,000 lines of SMP code that are
] "infringing," and they are just off their rocker. The SMP
] code was written by a number of Linux people I know well
] (I did a lot of the SMP IRQ scalability myself,
] personally), so their claims are just ludicrous. And they
] claim they own JFS [journaled file system technology]
] too. Whee. They're not shy about claiming ownership of
] other people's code

Torvalds Slams SCO