The code can be readily adapted for other web services that use the MediaDevices API, so I didn’t want to tie the name down to Google Meet. On the other hand, h

The code can be readily adapted for other web services that use the MediaDevices API, so I didn’t want to tie the name down to Google Meet. On the other hand, having a unique name is counterproductive to an extension which is dependent on another service. People search for Google Meet; I’d have to try a lot harder to get them to remember Mercator. “Mercator Studio for Google Meet” sounds like a fair compromise though. I’ll think about that.