You’ve been amazing at providing us with your awesome feedback on the first version of Duckist.com and hoped you’d be just as active in sharing your thoughts on the new version. Our original idea was to make it easier for companies to share passwords securely. As a small software development service provider, we have had to gain access to countless accounts over the course of our work.
Clients frequently just resorted to sharing passwords in clear text, instead of taking the time to set up password managers. Bad idea!
Our tool took the hassle away, but our clients wanted it to be able to do more.
Now you can also encrypt files directly in the browser and even live chat. Not easy to do in terms of programming, because we have to encrypt a file in chunking using a type of stream. If done incorrectly the browser just crashes because of the excessive memory usage. We are considering to make a detailed blog article about how we achieved this and also open source the relevant part of the code. Would you be interested in reading it?
HN has the best positive roasting community I have encountered, so please feel at liberty to share as much feedback as possible! It would be tremendously appreciated!
1 comment
[ 2.9 ms ] story [ 14.9 ms ] threadYou’ve been amazing at providing us with your awesome feedback on the first version of Duckist.com and hoped you’d be just as active in sharing your thoughts on the new version. Our original idea was to make it easier for companies to share passwords securely. As a small software development service provider, we have had to gain access to countless accounts over the course of our work.
Clients frequently just resorted to sharing passwords in clear text, instead of taking the time to set up password managers. Bad idea!
Our tool took the hassle away, but our clients wanted it to be able to do more.
Now you can also encrypt files directly in the browser and even live chat. Not easy to do in terms of programming, because we have to encrypt a file in chunking using a type of stream. If done incorrectly the browser just crashes because of the excessive memory usage. We are considering to make a detailed blog article about how we achieved this and also open source the relevant part of the code. Would you be interested in reading it?
HN has the best positive roasting community I have encountered, so please feel at liberty to share as much feedback as possible! It would be tremendously appreciated!