4 ms·
You don't need to, just make sure your users are aware. I don't think users would disregard your service - as long as it doesn't deal with some heavily private
by sahillavingia 16y ago
You don't need to, just make sure your users are aware. I don't think users would disregard your service - as long as it doesn't deal with some heavily private stuff - just because you don't have an SSL cert.
- AgentConundrum 16y agoas long as it doesn't deal with some heavily private stuff Nothing private. The only things that wouldn't get made public by default are intended to be things that I'd like you to opt into making public anyway, and none of these features would be in the 1.0. just make sure your users are aware Any suggestions for this? A popup saying "hey, this is pretty insecure.. are you sure you want to bother?" seems like a good way to get people to leave your site alone.
- Andrew_Quentin 16y agoNah, leave the users alone. If they are developers they should check that it does not say https anyway. I mean, hacker news does not scare people by saying, hey man this data is not secured. But then hacker news asks for a username which you make up on the spot and a password for which you do the same.