webextensions-examples VS native-messaging-c

Check out Firefox examples on github, you’ll like it, I’ve had great experience learning from them to add nifty features to my browser:

https://github.com/mdn/webextensions-examples

This is a place to start https://github.com/mdn/webextensions-examples.

I downloaded Content script registration repository from MDN webextensions-examples on GitHub.

In some cases it does Banning a user doesn't magically make your bugs go away; Can't get response in Ubuntu #506.

It's pretty straightforward with the provided example.

I tried a couples: for example this one is working perfectly but not printing using console.log https://github.com/mdn/webextensions-examples/tree/main/commands

I believe there are already extensions for that. In fact, there's even one on the Mozilla Developer Network's GitHub called Theme Switcher which is essentially a dropdown menu with all of your themes.

I modified this https://github.com/mdn/webextensions-examples/blob/main/native-messaging/app/ping_pong.py example Python Native Messaging host slightly to point to python3 on the shebang line and pass -u to python3

You dont need much. You can use this https://github.com/mdn/webextensions-examples/tree/master/discogs-search as a template

Ultimately what I am trying to do is test the simplicity and efficiency of using a local server versus using Native Messaging, which I have working https://github.com/guest271314/native-messaging-c, https://github.com/guest271314/captureSystemAudio/blob/master/native_messaging/capture_system_audio/capture_system_audio.c.

Yes. I use Native Messaging to do that as well https://github.com/guest271314/native-messaging-c. Far less overhead cf. HTTP. Nonetheless I am trying to improve the implementation.

I would suggest sending valid JSON. Here is a Native Messaging host written in C which sends JSON to the client https://github.com/guest271314/native-messaging-c.

I will probably adjust the variable names in your code and publish here https://github.com/guest271314/native-messaging-c including link to your answer.

For the C version which is now just an echo of input https://github.com/guest271314/native-messaging-c/tree/main repeat steps 1.-6. Instead of pinning the icon to address bar, navigate back to chrome://extensions, click "service worker" which will open a DevTools window for the background MV3 ServiceWorker context, then run this code in the console