If it’s trying to talk to a device over Bluetooth or USB, it’s not supported in Firefox. Mozilla refuses to implement WebUSB because they think the danger of letting people accidentally flash malware onto a physical device outweighs the benefits.
There was nothing RESTful or well planned about this API’s interfaces, and the work to do something like that would have been nontrivial. Management never prioritized the work.
At a prior job, our API load balancers would swallow all errors and return an HTTP 200 response with no content. It was because we had one or two clients with shitty integrations that couldn’t handle anything but 200. Of course, they brought in enough money that we couldn’t ever force them to fix it on their end.
There definitely are FOSS projects run by the US government: Ghidra is an open source reverse engineering tool developed by the NSA.
Reminds me of http://www.thecodelesscode.com/case/21
It’s probably using WebView, or whatever it’s called where an android app brings up a browser window. If you have Firefox as your default web browser, apps will use it instead of chrome. It’s usually pretty nice, because if you have adblock in Firefox you also get adblock in the app.
It’s possible that the sign-in webpage wants to talk to the camera before returning control to the app.