Skip to main content

(Insert Your Encryption Key Here)

I'm not going to post The Number, but I'm going to talk about it.

What another big shouting match the interwebs have found themselves in. Is it wrong to post The Number on public sites? I don't think so. Anyone who can use it already has to write software that the regular Joe will grab. The Number is just a political/social status symbol now. Publishing is the The Number is the anti-crypto1 parallel to the eye-liner high schooler shopping at Hot Topic. The point is making the point, more than what point exactly is being made.

So did the lawyers overreact? Of course they did, and consulting their clients before making moves on their behalf might be a decent idea. Maybe someone at the companies would actually realize the PR mess they might be stepping into. Maybe someone would say "Is the new technology stable enough to shake up our customers, yet?" Blu-Ray and HD-DVD are a techy's toy at this point, alongside wealthy status symbol usage. So, the large portion of the consumers who even use the technology are precisely those who know of and care about this story. When your ratio of Geek to Joe is that high on the Geek side, you need to act a little differently. Joe didn't even notice.

We sure noticed. Some of us noticed too much. I wish Joe noticed more.

Does anyone else mentally picture the AACSLA as Gollum and the The Number has their precious?

Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be u

How To use Sphinx Autodoc on ReadTheDocs with a Django application

Sphinx is awesome for writing documentation. ReadTheDocs is awesome for hosting it. Autodocs are great for covering your entire API easily. Django is a great framework that makes my job easier. Between these four things is an interaction that only brought me pain, however. I'm here to help the next dev avoid this. Autodocs works by importing your modules and walking over the classes and functions to build documentation out of the existing docstrings. It can be used to generate complete API docs quickly and keep them in sync with the libraries existing docstrings, so you won't get conflicts between your docs and your code. Fantastic. This creates a problem when used with Django applications, where many things cannot be imported unless a valid settings module can be found. This can prevent a hurdle in some situations, and requires a little boilerplate to get working properly with Sphinx. It require a little extra to get working on ReadTheDocs. What makes this particularly h