@MonkderVierte The thing is, since the code is running inside a browser extension there’s no way to interact with third party tools that aren’t part of the standard JavaScript api.

Well, I mean there’s Native Messaging https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native/_messaging but it only works for PC (Bye bye to ~70% of Android users) and I’d have to use a forked version to be able to handle messages from the browser extension, so I think that’s not the best solution for me

@MonkderVierte I’m afraid I can’t handle that from a browser extension, but good to know!

@Redex68 Honestly I have no idea, I barely use OBS

@prex Wait that’s a thing?
Well, this host basically the same value as a “Sent from my iPad” signature haha, how can you encrypt a post that’s publicly available to everyone?

- Sent with Mastodon Web

@LodeMike A more programatically concrete way would be to use https://developer.mozilla.org/en-US/docs/Web/API/MediaStream/_Recording/_API/Using/_the/_MediaStream/_Recording/_API

@geneva_convenience Elaborate?

@ShellMonkey Be careful, obfuscation isn’t encryption!
And no, there doesn’t need to be a publicly shared token! Take a look at how simplexchat does it!
https://simplex.chat/

@ShellMonkey That’s true, but these should also be encrypted, don’t you think?
Sure the messages could still be encrypted but from the metadata you can most of the time infer the content.

It’s a bit long, but you can read this if you’re interested
https://www.pnas.org/doi/full/10.1073/pnas.1508081113

@MrFloppy I agree! I sometimes received notifications on Mastodon from comments by Lemmy accounts on this post but far from with all comments (~10%) and sometimes my replies on Mastodon didn’t carry over to Lemmy (I don’t even know if this one will!) so there’s still work to be done to get things working just right!