News for hackers. Stuff that matters.
Re:How BrowserID differs from OpenID by _pdeschen on Friday July 15, 2011 @11:32PM (#2770035)
Speaking of such (which is a valid concern) I always use a nice feature from gmail which gives the ability to append +anything to your username. Mail will be forwarded to your inbox as usual where you can apply filtering to know whom as leaked your email. Hence you can use [email protected] while registering for foobar webapp.

This assumes that foobar webapp accepts + as a valid email local part character which is not always the case unfortunately (and against RFC) but that is another story.

Just sayin

Re:How BrowserID differs from OpenID by doublec on Friday July 15, 2011 @11:54PM (#2770078)
Given that everyone knows about this feature, what's to stop spammers just stripping of the '+' portion?
Re:How BrowserID differs from OpenID by drdaeman on Saturday July 16, 2011 @04:07PM (#2771639)
Simple solution: give everyone address with "+suffix", and mark as junk any mail without it.

For stubborn services who don't accept "+" in email addresses use unique redirect aliases.

(Also, IIRC, Gmail ignores dots, i.e. "[email protected]" and "[email protected]" is the same address. Chose a canonical one with a dot somewhere, and filter the rest with exception for legimate senders.)

Re:How BrowserID differs from OpenID by barkmadley on Saturday July 16, 2011 @12:16AM (#2770102)
you can get the same effect with arbitrary dots.

e.g. [email protected] is the same as [email protected]

Re:How BrowserID differs from OpenID by grk on Saturday July 16, 2011 @05:58AM (#2770484)
Still, they can remove all dots from gmail addresses.
Re:How BrowserID differs from OpenID by cgranade on Saturday July 16, 2011 @10:07AM (#2770780)
You can hide the + portion of a Gmail address behind redirects and forwards, if you feel so inclined. It's a lot of work, but it does let you use the "deliveredto" operator in Gmail to automatically sort and discard spam like that.