Devs, don't do this

@phonggt_

141.3K followers · usually 36.5K views a post

Views

1.2M

Likes

43.6K

Comments

536

Shares

5.3K

SoundTikTok sound · original sound - phonggt_

Why it worked

The video leverages a high-stakes security vulnerability that is relatable to developers, using a 'shock' factor by showing real-world examples of exposed credentials.

Summary

The creator warns developers against the dangerous practice of accidentally committing private API keys to public or private GitHub repositories. He demonstrates how easily these keys can be found by searching through public code repositories.

Structure

1Hook: Don't do this
2Context: LinkedIn post claiming GitHub is for free API keys
3Investigation: Searching GitHub for exposed keys
4Evidence: Showing examples of exposed keys
5Conclusion: Warning against committing private keys

On-screen text

Devs, don't do this

Transcript

Devs, don't do this. If you're a dev don't do this. I saw this post from LinkedIn, what on earth is GitHub? It's the easiest place to find free OpenAI API keys. I was like no way. So I did a search on GitHub just to see how bad this was. Seem pretty okay people were truncating their keys, they were putting X X X and then I got a little bit better at searching and found this. James shame on you. Snapbrillia shame on you. Shame on you, shame on you. Shame on you. Artashas shame on you. My god, you three shame on you. It just keeps going. Get help warns you or something if you put private keys in your repo. So this is actually crazy to me, but don't put your private keys in your repositories even if it's private.