3 ms·
Thanks! I was thinking of a similar pricing plan. I worried that companies wouldn't be comfortable with the security issues of having their drawings on my serve
by zhyder 18y ago
Thanks! I was thinking of a similar pricing plan. I worried that companies wouldn't be comfortable with the security issues of having their drawings on my servers though. Any tips on what I could do to make the service secure, and to make them trust me?
Btw, just like Basecamp is the anti-Project, I'd like to think of Dabbleboard as the anti-Visio (or anti-Netmeeting-whiteboard) :).
- ashu 18y agoMake sure the logo is professional looking! I am only half kidding. But apart from that, why not just go ahead and try pitching it to them as it is? There's tons of value in here even without adding security. If you later figure out that security issues make or break the deal, then you can revisit this issue (or keep working on it in parallel.)
- tptacek 18y agoI could give you a million things you could do to really improve the security of your service, but the reality is there are a couple of superficial things you can do right now that will get you over the marketing hump on security: * Deliver all content over HTTPS. * Have big long random strings of hex characters in the URLs.
- zhyder 18y agoYeah I should do the https thing. At least makes the transfer secure. I already do a bit of random strings. Try sharing a drawing, the link it produces includes a 16character code that must match for the sharee to be able to access the drawing.
- tptacek 18y agoIt doesn't really add any meaningful security. The real security issues with your app are going to be in your code, not on the wire. But it's a strong psychological signal. It's the same with the random IDs. Generate UUIDs with SHA1 or something, and make them show up in the URL bar. The signal is, "there's no simple integer counter here where if I incr it, I get some other customer's data".