Open tomayac opened 1 year ago
why should it not run on http any main reason for this?
localhost .local domains .local (services via mdns) do not even support https out of the box.
this runs already in privileged Extension context with access to storage api
i extensiv use opfs in my local apps and my awesomeOs prototype which is designed to replace goma at some time with a WebRTC powered live distributed build grid. The basics are working but i am doing it all alone so it takes time but the fundamentals are there and working.
I already got OPFS Working on remote instances via WebRTC and spinning up local webrtc connections is a matter of transsporting the peerconnection.id property to a other context so i can run this already via local webrtc on http and in any other context.
think about it like devools protocol and comlink and all that or the puppeteer carlo ipc but via webrtc and a local webrtc connection only needs the id string as identifier for the initial connection handshake.
via a local webrtc connection you can reduce the context linking to a single id property that is a string this is awesome
Currently, the extension runs independent of the protocol, but it should only ever run on
https:
sites.