Yes, at least partially. I think the most important component is that you'll only get application resources (like graphics, but potentially others depending on the application) that are required for the device you have. This means you'll not get graphics that aren't even targeted for your device, which is easy and a good thing, because you'll not have resources for retina screens on non-retina devices or vice versa. It basically rips out stuff you'll never need on your specific target device. And as far as I understand it this is not Apple doing magic, but the app developer defining in XCode which resources are targeted at which type of device.

DIsclaimer: I'm not a mobile app developer, I just watched the presentation and demo showing the XCode screens for defining this :)

Why don't we try the open source route and have people adopt these at-risk core system utilities? Won't there be any interest if those are up for adoption? If we get 3-4 volunteers per tool we can for sure do something about this and get more people to contribute to those tools.

I would definitely be up for something like that.

Any ideas on what might be a suitable replacement for Pipes? As it so happens I'm lazy and still seem to be using one or two pipes we built a long time ago :)

Indeed; I just looked this up several days ago and I'd be very carful with the Series 30+ phones that Microsoft Mobile is currently releasing. Although they're cheap and nice for a second phone, they're priced appropriately for what they are, which is not much in terms of even basic dumbphone features.

The Nokia 301 and the Nokia 515 are probably the "last" good dumbphones out there, and they're available as single and dual-sim... all the others either have problems with the address book sync, are not at least triband, or have some weird issues with connecting to in-car systems with bluetooth (although that last point was only my impression after reading reviews on the web, but not car manufacturer is testing dumbphones anymore :-/)

You do realize that you actually can modify a git repository to delete all traces of a file you previously comitted, don't you? If not, check out http://git-scm.com/book/en/v2/Git-Tools-Rewriting-History

I'm not sure I can help out with the project itself as I don't know what it is and what it is written in, but I've been recently working on static site generators and if it helps I might be able to help you migrate it over and hosting it on s3, github, or a privately owned server, depending on what is the best fit going forward.

I guess in the security advisory there will be a neat list of affected companies. This is already a good first step to get this funding and process issue addressed... it's just a matter of someone taking it from there. But I'm not holding my breath.

From my reading this actually does not only track bills, but automatically settles the payment transaction. I guess even the banks don't do this (yet). Paypal or local banks might be a prime candidate for something like this, though. Notwithstanding any prior art I guess this should be obvious to not only people in IT, but also to people in banking ;-)

No, security cameras are not illegal as long as you're only recording private property. As soon as you record on public property the recording needs to be registered with the data privacy commission and you need a reason for doing this. (e.g. perimeter cameras outside of bank buildings and such)

Nice that you made that available under the Apache License and that you're allowed to integrate contributions! It would be nice to have a great Python IDE available as open source. I'll definitely check this out when I get a chance!