this little gem has been sitting in my reading queue for a little while. it’s an interesting variant of the, “what would you do if you found someone’s wallet?” scenario. with everything sitting on your smart phone, you wonder why more folks don’t lean on the built in protections to secure their data.

obviously, the punch line to the story is the notion that we simply can’t trust other people not to root around in our found personal stuff. if this holds true to folks at an individual level, what’s to stop those who have access to far vaster realms of personal info and who watches these orgs?

when little dude gets older, i’m going to pedantically remind him of all sorts of inane shit. i plan on bringing it up at the most inopportune times just to bug the hell out of him.

dude, remember on 11-may, 2012 at your carnival there someone in an deciduous tree costume handing out educational stuff at your carnival? no? i do. it took me like 20 emails and 4 phone calls to make that happen.

the 20 emails and 4 phone calls part will be an amplification by at least an order of magnitude just to be more annoying.

here’s a slick little tip that i discovered on a mailing list today. the OSX resolver is more flexible than i initially gave it credit for. in lieu of running dnsmasq or something along those lines if you want to have selective resolution of DNS for different domains or use alternate name servers you can override this behavior within the /etc/resolver directory by providing per domain resolve.conf files.

doubly useful if you want to probe to a destination when you’re allegedly offline due to being placed behind a less than cluefully deployed walled garden.

since i’m in kind of a pissy mood anyways …

i’d like to thank you for making me waste a solid 45 minutes fixing various and sundry pointers because you decided that moving everything from /Developer to /Applications/Xcode.app/Contents/... was a productive way to facilitate an “upgrade”. this results in all sorts of unexpected behaviors. like oh say, an inability to find stdio.h.

some quality time with xcode-select and its associated manpages as well as some judicious googling seemed to result in the appropriate behavior. but i’m not entirely sure that i have the right switches in place. in the interests of saving someone else this hass. the following worked for me.

Zog[~]% sudo xcode-select -switch \
 /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer

note, that one would expect the following to work as well, but interestingly some stuff tries to sniff even further into the directory hierarchy and points at a number of 10.7 specific SDKs. these are not picked up by the CLI tools.

Zog[~]% sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer

i suspect there’s deeper magic i need to divine in order to make sure that i really haven’t screwed something up here. but at least my stuff is building complaint/warning free.