Quote from: etotheipi on August 09, 2014, 02:52:18 PM

The 30 minutes isn't to for "collection", it's for announcement checking. If there's a hard fork and people are potentially going to lose money, we need users to be aware as soon as possible.

Why don't you use the alert system in Bitcoind just like everybody else? It would be instant and more reliable, only you wouldn't be able to collect personal information with that method.

Quote from: etotheipi on August 09, 2014, 03:00:16 PM

Quote from: ForgottenPassword on August 09, 2014, 02:53:29 PM

Quote from: etotheipi on August 09, 2014, 02:52:18 PM

The 30 minutes isn't to for "collection", it's for announcement checking. If there's a hard fork and people are potentially going to lose money, we need users to be aware as soon as possible.

You don't need to send the installation ID when checking for announcements. Why would you need that?

So that we don't "count" that ping as a unique user. Our goal is to get a rough gauge of how many people are using Armory, and what the OS & version distribution is. That's all we use the data for. If we send a ping without the ID, we don't know if it's a duplicate.

Utter nonsense.

If you wanted a unique anonymous ID you would have generated a few random bytes and used that. Instead you used a highly identifying, personal piece of information and sent it to your remote server along with the IP address of the user. There's no way you can pretend that was a mistake from somebody who is writing wallet software.

Why don't you do us a favor and delete all the information you've collected without your users consent.