Net Neutrality & Whitehouse.gov petition

There’s a Whitehouse.gov petition posted about Net Neutrality. It’s a little bit of a rant, but I agree with its punchline: No bandwidth modifications of information based on content or its source.

This relates to a comment from Philip Greenspun’s blog (How many times do we have to pay for the same internet service?) If I’m paying my Internet Service Provider (ISP) to provide bits from the Internet to my home, and content providers pay an ISP for getting their bits into the Internet, what’s the problem? Why do the ISPs ask to be paid more for certain content, say, from Netflix?

The problem is that most ISPs (cable company, DSL/phone company, etc.) seriously underprovision their facilities. If every home subscriber ever attempted to use the service (at 3 megabits/second or 7, or 15, or 100, or whatever) that the ISPs advertise, there would be dramatic slowdowns. The ISPs simply don’t have sufficient capacity in place. The “easy out” for the ISP is to brand Netflix and other content providers as “bandwidth hogs” and using “more than their share” of bandwidth.

Two questions come from this:

  1. If, Netflix, say, did pay more, would my ISP promise to provide great service that didn’t slow down? (I wouldn’t bet on it. They don’t like to promise anything…)

  2. Why shouldn’t we consumers treat these bandwidth claims as false advertising? ISPs take our money while promoting a service that they know they have no ability or intention of providing. Wouldn’t that be a fun class-action suit? 🙂

In any event, you can read and sign the Whitehouse.gov petition at http://wh.gov/lwhFt They got almost half the signatures they need in a week; they need another 60K signatures by 24 May to get an official response from the White House. The more publicity on this issue, the better.

LibreSSL fork of OpenSSL

A small team of well-known developers from the OpenBSD team is working on a fork of OpenSSL, to be named LibreSSL.

This group is going through the OpenSSL source code base and removing old/ancient distributions, reformatting the code to KNF (Kernel Normal Format), removing dead code, fixing bugs and improving the package documentation.

They’re aided by the freedom to abandon old cruft that will never again be used, but there’s a certain amount of enjoyment to be had in reading snarky commit comments such as:

ASN1_STRING cleanup - realloc has handled NULL since I had a mullet
and parachute pants ...

and

This only works on systems where calloc() does the integer overflow
check, but if your system doesn't do this, you need to ask your vendor
WHY THEY ARE 10 YEARS BEHIND IN BEST PRACTICE? 

and

