legitimate_key

10 ms·

1.
Show HN: We tried to recover blurred, pixelated and redacted text (480 cases)(datablur.app)
4 points by legitimate_key 17d ago|0 comments
2.
by legitimate_key 7mo ago
Most of the solutions here assume you control the recording environment, which works well for async demos. The harder case is live screen shares. If you're walking a client through something in real time and your terminal prints an env
3.
by legitimate_key 7mo ago
The concerning pattern is that the data-collecting ones actively hide what they're doing — the Similarweb-linked extensions apparently obfuscate with Base64 or AES-256 before sending. Worth distinguishing from extensions that are genui
4.
by legitimate_key 7mo ago
This is interesting. How much overhead did that add to your development workflow? I'm curious if building and maintaining that parallel demo infrastructure became its own project, or if it stayed lightweight. Also, did you use this for
5.
by legitimate_key 7mo ago
I thought this too initially - "just make the fake data look professional." Where it broke down for me: investors with technical backgrounds would ask edge case questions ("show me how this handles 10K records" or "
6.
by legitimate_key 7mo ago
Thanks for the Mockaton suggestion! I like the API mocking approach - that handles the backend data cleanly. The challenge I kept running into was the frontend side during live screen shares. Even with mocked APIs, I'd have credentials
7.
Ask HN: How do founders demo real product without exposing sensitive data?
5 points by legitimate_key 7mo ago|10 comments
8.
by legitimate_key 7mo ago
Interesting and smart approach - most noise generators are obviously artificial in their traffic patterns. I've been thinking about browser privacy from a different angle: not hiding what you browse, but hiding what's visible on y
9.
by legitimate_key 7mo ago
This is a smart workflow. I've been doing something similar (record screen, then manually write docs) and the AI approach saves hours. One thing that still trips me up though - the prep before hitting record. I spend like 10 minutes cl
10.
by legitimate_key 8mo ago
Nice execution. The toggle visibility approach is intuitive for live coding. One use case you might not have considered: pairing this with a persistent "demo mode" profile in VS Code. I've been experimenting with a separate w
11.
by legitimate_key 8mo ago
Really clean approach to the pre-call panic. The dual reality concept is smart. I've been working on a similar problem from the browser side (since most of my sensitive stuff lives in tabs - email, Slack, Notion). Different angle but s
12.
by legitimate_key 8mo ago
The browser-vs-app debate aside, the bigger issue for me is what happens once you're in the call. Screen sharing on Zoom (or any platform) is where the real anxiety kicks in. One wrong tab, one notification, one bookmarked URL you forg
13.
by legitimate_key 8mo ago
Congrats on the launch! This resonates - I've dealt with the "accidentally exposed credentials during a demo" problem a lot. The .env file is one of the most common culprits, but I've found the problem extends beyond jus
14.
by legitimate_key 8mo ago
I'm experiencing this exact problem building app that blurs sensitive data for screen sharing and recording. Users immediately ask: "How do I know you're not collecting my data?" What I've learned about building tru