Hacker News new | ask | show | jobs
by wildrhythms 1397 days ago
This is really cool! One suggestion - don't expose when 'identical form exists' on duplicate creator names. This can be de-anonymizing, because I can put some (fictitious) 'target's name into that box and see if they made a form using your service. Also it's not clear to me why it's necessary to have a creator name in the first place.
1 comments

The de-anonymizing attack is very interesting. Thank you for highlighting it.

The creator name is 'feature creep' about a future use scenario. People were trying to add uniqueness by changing the creator name, so I added it to the key generation hash.

Instead I should have removed the creator name field from the interface.