I'm glad to know that Ultrix CC has a bug optimizing switch() statements
lacking an explicit `case 0:' construct. But Ultrix has been dead for more than
15 years, really. Don't give it any reason to move out of its coffin.

and

12 years ago, old_des.h was used to provide compatibility with libdes.
The man page says "Compatibility des_ functions are provided for a short
while" and indeed even the original commit message says "The compatibility
functions will be removed in some future release, at the latest in
version 1.0." So here we are, a short while later.

Now I've only been an OpenBSD developer for 11 years, one year less than
this header has existed, but in that brief time, I've learned a thing or
two about deleting obsolete code. It doesn't delete itself. And worse,
people will continue using it until you force them onto a better path.

(To read more from the complete check-in history, see OpenBSD CVSweb)

I, for one, am glad to see a dedicated team look at this code base with the freedom to make it better, smaller, and auditable. I wish them the best, and have thrown a few simoleons into their kitty.

Get your IRS transcript!

Why can’t the IRS tell me how much has been reported? Various companies and entities forward the same information to me and to them. If only I could look at the IRS’ notion of what has been reported, I could avoid rummaging around for all those scraps of paper at tax time.

Well, now you can. The IRS Get Transcript site allows you to get a list of all the accounts, forms, etc. that have been filed in your name.

Go to the site, create an account in the obvious way. My confirmation arrived within seconds, the entire signup process took two minutes. Then you can browse your records, both for the current tax year and for previous years (including your past tax returns).

Hat tip to Dave Winer’s Scripting News and Philip Greenspun’s blog

Better than rm -rf /.Spotlight-V100

My MacBook Pro (10.9.2) was running slowly. I saw frequent spinning beach balls, systemstats was consuming 100% of the CPU on a regular basis, Apple Mail was grinding away indexing files, etc.

The forums at discussions.apple.com contain all kinds of dicey recommendations about rm -rf /.Spotlight-V100 followed by “Works for me!” and “Didn’t work for me!” I’m not averse to wading in with Terminal, but I’d rather get advice from a trusted source.

One of the advantages of having AppleCare (you get it for 90 days after you’ve upgraded to a new OS, such as Mavericks) is that you can call 800-275-2273 and speak to a knowledgeable person. They recommended that I do three things:

  • Boot into safe mode, and let the computer perform a thorough disk and permissions check. (See the Apple “What is Safe Boot, Safe Mode?” article for more info.)

  • Force Spotlight to blow away and rebuild its index.

  • Then let Apple Mail re-index.

To do this:

  1. Boot into Safe Boot mode. Restart your computer and hold down Shift until you see the Apple and the progress bar that indicates that the hard drive is being checked/repaired. When the OS starts up (probably many minutes later), you’ll see “Safe Mode” in red text at the upper right corner of the screen. Restart your computer.

  2. To force Spotlight to rebuild its index, simply open System Preferences, click Spotlight, then the Privacy tab. Add your hard drive (hit the “+” and select the hard drive). Then close System Preferences. Re-open System Preferences, and remove the hard drive from the Privacy tab. This is the cue for Spotlight to begin re-indexing. In a moment, you can click on the Spotlight magnifying glass to see that it’s rebuilding the index. (Rebuilding took about three hours on my system.)

  3. Leave Apple Mail closed during all this. (You don’t want to have them both indexing at the same time – it hammers the processor and prolongs the agony.) When Spotlight finishes its indexing, open Apple Mail to allow it to re-index its cached files. You can continue to work in Apple Mail while this happens.

My system has been much more responsive since I did this, and I didn’t have to try any odd suggestions.

Learning about Single Page Apps

I’ve been looking for a way to sort out Angular, Backbone, Bower, Grunt, Node, NPM, Yeoman and all the other buzzwords that get thrown around for writing a Single Page App for the web. There are many Youtube videos around: these videos stand out as excellent resources.

Leave a comment with a link to other resources, and I’ll add them to this list.

And the H@ckfest results…

What a great weekend! What interesting ideas came from the H@ckfest!

My team, the inforMED project, presented an idea for helping first responders (EMTs, ED triage) to get relevant data on their cell phone/tablet when they first encounter a patient. If the patient has one, the EMT would scan the token (RFID, QR code, NFC, etc) and this would immediately bring up a face sheet that give contact information, current medications, allergies, and advance directives to that they could initiate appropriate treatment.

We won an honorable mention for the CIO Track of the entire competition, and also won a $1,000 prize from Intel. The team members were:

  • Rich Brown
  • Adrian Gropper
  • Jake Mooney
  • Susan Katz Sliski
  • Jessica Wang
  • Joyce Zhang
  • Alice Zielinski
  • Patrick Zummo

What a great team!

RRUL Tests – CeroWrt 3.10.28-14

RRUL charts

[Note: This is an earlier result. Check out the subsequent posting for CeroWrt 3.10.28-16 (above)]

The postings below are a series of charts that were created by the netperf-wrapper program. Note: I don’t know why the upload charts show such fragmentary data.

All charts made with default Queue Discipline: fq_codel, simple.qos script, ingress ECN on, egress ECN off. Variations are primarily with the Link Layer method.

DSL Modem has sync rate of 7616kbps down/864kbps up.

Chart names have the form: Down-Up-dflt-link-try.png where:

  • Down is the entered download speed (kbps)
  • Up is the entered upload speed (kbps)
  • Dflt is the default Queue Discipline as described above
  • Link is None or ATM with the number of overhead bytes [0 | 44]
  • try is an optional second or third attempt

Click on an image to view the entire set in a gallery