Skip to main content

Watching Apple vs FBI With Worry

I’m watching the Apple vs FBI case with a cautious eye, worried about the outcome and really without much of a clue where its going to go. At this point we have a situation I can’t feel comfortable on either side of. Do I want an enormous multi-national billions-rich company refusing to follow court orders? That’s the kind of situation that would usually have me calling for pitchforks, probably metaphorically but increasingly physically. Yet, in this case, I can’t help but find that I agree with the specific case. Encryption, I believe whole heartedly, is a human right. … Don’t I? So what do I do when the hands that protect that are owned by share holders? We’re in a position that we shouldn’t be in. We have government agencies like the FBI and the NSA and the Department of Defense which should be tasked with protecting us and, therefor, with protecting the mechanisms that keep both our physical and ephemeral property safe. The NSA should be funding real encryption and promoting public awareness of keeping their data out of anyones hands, including their own. The FBI should be going after companies that offer shoddy encryption that puts our information in harms way, not strong arming them into crippling it. I worry that there will be a day when I look back at the Age of Encryption. I worry that I’ll have to explain the concept of secrets and privacy to a future generation the way I explain to my son today that our phones used to be tied to the walls.

Comments

Popular posts from this blog

My Software Job Transition Strategies?

I’ve been spending a good deal of the last two days preparing mentally for starting a whole new challenge as a developer. New things aren’t new to me, but this is different and big enough really call for some Deep Thoughts ™. For one thing, I’ve made a big move from the world of Python web development to totally other Python work and while web development has never been the only thing I do, it has been the only work that paid the bills. That transition isn’t one that bothers me or daunts me, though. Instead, I’m thinking about transitioning to the scope of the work I’m getting into. For a long time, I juggled multiple clients and client projects every day, so no single project usually took up most of my time. Every developer juggles time through the day, but exactly how that works in each company and on each project varies a lot. I was looking for a place that I could really focus in a way that I haven’t for a long time. I think I found that, but now I have to deal with the consequen...

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 operat...

The Snake Pit is About to Burst

The signs are all over the place. I can count at least five implementations of Python today: CPython, CL-Python, Jython, IronPython, and PyPy. The use of the language is sky rocketting and set to grab real mind-share as the hype over Ruby subsides. Things are looking good for a favorite green snake and british comedy troop reference, aren't they? Trouble is on the horizon in the very ingredients that could push us into true success. Our community and our very language is in danger of segregation, unless we all do something about it and learn to get along. One of the most visible dangers (to me) is being ignored for various political, cultural, and non-technical reasons. IronPython's users are increasingly pushing IronPython-only recipes, libraries, and tutorials. No one is talking about the transition of the alternative implemenations to CPython 3.0 compatability. To make matters worse, we still can not define the language without refering to an implementation. This is very un...