Usually you'd have your canvas server running in the cloud or on a beefy workstation managing local AI agents and other roles like minio or maild. In such setup, you'd want to connect multiple(or maybe all) compute devices to the same canvas-server instance.
Devices in Canvas are automatically identified by a device ID and an optional device name, it would be good to display this in the browser extension as well.
Feature bitmaps also play a major role in the architecture of Canvas (does not look like that but be prepared!), what browser a tab is coming from can be stored as a feature bitmap or within the tab document itself.
Regardless of the implementation, tabs in the extension should be sorted as
Device ID: Firefox (OS)
tabA
tabB
tabZ
if a device name is set, its Device name (device ID): Browser (OS)
idncsk
commented
1 month ago
Usually you'd have your canvas server running in the cloud or on a beefy workstation managing local AI agents and other roles like minio or maild. In such setup, you'd want to connect multiple(or maybe all) compute devices to the same canvas-server instance.
Devices in Canvas are automatically identified by a device ID and an optional device name, it would be good to display this in the browser extension as well.
Feature bitmaps also play a major role in the architecture of Canvas (does not look like that but be prepared!), what browser a tab is coming from can be stored as a feature bitmap or within the tab document itself.
Regardless of the implementation, tabs in the extension should be sorted as
Device ID: Firefox (OS)
if a device name is set, its Device name (device ID): Browser (OS)
Work NB (d1a34b96): Firefox (Linux)
Work NB (d1a34b96): Chrome (Linux)
Home (cf11b2d4): Edge (Windows)