Ars Technica: "We're probably Harvard's oldest blog, and we're certainly its most popular." [Scripting News]
They have an rss feed. I also created a scraped one for andrew sullivan's daily dish.
2:58:58 PM    comments ==

I just noticed that along with the p2p beta bits you install for threedegrees, you can also download and play with the Windows XP Peer-to-Peer SDK.
2:36:52 PM    comments ==

Three degrees of separation, and rising.. Yoz Grahame: Three degrees of separation, and rising. "As you can see, the kids have to be down with installing a metric arseload of supporting extras before they can get jiggy with the winking action." It looks like ThreeDegrees uses IPv6 via either 6to4 or Teredo. How long will it take for the rest of the P2P world to catch up? [Hack the Planet]

Some people are have all sorts of trouble with ipv6. Here is a little hint, before you turning off services. "netsh.exe interface ipv6 uninstall"
10:06:33 AM    comments ==

So I learned a little bit more this morning about NATs. Of the two most "secure" types" there are restricted and symetrical. I was wrong earlier about symetrical type. They won't work here. The difference between symetrical NATs and restricted NATs is that the restricted allows the client to have a NAT mapping go to more then one globally reachable host ip/port, while the symetric nat only allows one connection per globablly reachable ip/port. Thus an outside server can be used to bootstrap a connection between two NAT'd clients if a restricted NAT isn't involved.
9:35:56 AM    comments ==

So last night I went home and got some folks to install threedegrees. They seemed pretty happy with. I made sure to send out the Developers! wink :)
8:55:35 AM    comments ==

Dancing with the devil. While trying to stabilize a Windows server yesterday, Dave Winer pointed to a symphony of BSODs and wrote: Windows itself is stable, but the server junk they throw on top of it blue screens, probably because MS engineers don't feel that they have to follow the rules, and they have access to the OS source code. Scripting News My impression is that it's not access to source code that causes these problems, but rather, dancing with the devil at ring 0. Anybody who writes a device driver has to do that dance. Of course, the increasing kernelization of servers, for performance, does make them more device-driver-like. In Windows Server 2003, for example, the HTTP stack moves into the kernel -- a prospect that is both exciting and scary. ... [Jon's Radio]

Well, it's a scary change, but hopefully appropriate. The chunk of the HTTP stack that we put in the kernelwas the routing part. In the same way that the kernel routes different socket ports to different applications and servers running in different accounts, Http.sys routes different url namespaces. It used to be IIS that would do this for the windows platform, but IIS forced to much code from different teams into one (way too privledged) security context, and comes with too much negative baggage. This becomes a new multiplexing point for http in the platform (however, most of the time IIS is still the better thing to code to). This is the only reason we did this; a lot of IIS 6's new features are dependant on have such an independant multiplexing point. However for a non IIS user, the ability to share port 80 across different security boundries and good common URL parsing will be critical for having lots of apps recieve xml-rpc and soap.
8:38:18 AM    comments ==