this post was submitted on 05 Jul 2025
25 points (85.7% liked)

Programming

21556 readers
217 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 !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
UlrikHD@programming.dev
25
Just built Zync — a privacy-first tool to instantly share code, links, or notes (no login) (zyncshare.vercel.app)
submitted 1 week ago* (last edited 1 week ago) by raw_echo@programming.dev to c/programming@programming.dev
12 comments fedilink hide all child comments
 

I wanted a dead-simple way to share text, links, or code without creating accounts or dealing with messy UIs. So I built Zync(https://zyncshare.vercel.app/) — paste, share, done.

  • Share plain text, links, or code instantly
  • Replies work without login
  • Everything auto-expires in minutes or hours
  • No tracking, no ads, no clutter.

Would love to hear what you think. Is it something you’d actually use?

you are viewing a single comment's thread
view the rest of the comments
[–] raw_echo@programming.dev 2 points 1 week ago

Thanks for your detailed feedback! the current logic (auto-expiry after first view or a max of 2 days) is meant for simplicity and privacy. I posted an MVP to understand if this is worth it to continue building but seeing all the comments here it seems the major issue next is security. As the others mentioned I was planning to do either a simple CAPTCHA or optional PIN protection — whichever feels smoother for users. Appreciate you taking the time to explain the risk — that really helps me plan the next steps better!