4 ms·

Hi HN, author here. I've been scratching this itch for a while, and now I think it's ready to share: https://kopi.cloud https://kopi.cloud * Protect your real

• clusmore 8y ago
  I currently have Fastmail with a catch-all so I can give out a unique address to every company, but before that I was looking for services like this. This looks really interesting, congratulations on launching! Could you add a few screenshots of the application that I can view before signing up? I'm also a bit confused about the term "keyword" which is mentioned only once on the landing page and several times in the pricing page but never really explained. I assume this is the alias (e.g. hackernews@kopi.cloud)? I'm also curious about the statement "You can even reply to emails through Kopi." Is this from inside the Kopi app, or is it replying to the email in my own inbox which Kopi forwarded to me, or either?
  • Shorn 8y ago
    Screenshots are a good idea, I'll do that. Thank you for pointing out the confusion about keywords. There's a few tutorial-style tips when you first signup that hopefully makes it obvious. But clearly I need to explain it better on the website. I've been in it too deep too long to see the obvious >.< A keyword is a unique string that you reserve when you first sign up (subscribers can reserve many keywords under different domains). So when you sign up, you might decide on the keyword "clusmore". Once the keyword is created, you can give out addresses like "facebook-clusmore@kopi.cloud" and "ycombinator-clusmore@kopi.cloud" (you don't need to sign in to Kopi, just prefix with a "stub" to identify you you're giving the address to, add a dash to separate from your "keyword", then give that address out). As for replies, if I were to send an email to "shorn-clusmore@kopi.cloud", it would end up in your real inbox with a "reply to" email address pointing back at Kopi with a unique reply address. When you reply to that email, the message will come back to Kopi, be mapped back to the original from address, then forwarded back to the original sender. This way, you can have a whole email conversation back and forth without ever telling the other party your real address. I should point out that Kopi is just about simple privacy of your email address. It's not appropriate for dealing with actual secrets and secrecy. In general usage, you don't log in to Kopi at all. The only time you would need to use the actual Kopi interface is to block particular email addresses (e.g. you would log in to Kopi and block the "shorn-clusmore" mail mapping), enable RSS publishing, create new kewyords, change where your mail is forwarded to, etc.
    • davchana 8y ago
      So it's kind of similar functionality Gmail provides with + address. Your hn-clusmore@kopi is Gmail's clusmore+hn@gmail If/when kopi becomes popular, what stops from websites just removing anything before - before saving clusmore@kopi & thus identifying, similar to what they do with Gmail plus addresses. hn-clusmore@kopi becomes clusmore@kopi. Signing up for new keyword is not like signing up for a new GMail address? Thanks
      • Shorn 8y ago
        Yes, similar to the gmail + address. If Kopi became popular enough that people found it worth doing this - I think it would be relatively easy to come up with many different approaches to prevent / mitigate this sort of thing. Different separators, passcode separators/prefixes, machine-learning based on the from / to pairings, ... all the way up to white-listing (blech). As a paid service whose continued existence depends on the customer's satisfaction - it'd be easy to justify doing any or all of those things.
• 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).
• sharcerer 8y ago
  1 more benefit of different pseudo-emails for each service is that when large collections of email, passwords are leaked then hackers can't apply same email to different services as each service would have a different account. This could safeguard users from situations like the recent Collection 1 leaks. I think you should list this as a benefit. Though if I make amazon-myname@kobi, twitter-myname@kobi then hackers can obviously try to guess the email, but still would be more work for them. Basically, in 1 sentence, the benefit is that, till now, aware users followed the obvious rule of different passwords for each service and then use a password manager to manage all. But, a much better norm would be different email AND password for each service. this part is important: DIFFERENT EMAIL AND PASSWORD. I want this to become a norm in the next 1 year. By norm, I mean I want some big players to implement this as well. Also, good work on kopi. What are your thought on bulc.club ?
  • Shorn 8y ago
    > thoughts on bulc.club Looks like pretty much the same thing as Kopi, but more polished and without the the forward to RSS functionality. How does "free" work though? Couldn't find anything in the FAQ.