Gnah, updating is always such a pain when money is at risk. The "do you know the ppa guy" question being unanswered is also priceless. For Bitcoin and sensitive apps like that we need some signing mechanism that is easy to use and transparent.
When I use the ppa, I want to see something like "This binary is signed by A, B and C. D is missing. Should we install anyway?" If yes: "Do you generally trust updates containing just A, B and C?"
My other question: To have multiple people confirm the quality of a binary, can they compile it separately, getting the same binary? I would love to see as many people that review code to sign the binaries to gain trust. The source being trustful and the binary being signed by just one person is kind of a joke with the money at stake. No offense, Gavin, you are doing a great job and it's maybe a lack of tools or maybe a lack of understanding on my side (which would be a lack of easy and well known tools) but I think this update process needs more trust.
Extending this to mobile, I earlier mentioned how it is a joke to advertise a wallet as open source when 99.99% of all users use the binary. There needs to be a way to get what you want and to sign stuff.
To understand how many signatures I am thinking of: I want to be able to publicly approve of stuff and I want to be able to configure my friends' PCs to warn about updates if I did not approve of this version publicly.