How I built an end-to-end encrypted pastebin (and why the server can’t read your

<p>Hey everyone! 👋</p> <p>Like many developers and sysadmins, I constantly find myself needing to share temporary credentials, API keys, or sensitive text with clients and

<p>I've been building <a href="https://flowvault.flowdesk.tech" rel="noopener noreferrer">Flowvault</a>, an encrypted browser notepad. "Encrypted notes in the browser" isn't new —

<p>I had a screenshot to send. Nothing secret — a stack trace from a side project — but it had an internal hostname, a file path with my username, and a chunk of a config file in

<p><a class="article-body-image-wrapper"

<h1> Most developers have done this at least once: </h1> <ul> <li>Sent a password over Slack</li> <li>Shared credentials in email</li> <li>Copied secrets into a notes app and

<p>Hey DEV community! 👋</p> <p>As a developer and digital marketer, I got sick of using random, ad-stuffed websites every time I needed to quickly format JSON, calculate a margin,

<p>Turn on encryption and your upload is scrambled client-side with AES-256-GCM before it leaves your browser.</p> <p><a class="article-body-image-wrapper"

<h1> I built a self-hosted one-time secrets service in Node — here's the threat model </h1> <p>Sharing an API key in Slack feels wrong. Password managers work great inside a team