How to mitigate the security vulnerability of showing the Stream Key in the b.siobud links?

[BombasticBooger]

I use this service with my friends and I frankly love it, but it's very uneasy to me having the stream key out, even in private DMs.

I reset my Twitch stream key so the stream key I use in OBS to Broadcast Box (I'm guessing) shouldn't lead to anywhere (i just tested and it gives an error with Twitch), but I'm also skeptical that I don't know enough about how Stream Keys work and this might still be a big vulnerability (the first 9 number digits stay the same even when I reset, I haven't found any documentation on how Stream Keys work), though I want someone competent enough to know if my guess is right.

Thanks!

[theFroh]

The stream key in Broadcast Box is not like a Twitch stream key. Think of it like a room name; you're going to give it to anyone who wants to come watch, and anyone with it can stream to the room. You can put anything in there, be it something like my-special-stream, to something harder to guess like a UUID, e.g. a1ec007c-1377-4ec3-949b-12b8826c1be5.

Whatever you pick, you're going to be giving it to your friends. Technically you're trusting them to not stream to that room too, or maybe you're OK with that.

Your Twitch stream key must remain private. Never share it with anyone. Since it sounds like you used your Twitch stream key as a Broadcast Box stream key, refreshing it was the right move. The first nine digits being the same after the refresh is fine.

(Also Broadcast Box has a concept of "reserved" stream key/profile, which gives you a key to stream with that you can keep secret that is different from the one you give out to view, but I do not believe there is any way to use this on the public b.siobud instance.)