AppDNA is a small XCode shell script which efficiently packages a Mac OS X Application's source code into the application itself. The resulting embedded project directory is fully functional, allowing the code and resources to be examined, modified and re-built. The application is self-compiling when a Release build is performed.

Blog Posts (not ReBlogs) will now have additional links at the bottom of the permalink page to do nifty stuff like email the post to someone else, add it to digg or delicious and check Sphere for related posts.

The links will only appear on the archived permalinks, and not on the main page.

UPDATE: Actually, this feature is being implemented via Feedburner's FeedFlare suite, which doesn't seem to work consistently. So, depending on how everything is working on their end you may or may not see it on any given blog post.

I know this has made the rounds already, but it's always worth mentioning. The more I see this kind of stuff, the more I like it. I just hope Texas has struck down that silly law requiring "prefab homes" aka "mobile homes" to have wheels by the time I'm ready to do this.

My bank is making an effort at providing better security for online account access.

The Bad

I can't trust it.

The Backstory

For weeks, after logging in, I've been prompted to opt-in to a program that is supposed to improve security by providing answers to security questions -- they call it multi-factor authentication. Given the option to "do it later", I always passed. That is, until I was presented with three questions I never supplied answers to and no access to my account without the correct answers.

I call the number that is suggested when I run into problems. They tell me it was supposed to be gradually implemented over the period of a few months and the deadline passed for voluntarily opting in. I was aware that they were trying to implement this feature, I was not aware that it would be mandatory. I asked if I could opt out altogether, I'm happy enough with an account number and password. They tell me that it was mandated by a federal regulation, but weren't able to give me any information about what regulation mandated this change, specifically. Nor are they able to give me any details about where and how this supposedly private information is stored and to whom access is afforded. Either way, they would be happy to temporarily change the password to an arbitrary number, not of my choice, which when used would prompt me to select and answer the security questions. Each of which are somewhat personal in nature and frequently crop up at other sites (for password reset/retrieval) and most staggeringly are all questions for which the answers can be found in public records! To top it off, and to make things easier no less, I'm given the option to bypass this step in the future for the computer I'm using at the time, or for any other computer I authorize in the future.

Yep, sounds secure to me.

On the subject of Best Practices

I'm still impressed by the American Express technique of partially occluding the user name when returning customers log in... and no silly third-party solutions that may or may not have been federally mandated.

This sounds like fun. David Choe, The London Police and more painting to the tune of a live performance by The Dandy Warhols.
Bonus for following the link to the Dandy Warhols site: Wear 3D glasses. I always wanted to do that, in fact, it was one of my motivations for learning flash, so I could maybe have some animated stereogram action on the site.