HFT in my backyard – II
This is insane: more than 28,000 visitors came to read Part I of “HFT in my backyard”. Some of them are inevitably bots, but my logs reveal the majority to be human readers from bank desks, technol…
The latest blog posts to take off on Hacker News. 1,615 posts.
This is insane: more than 28,000 visitors came to read Part I of “HFT in my backyard”. Some of them are inevitably bots, but my logs reveal the majority to be human readers from bank desks, technol…
NOTE: malware is now using this as their User-agent. I haven't run a scan now for over two days. I'm running a scan right now of the I...
INTRO As soon as the summer sun returns to Belgium, there is a natural human migration from Francophone Wallonia to the west coast sea in the Flemish part of the country. Here, à la mer du Nord, pe…
[Note to the impatient: to try out my beamforming simulation, which produced the above image, visit my beamlab test page - ideally in a brow...
A few hours ago, I sent the following “dear colleagues” email (lightly edited to remove some private details) to all my users at work: This has been a very trying week. For those of you…
This page has moved. If your browser hasn't redirected you already, click here .
wingolog: article: high-performance packet filtering with pflua
At around 06:49 CEST on the morning of August 27 2014, Google deployed an HTTP/2 draft-14 implementation on their front-end servers that handle logins to Google accounts (and possibly others). Those at least take care of all the various login stuff you do with Google, G+, gmail, etc. The little problem with that was…
The NY Times has a post up this morning about a neighborhood in Brooklyn called Red Hook where they have built a hyperlocal mesh network to service the entire neighborhood, from housing projects to townhouses. Red Hook is a cool place. We were there last night to sample Hometown Bar-B-Que‘s massive beef ribs and a […]
I've been using 802.11 on Linux now for over a decade, and to be honest, it's still a pretty sad experience. It works well enough that I mostly don't care... but when I care, and try to dig deeper, it always ends up in the answer “this is just crap”.
On a flight back to New York I read Level 3’s assessment of the latest round of the Netflix vs Internet Provider debacle. The summarized version is that basically Netflix is slow because Verizon refuses to add capacity to peer with Level 3. Fixing the situation would cost Verizon
Major DNSSEC Outages and Validation Failures
A blog about signals, programming, music, and other stuff.
Don’t use RFC 2616. Delete it from your hard drives, bookmarks, and burn (or responsibly recycle) any copies that are printed out.
These documents make the original specification for HTTP/1.1 obsolete . As a HTTP geek, this is a big deal.
Some major ISPs appear to be attempting to extort money in exchange for peering with Level3
That’s the title of RFC 7258 , also known as BCP 188 (where BCP stands for “Best Current Practice”); it represents Internet Engineering Task Force consensus on the fact that many powerful well-funded entities feel it is appropriate to monitor people’s use of the Net, without telling those people. The consensus is…
When TLS was defined, it didn’t allow more than one hostname to be available on a single IP address / port pair, leading to “virtual hosting” issues; each Web site (for example) now requires a dedicated IP address.
Software engineer, Free, Open Source Software Consultant, Innovator, Fedora & Debian Developer