You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to how Chrome/Firefox pop up a dialog asking for permissions, could you consider adding a permissions system for third-party apps to use Arduino Create Agent?
The agent could pop up a dialog whenever a site makes a request to its http server, asking "domain.com is trying to access your serial ports, Allow / Deny". If the user allows, the origin gets added to the config.ini. If the user denies, the origin is stored in some sort of blacklist.
Additionally, it'd be really awesome to have a UI for viewing and revoking access of domains to the serial ports.
When #165 is resolved, to the best of my understanding, the signature keys won't be required anymore.
When implemented, it would effectively make this agent an extension to the web itself, making it the defacto app to use for electronics hobbyists whether they use Create or not. It will also serve as an example for standards bodies to help decide if this (or similar) is worth including in the standards process. (I'm aware of WebUSB and WebSerial, but neither do what this project aims to.)
If browsers were to implement this, to the best of my knowledge, they'd approach it by making permissions even more granular. The browser would implement a 'Port picker" UI, and only allow access to the user's selection, so as not to expose the list of connected peripherals to the web. I'm speculating here of course, but it's the most obvious implementation, considering security ramifications.
There are several apps that can use this. The most advanced example I know of is BetaFlight, which is currently implemented as a Chrome App, and are in trouble because Google has end-of-life'd Chrome Apps. I'm working on a similar app too. We all need to have this native layer, and it feels stupid to duplicate the work you've done. Instead, IMHO, it'd be much more awesome to focus on just this one project and make it awesome for everyone.
The text was updated successfully, but these errors were encountered:
Similar to how Chrome/Firefox pop up a dialog asking for permissions, could you consider adding a permissions system for third-party apps to use Arduino Create Agent?
The agent could pop up a dialog whenever a site makes a request to its http server, asking "domain.com is trying to access your serial ports, Allow / Deny". If the user allows, the origin gets added to the config.ini. If the user denies, the origin is stored in some sort of blacklist.
Additionally, it'd be really awesome to have a UI for viewing and revoking access of domains to the serial ports.
When #165 is resolved, to the best of my understanding, the signature keys won't be required anymore.
When implemented, it would effectively make this agent an extension to the web itself, making it the defacto app to use for electronics hobbyists whether they use Create or not. It will also serve as an example for standards bodies to help decide if this (or similar) is worth including in the standards process. (I'm aware of WebUSB and WebSerial, but neither do what this project aims to.)
If browsers were to implement this, to the best of my knowledge, they'd approach it by making permissions even more granular. The browser would implement a 'Port picker" UI, and only allow access to the user's selection, so as not to expose the list of connected peripherals to the web. I'm speculating here of course, but it's the most obvious implementation, considering security ramifications.
There are several apps that can use this. The most advanced example I know of is BetaFlight, which is currently implemented as a Chrome App, and are in trouble because Google has end-of-life'd Chrome Apps. I'm working on a similar app too. We all need to have this native layer, and it feels stupid to duplicate the work you've done. Instead, IMHO, it'd be much more awesome to focus on just this one project and make it awesome for everyone.
The text was updated successfully, but these errors were encountered: