4 ms·

I'm working on a service which provides (obfuscated) aliases of your users e-mail addresses on your own domain. It only requires some API calls to generate the

• meowface 12y ago
  I'm not sure I understand the tradeoff here. It sounds like people are gaining a little bit of extra privacy (by preventing spammers harvesting your email) while sacrificing a ton of privacy (by allowing a a third party MitM to intercept all of their emails to and from that domain). I actually like the idea a whole lot, but I'd prefer if this could be done in some provably confidential way (where your service has no ability to see the content of messages, only To and From).
  • Wouter33 12y ago
    Of course you're putting some kind of trust in a third party. But the idea here is that you do that with all your good intentions and have a better alternative than just plain listing the address. It is up to us to prove our reliability, got some ideas on how to do that, but love to discuss that with you! Apart from that it could also provide a service to your customers with the webhooks you utilize.
    • meowface 12y ago
      It's not hard to believe in good intentions, but a bit harder to believe that your service is and will always be secure. One breach and suddenly millions of emails from thousands of domains from old backups are all over the internet. There is a way of making a service like this with minimal risk if you have a full breach, but it's hard to verify that as an outsider.