Send message from extension to GNome desktop application - google-chrome-extension

I want to make a Firefox / Chrome extension that sends messages to a GNome application made in GTK. I have read something about D-Bus. But I am not clear if it is possible to use that API from a Javascript extension. Is there any method to send messages between browser extensions and GNome API?

Related

Push Notification for Chrome browser extension?

I built this Chrome browser extension plugin and can't figure out if there is a way to receive a server message from my Backend service in the plugin pretty much like the push notification for iOS.
e.g. notifying the user an event (from the backend) has happened and display this message in the plugin
I spent time looking into Chrome extension's documentation. They don't seem to have API similar to push notification for the Chrome extension.
Is there any other way do achieve this?

Is it possible to detect a user's browser(like IE11) and then redirect them to another(like Chrome)?

I have an application that does not work in IE. I am assigned the task of redirecting the user to Chrome if they open the application in any other browser. Is this possible? If not, how can I detect what browser a user is utilizing so that I may display a banner that instructs them to use Chrome?
I have researched this topic but have not found any documentation on this besides the jQuery Browser Rejection plugin
The Dream goal would be to launch chrome if the user has it installed or suggest a download if the user does not have it installed

Chrome extension accessing UWP app?

We have chrome and FF extensions which works with a native messaging app. Recently we developed edge extension and a UWP app which works in the same way. Now the user has to install two separate native messaging apps if they want use any chrome/FF/Edge browsers.
My question is, is it possible for Chrome/FF extension talk to windows UWP app?
Unfortunately no. On Windows, both Chrome and Firefox use the registry to locate the native applications manifest, and Windows Store apps are forbidden from writing to the registry. (ref: Prepare to package an app (Desktop Bridge)
If something changes (Store apps gain the ability to alter the registry, or Chrome and Firefox introduce an alternative way to locate the manifest), then it might be possible. Though likely not via the UWP app directly. UWP apps appear to support standard input and output, but the way they are run prevents access to it. It might however be possible to create an intermediary Win32 app that can communicate with the UWP app via the AppService and the browser extension via stdio.
Afterthought: Enpass Password Manager (win32) was ported to the Windows Store reportedly because of API issues, and has a browser extension for Chrome and Firefox. Might be worth asking them how they pulled it off. I did some more digging, and figured it out. localhost loopback, a custom url scheme, web sockets, and browser verifications is how they are doing it. Not an ideal solution, but it seems to work.

Can i use Chromecast as a server?

Studying the possibility to achieve the following:
We have a CMS that from time to time posts to a web hook a media URL (video) (public internet hosted)
This web hook post we would like to post directly to a ChromeCast which is plugged in to a TV
Questions:
1. Can a web server like nodeJS be installed on a chrome cast?
2. Is it possible to use for example DynamicDNS to link the Chromecast to a domain name so the post from the web hook can be made?
ChromeCast has a sender API which allows you to "send" content to a specific Chromecast. Right now, the sender API works on Android, IOS and Chrome OS. You can read more about it here: https://developers.google.com/cast/docs/sender_apps.
And, here's how a receiver application that would receive your content on the ChromeCast would work: https://developers.google.com/cast/docs/receiver_apps or if you're content is a standard type, then you can use a prebuilt receiver application without building your own.
To answer your specific questions:
Can a web server like nodeJS be installed on a chrome cast?
No, not without enormous hacking and development yourself to basically take over the hardware somehow and get your own stuff to run on it.
Is it possible to use for example DynamicDNS to link the Chromecast to
a domain name so the post from the web hook can be made?
Not that I know of.
The chromecast has an android like google chrome operating system. It is possible to root it, but you will not be able to (to my knowledge) get a server on it. I would suggest taking a look at the Raspberry Pi. You should be able to run a slim server on it. After you get that set up it might be feasible to pass command line commands to chrome or another web browser to display the data you like. A browser is not necessary, but I'm not sure if you know of any other way to display the media.
A different approach would be to have a server anywhere (could be in your home) and have something like the raspberry pi (any computer for displaying the content) connect to a webpage hosted with that server. Using websockets something like socket.io, you could set it up so that the server could send messages (url of video) to the browser session you have open. The javascript of your webpage would then use that message to open that url.

Build Chrome Extension that receives voice input

I plan to build a Chrome Extension that allows users to navigate web pages via voice commands.
To do so, I plan to put my speech recognition program on a backend server that connects with clients via Chrome extension.
Is it possible? I know how to develop an extension, but would appreciate if you could show a way of receiving voice input.
You don't need to modify Chrome.
Until the HTML5 tag gets landed in Chrome, your only option right now is to use NPAPI and include the plugin into your Extension. For more information visit this page:
http://code.google.com/chrome/extensions/npapi.html
You would have to implement a JavaScript audio input API using C++ inside Chromium, being aware that you have to transfer data through the sandbox, then once exported you can use the new API in your extension.
A lot of groundwork has already been done on specifying the audio API, read the details over at W3C:
http://chromium.googlecode.com/svn/trunk/samples/audio/specification/specification.html
Which links to details of a special build of Chrome with some already built samples:
http://chromium.googlecode.com/svn/trunk/samples/audio/index.html

Resources