Great idea, but how do you guarantee “no-account needed” security? Even if the code runs on the client, browser extensions (such as malicious plugins) or a compromise of the CDN from which your script is loaded can easily intercept this data. Trusting the “browser” when it comes to the security of client data is an oxymoron. How do you plan to convince paranoid security experts that your website hasn’t been compromised?
empinet.dev is a collection of tools for everyday developer work. JSON formatters, converters, JWT decoders, image tools and more.
We needed these while working on projects for our clients. We wouldn't send client data to third-party servers just to format or convert it, so we ended up building our own set of tools.
Everything is processed in your browser. Your input stays on your machine. They're free, and there's no account needed.
Would love to hear what's missing or what you'd find useful.
Great idea, but how do you guarantee “no-account needed” security? Even if the code runs on the client, browser extensions (such as malicious plugins) or a compromise of the CDN from which your script is loaded can easily intercept this data. Trusting the “browser” when it comes to the security of client data is an oxymoron. How do you plan to convince paranoid security experts that your website hasn’t been compromised?
empinet.dev is a collection of tools for everyday developer work. JSON formatters, converters, JWT decoders, image tools and more.
We needed these while working on projects for our clients. We wouldn't send client data to third-party servers just to format or convert it, so we ended up building our own set of tools.
Everything is processed in your browser. Your input stays on your machine. They're free, and there's no account needed.
Would love to hear what's missing or what you'd find useful.