Original Summary

I wanted a way to send someone something that behaves like a view-once message without both people needing the same messaging app, so I built BurnLink . It runs on the sender's Windows PC and creates a temporary link. The recipient just opens the link in their normal browser — no account, extension, or installation. What it currently supports: one successful retrieval per link text + images MP3/M4A/WAV/OGG/WebM audio Spotify tracks optional song start timestamps music can keep playing after the private message disappears adjustable read timers expiration for unopened links optional passcodes five-attempt passcode lockout sender-side revoke Waiting / Opened / Viewed receipts Windows notification when a message is viewed light/dark mode browser-side encryption screenshot/copy/privacy deterrents I want to be clear about the last one: I'm not claiming a website can make screenshots impossible. Someone can always use OS-level capture tools, modified software, or just point another camera at the screen. BurnLink only makes casual capture harder. The sender's PC also has to stay online while an unopened link exists because BurnLink serves the message from the sender's machine through a temporary tunnel. There isn't a permanent BurnLink server storing everybody's messages. It's open source, and the Windows build is available as a GitHub release. GitHub: https://github.com/keystonehosting/BurnLink Release: https://github.com/keystonehosting/BurnLink/releases/tag/v3.0 This is the first public release, so I'd genuinely rather hear what breaks, what feels confusing, or what you think is badly designed than get polite feedback. Especially interested in: recipient UX Windows/browser compatibility security/privacy problems features you'd actually use   submitted by   /u/MAndatory112 [link]   [comments]

  • 情报分类：服务器与云资源
  • 分类依据：内容涉及服务器、云资源或网络线路
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/12 21:04:03