Viewing profile — legitimate_key
legitimate_key
HN member- Joined
- Wed, Jan 21, 2026, 8:54 AM UTC
- HN karma
- 2
- Public activity
- 13 items
- HN profile
- View on Hacker News ↗
About legitimate_key
No profile information was provided.
Recent public activity
-
comment
Comment #47071611
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…
-
comment
Comment #47046698
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 sendi…
-
comment
Comment #47001498
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, …
-
comment
Comment #47001494
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…
-
comment
Comment #47001489
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 scr…
-
story
Ask HN: How do founders demo real product without exposing sensitive data?
Pitching soon and want to show the real thing, not a sanitized environment. How do you handle sensitive during live demos? The problem: investors want to see your actual product wo…
-
comment
Comment #46947933
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 hidi…
-
comment
Comment #46906104
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…
-
comment
Comment #46884303
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 Co…
-
comment
Comment #46883302
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…
-
comment
Comment #46765760
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 w…
-
comment
Comment #46747874
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…
-
comment
Comment #46703067
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?" W…