Yet Another New Blog...
I have been unhappy with my infrastructure for a long time, but never quite unhappy enough to change it.
Dissatisfied with the servers I had and the blog being on Tumblr, I decided to change things up a bit. The blog is now a static site on github.io and I’ve re-organised my servers on a different hosting service.
Since Tumblr is a little hard to pull the old posts out of, I am going to port a few just so there is something here, then for anything else, you can just go direct to the archive of the old blog there:
A little something coming…
I know this blog has been a ghost town, but my work on the PhoneGap team at Adobe has keep me plenty busy.
However, I am working on something cool that I am hoping to blog about on here soon. read more » </div>
Encryptr Now an Official SpiderOak Product
I am happy to announce that SpiderOak has acquired Encryptr. They were already providing all of the hosting of the Crypton server back-end, but they are now taking over ownership, marketing, support, etc.
I am still the primary developer for now (Encryptr is open source, after all), but SpiderOak will be in control of the day to day direction of the app such as features and releases. read more » </div>
(Belatedly) Introducing: Encryptr (and Development With Crypton)
“A free, open source password manager and e-wallet. Zero-Knowledge. Cloud-based. Private.”
If you would like to see it in action, my colleague David Dahl has made a video of it on Linux.
First, An Origin Story
In December 2013, I took two weeks off (for certain values of “off”) to travel with my wife and children up to Brisbane to have Christmas with my parents. I used that break (among other things) to spend some time away from my day to day dev tasks by exploring the new Crypton privacy framework being built at SpiderOak. I decided the best way to really learn it was to actually write a small example app. When I had been talking about Crypton at meetups, I had thought that a simple password manager would be a great use-case for the framework. read more » </div>