Description: Resolution caps, "we delete it after 2 hours (trust us)", paywalled buttons, and why your browser can now do all of this by itself.
Y...
For further actions, you may consider blocking this person and/or reporting abuse
@effessdev tested?
Still in bus :(
hmm no problem just chat here for a while 🤣
What? 😂 You go and add more features to it dont waste time
I've done already bro reach home and test it you will see what I've cooked.
Let me test it right now...
What do you want to get tested?
@xulingfeng bro can you give me gem?
🤣I have no gem
bro whatt? means we have to get a gem to give someone a gem?
it is like a currency? and if yes then to get gems we have to give something or dev.to randomly gives to anyone?
DEV curator Gem de sakte hai.
who is curator?
@technogamerz & me with 0 gems but quality posts bruhh.
@xulingfeng based on your resident evil post
my chance of survival will be 90%
my job: (lol I don't know I'm employed or unemployed) but if employed then: Founder & CEO
if unemployed: then Techno Gamerz subscriber( @technogamerz you know this legendary youtuber ☠️) and because I've watched techno's all resident gameplays I know what to do what to not.
and if employed then I will launch ATLOCK_v6 that will protect humanity's last images forever, humanity's last messages kept in files for aliens will be locked by ATLOCK_v6
☠️
btw I've watched resident evil movie too.
You sly guy! Instead of leaving a relevant comment under my post, you commented on your own thread, hahaha 🤣
yeah because my comment on your post will start thread of discussion and then your post will be in active discussions which is already and mine will be not.
☠️
Yeah that's fair honestly.
yeah, that's AAK move.
But why U are using my Username? 🤣
The client-side approach is a real improvement, but I think there's another engineering detail worth considering: keeping the image local doesn't automatically mean the entire workflow is private.
For example, imagine a browser-based background remover running an ONNX model through WebAssembly. The image never gets uploaded, but a third-party analytics script, a compromised dependency, or an overly permissive integration could still expose information about the user's session. The Network tab is a good first check, but it doesn't establish the full security boundary.
I'd also pay attention to EXIF metadata in the exported file. Removing the background while preserving the original metadata could unintentionally retain GPS coordinates, camera details, or timestamps. That's especially relevant when the image is a client's unreleased product shot or contains location-sensitive information.
A strong implementation would combine local processing with a restrictive Content Security Policy, minimal third-party dependencies, explicit metadata handling, and clear documentation of what actually leaves the browser.
The interesting part isn't just moving image processing from the server to the client. It's making the privacy guarantees hold across the entire pipeline.
The Network-tab verification tip is one of the strongest parts of this post because it turns a privacy claim into something users can actually test. One nuance worth considering is that “no image upload” and “no data leaves the browser” aren't quite the same guarantee. Analytics, crash reports, or third-party scripts can still send metadata even when the image itself stays local. A clear explanation of which requests are expected, and why, would make the transparency even stronger. Privacy is much easier to trust when users can verify not just the main processing path, but the surrounding page behavior too.
@merbayerp
finally got like from one of most busiest person alive on the planet earth
🫡
Haha, Anmol! 😂 I’m not that busy, my friend. Just juggling a few projects!
But seriously, I enjoyed this one. Moving image processing entirely into the browser is a great direction, especially from a privacy perspective.
I also liked that you discussed the engineering challenges behind it, not just the features.
One small thought: the Network tab is a useful first check, but privacy also depends on the scripts running in the browser.
Keep building, my friend. And don’t worry, I’ll try not to make you wait so long for the next like! 😄🫡
So this is the person whome you were talking about?
yeah one of the most experienced person you will see on dev.to ever.
Haha, Anmol, you’re too kind! 😄
I’m just someone who enjoys building things and learning along the way. There’s still so much I don’t know.
It’s always nice to see people sharing ideas and helping each other improve. Keep up the great work, both of you! ❤️🫡
On point. "Free" is a bait, a trap to get data or a solution. Your text about the "Tab Spiral" and the risks of privacy on the servers is correct, but it's necessary to change the paradigm, to bring the battle to the front of the client WebAssembly AI, and to make users aware that they can protect themselves by looking at the Network tab and checking if their private information is on the servers. I completely agree with your text.