search

EFForg / cryptobot-email

GNU Affero General Public License v3.0
61 stars 11 forks source link

Analytics #12

Open micahflee opened 11 years ago

micahflee commented 11 years ago

We should have usage analytics. At the very least the number of emails the bot reads, but at most the properties of each email that was sent. That way we can say x people sent us plaintext emails, y people sent is perfect encrypted and signed emails.

0.2 probably? Though just keeping logs (in an analytics-friendly format) shouldn't be too much work to implement.

mfb commented 11 years ago

For analytics, it would be nice to store an HMAC of each email address and key fingerprint interacting with the bot. Depending on the privacy policy, this could be an HMAC with non-rotating salt which would allow encryption adoption/bot usage to be measured accurately over a long period of time, or an HMAC with rotating salt like Cryptolog uses, which would prevent someone who had access to the HMAC and salt from looking up whether or not a user has interacted with the bot.

micahflee commented 11 years ago

Good idea. I'm adding this to 0.1 milestone. I think we should have at least basic analytics when we launch.

micahflee commented 10 years ago

Switching to 0.2 milestone.