Re:Show HN: Share It, Anonymously with Self Destruct Messages
by BiteCode_dev on Tuesday June 01, 2021 @08:28AM
(#27353439)
Unless I missing something, there are a ton of open source client side encrypted pastebins around.
E.G: 0bin.net (https://0bin.net/), with a lot of good faith in the FAQ (https://0bin.net/faq/), a basic and open source code (https://github.com/Tygs/0bin), zero JS stats on the main instance and alternative instances already in the wild. It does feature self destruct.
Re:Show HN: Share It, Anonymously with Self Destruct Messages
by premek on Tuesday June 01, 2021 @06:30AM
(#27352585)
well now you have your platform where you can be confident that no one is snooping but if anyone else would like to use one too, they would have to make it themselves (or deploy your source code when you publish them)
Re:Show HN: Share It, Anonymously with Self Destruct Messages
by Tepix on Tuesday June 01, 2021 @06:36AM
(#27352628)
What's wrong with the cryptpads?
Anyway, a bit of feedback:
1. You really need a privacy policy
2. Instead of very long hexadecimal UUIDs use shorter IDs with more valid characters. Do you really need 128 bits for something that has to be brute forced and only lives for a limited time? Perhaps 64 bits are sufficient?
Re:Show HN: Share It, Anonymously with Self Destruct Messages
by loa_in_ on Tuesday June 01, 2021 @08:34AM
(#27353487)
2) what would shorter IDs accomplish?
Re:Show HN: Share It, Anonymously with Self Destruct Messages
by quickthrower2 on Wednesday June 02, 2021 @06:07AM
(#27366882)
Typing URL onto mobile?
Re:Show HN: Share It, Anonymously with Self Destruct Messages
by vort3 on Wednesday June 02, 2021 @06:24AM
(#27366972)
Can't you just scan the QR code?
Re:Show HN: Share It, Anonymously with Self Destruct Messages
by IYasha on Friday June 04, 2021 @04:50PM
(#27398920)
Did it ever occur to you there are devices without cameras/QR scanners? Just FYI.
I ll publish the code on github too. The idea is that on every startup, system generates a new keys to encrypt data. This site is hosted on a single docker instance and there is no output (logs etc) for now. I dont intend to capture anything at all from this. Litreally. The dictionary lives in memory and there is a background service on the same docker that new(s) the Dictionary every 24 hours.