26
Just built Zync — a privacy-first tool to instantly share code, links, or notes (no login)
(zyncshare.vercel.app)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Jul 2025
26 points (86.1% liked)
Programming
21526 readers
527 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
Automatically adding a generatored password to each share site could fix this. Without the password the page cant be accessed and thus wont be deleted.
For sharing, the password could be embedded in the URL as a fragment/query param.
Even a captcha would work. You wouldn't have to have your users create a one time use password, you can just have a set of 5 random numbers that someone has to type in in order to access the data.
Do you think adding a basic captcha would actually stop these kinds of abuse attacks, or is there a better way? I think it will stop bots but I don't really know about preventing users. I’m still testing ideas like optional PINs, like the other comments said , but I’m not sure which one gives the best balance of security and ease for users. Would love your thoughts!
It will stop the lazy, which is 99% of the battle. If you want some form of security, then either a user generated pin or a captcha will do the trick to keep bots away. If you want to avoid both of those, then a longer url will also work. 12 characters will prevent attacks from getting anything but lucky.
Yeah! I just wanted to build the simplest UX for users and just added a 6-character access key for every Zync, plus basic rate limiting to stop mass scraping. It’s invisible to users but blocks most common abuse. Will keep improving it based on all your feedback — appreciate it a lot.
Yeah that’s a really good idea! I was actually exploring something similar too while building this MVP — like adding a PIN or auto-generated password to protect each drop. The idea of putting it in the link as a query also sounds smooth and user-friendly.
This is just an early version I made to test the concept and see what people think, but now I’m definitely thinking about adding this kind of protection to stop abuse. Thanks for the suggestion!