DEV Community: YuSuf_Abdelfattah

Protecting Your Screen During Meetings with a Single Click

YuSuf_Abdelfattah — Sat, 14 Mar 2026 08:05:05 +0000

We all know the anxiety of sharing your screen in a meeting and suddenly needing to switch tabs.
That moment of hesitation. That split second of "wait, what do I have open right now?" before you click.
I kept living that moment over and over.

Inspired by a very public ChatGPT history

A few months ago I was presenting to my team, accidentally switched tabs, and everyone saw my ChatGPT conversation history wide open.
That split second of "they can see everything" stuck with me.
So I started wondering:
What if a tool just handled all of this for you, automatically?

Introducing Privacy Shield

Instead of panicking when you switch tabs just don't worry about it. Meeting Mode auto-detects when you're sharing your screen and instantly hides all tab names and favicons. No setup. No clicking. It just works.
Alt+Click any element to blur it persists even after refresh Content creators can hide credentials live while recording no editing needed
Working in public? Blur anything a shoulder surfer might see.
Full control via settings per-site rules, blur intensity, whitelists

It started as a fix for my own anxiety during meetings.
After using it daily, I stopped dreading tab switches entirely and I'm sharing it in case it makes your screen sharing a bit less stressful.
It's completely free on the Chrome Web Store

Privacy Shield - Chrome Web Store

Privacy Shield blur pages, mask tabs, hide UI elements and keep your screen private whether you're sharing, presenting, or in public

chromewebstore.google.com

Happy coding ❤️

[Boost]

YuSuf_Abdelfattah — Sat, 14 Mar 2026 07:55:28 +0000

Jumping Directly to i18next Translation Keys from the Browser

YuSuf_Abdelfattah ・ Feb 25

#webdev #developers #vscode #i18next

Jumping Directly to i18next Translation Keys from the Browser

YuSuf_Abdelfattah — Wed, 25 Feb 2026 22:56:46 +0000

When working on larger apps with i18next, I kept running into the same small but annoying problem:

I’d see some translated text in the UI and want to update it.

So I would:

Copy that text
Search across JSON files
Jump between namespaces
Repeat

It’s not hard just repetitive and slower than it should be.

Inspired by LocatorJS

A few months ago, a colleague introduced me to LocatorJS, and I was honestly amazed by how quickly I could jump directly to the source code with a single click.

No searching by class names.
No blindly guessing which component is it.

I really liked the idea and started wondering:

What if another tool did the same behaviour, but for translation keys?

Introducing i18nKeyLocator ⚡

Instead of searching for where a string comes from just click it.
No searching.
No guessing.

Just direct navigation from the rendered UI to the exact namespace and line number where the translation key lives.

It started as a small experiment to speed up my own workflow.

After using it daily, I noticed I was spending much less time navigating translation files and I am sharing it in case it makes your i18next workflow a bit smoother.

Happy coding ❤️