This is expected right, HTTP is not only used for human consumable web applications but for API servers as well
The bulk of these would just be embedded devices running multiple API services, like port 7547 highlighted in the article is your typical TR-069 service running on most consumer internet routers
I would argue most non-API/non embedded devices web applications would still be running on 80 and 443
Yeah there is, the video chat is not P2P, everyone uses the SFU model where all your media goes through daily's server, so they have to pay for the instances and the bandwidth
So under the hood it's chromium headless and you are streaming screenshots back using an extension
Curious why not run normal chromium and vnc the whole screen back using a web client such as novnc, would have solved most of your "Normal Browser UI things not yet implemented"
The bulk of these would just be embedded devices running multiple API services, like port 7547 highlighted in the article is your typical TR-069 service running on most consumer internet routers
I would argue most non-API/non embedded devices web applications would still be running on 80 and 443