2 ms·
>is $2 too much to ask? I'd gladly pay $2 to retire my army of throwaway emails, assuming the service remains as currently advertised. How many email domains d
by rovyko 8y ago
>is $2 too much to ask?
I'd gladly pay $2 to retire my army of throwaway emails, assuming the service remains as currently advertised. How many email domains do you have available to choose from, and how do you plan to deal with vendors potentially banning your domains?
This is more of a general thought, but privacy is another concern. There are plenty of companies who took customers' money and then sold their private data anyways. I'm more inclined to trust a startup like yours, but somewhere down the line I see this as a possibility. Is there ever a way for a customer to be sure a company isn't misusing their data? Are there any 3rd parties who can confirm/audit their practices?
>What's the HN community feeling about when it is or isn't Ok for someone to post a comment reply pointing out their product might be able to help?
I'm still new here, but from what I've seen it's probably okay as long as the context is relevant. I see people pushing startup solutions on a daily basis and it's usually cool stuff.
- Shorn 8y ago> Is there ever a way for a customer to be sure a company isn't misusing their data? I'm interested in this too. But I don't have a practical answer. In terms of knowing if a service is misusing their data, I guess you could have a trusted third party do an audit? Though that doesn't really solve the problem of changing over time. Just because a service isn't misusing your data, doesn't mean they can't then change. And there's the issue of who to trust. An auditor that specialises in these things would have a serious conflict of interest issue to address. That all sounds terribly expensive.
- Shorn 8y ago> how do you plan to deal with vendors potentially banning your domains? See other comment, but I do plan to implement a feature where customers can bring their own domain. There's also a roadmap item to expose keywords as "sub-domains" (i.e. "facebook@rovyko.kopi.cloud"). Of course, subdomains won't help if they ban a top level domain. Additionally, I use AWS Route53 and all domains are managed with a full "infrastructure as code" approach. Having lots of domains won't be any kind of serious overhead to manage, except for the 50cents/mth cost (and inconvenience to users, but that pain can likely be mitigated).