As someone who has recorded 500+ tech video screencasts while occasionally dealing with sensitive information, here's what I've come up with: 1. Do whatever yo

As someone who has recorded 500+ tech video screencasts while occasionally dealing with sensitive information, here's what I've come up with: 1. Do whatever you can to minimize sensitive info exposure before you even start streaming or recording. For example I created a shell script which backs up and clears my shell history and does other things[0]. Make a note to use a browser where your history is cleared too. 2. Sometimes it's easier to say screw it and show the sensitive information with full intent that you're going to change your API keys, password or whatever sensitive data is shown. This ends up being much better because now you don't need to worry about blurring anything because you know you'll re-roll your keys. This is really good for pre-recorded videos vs live streams. 3. If you need to hide secrets, put all secrets into an .env file and have a .env.example file handy to show how to set them up without showing your real secrets. This is another way to eliminate ever having to blur anything and have a 0% chance of ever exposing a secret. 4. If you need to hide something, put a solid color over it instead of blurring it so it can't be reversed. 5. One of the pain points with hiding something in a video is the sensitive info might be on a page where you're scrolling up and down on the page which means you need to move your solid color rectangle or expand it based on which frame is showing. But overall this isn't too bad with most video editors since you can click and drag a rectangle onto a specific point in your timeline. If you adhere to the first 3 steps, you'll often only need minor hiding in all of your streams and videos. 6. Often times you're hiding unexpected things, like maybe you're logged into GitHub to make a video about an open source project but you view your GitHub feed which shows a list of private organizations you do freelance work for. This is the type of stuff to watch out for, which IMO also makes certain editor plugins that try to hide secrets not that useful since you can hide them in other ways, and it sets you up with a false sense of security because there's many other sensitive things outside of your editor to think about. I'm not trying to deter you from building your tool, but I suppose I'm having trouble seeing how I would use it in practice. I'd be curious to hear how other folks handle this. [0]: https://nickjanetakis.com/blog/bash-aliases-to-prepare-recording-videos https://nickjanetakis.com/blog/bash-aliases-to-prepare-recor...