imgopaal

7 ms·

1. 1.▲
   by imgopaal 9mo ago

   Hi, I'm a solo developer trying to build and learn new things along the way, and I appreciate your responses, about the QuickClip, I've been making some improvments along the way also I've updated my landing page about how we
2. 2.▲
   by imgopaal 9mo ago

   I went with PBKDF2 mostly because of its wide support and compliance history, but I’d love to hear your take on what you’d recommend.
3. 3.▲
   by imgopaal 9mo ago

   Thank you to everyone who took the time to review QuickClip and give honest feedback. I spent the day going through everything and fixing the issues that were pointed out, especially around security. You were right. The concerns were valid,
4. 4.▲
   by imgopaal 9mo ago

   Added https://quickclip.space/data-security with encryption details. FAQ coming soon. Thanks for the feedback—explaining encryption clearly is important.
5. 5.▲
   by imgopaal 9mo ago

   Keys are derived server-side using PBKDF2 (master key + user ID). Each user gets a unique key. Keys never leave the server. Details at https://quickclip.space/data-security . Thanks for asking—this is exactly the kind of que
6. 6.▲
   by imgopaal 9mo ago

   Clarified: it's server-side encryption with per-user keys, not true E2EE. Added https://quickclip.space/data-security explaining the approach. Open source is under consideration. Thanks for pushing for transparency.
7. 7.▲
   by imgopaal 9mo ago

   still working on it. Storage bucket policies now restrict folder access, but listing permissions need tightening. Will update bucket policies to prevent enumeration. Thanks for the detailed curl examples—they helped identify the exact issue
8. 8.▲
   by imgopaal 9mo ago

   Also Fixed. Images now use signed URLs with 1-year expiration. Public URLs are automatically converted to signed URLs. Storage bucket policies restrict access to user-specific folders. Appreciate you flagging this.
9. 9.▲
   by imgopaal 9mo ago

   Fixed. Each user now has a unique encryption key derived via PBKDF2 from master key + user ID. Old items are being re-encrypted in the background. See /data-security for details. Thanks for catching this critical issue.
10. 10.▲
    by imgopaal 9mo ago

    Thanks for reporting this. I'm working on it
11. 11.▲
    by imgopaal 9mo ago

    I also use localSend. Amazing tool
12. 12.▲
    by imgopaal 9mo ago

    Really appreciate your insights. Thanks
13. 13.▲
    by imgopaal 9mo ago

    fixed, thanks you for comment
14. 14.▲
    by imgopaal 9mo ago

    Yeah fair point. QuickClip does store data in database, otherwise syncing between devices not possible. But here is how it works: - Data is encrypted when sending and also when sitting in database. - Stored only so your devices can fetch it
15. 15.▲
    by imgopaal 9mo ago

    exactly
16. 16.▲
    by imgopaal 9mo ago

    thanks, I would work on that
17. 17.▲
    by imgopaal 9mo ago

    cool
18. 18.▲
    by imgopaal 9mo ago

    yup, thats still a nightmare for a lot of people
19. 19.▲
    by imgopaal 9mo ago

    Yes, It works smoothly with texts and images both
20. 20.▲
    by imgopaal 9mo ago

    great
21. 21.▲
    by imgopaal 9mo ago

    Thanks for your suggestions. Would work on it
22. 22.▲
    by imgopaal 9mo ago

    Hi, Its a simple web application, nothing is required to install
23. 23.▲
    Show HN: I built a universal clipboard that syncs realtime on multiple devices(quickclip.space)

    40 points by imgopaal 9mo ago|79 comments