Define You:
Is your feature request related to a problem? Please describe.
Right now we don't have a good solution for addressing offline situations. Say you're at an event like dweb, and the Internet goes down. It would be simple to self-host apps on the router on the LAN but browsers today don't support verifying local SSL certs. Without too much difficulty, the router could be updated to redirect local app-based domains to the IP of the server on the LAN, but the HTTPS verification won't work.
Describe the solution you'd like...
We need to invent a protocol for trusting the local router/gateway to act as the certificate issuer.
So there needs to first be a way of identifying the router's IP address (shouldn't be hard). Then trusting that entity to sign certificates for other domains in a "LAN mode". I.e. when this "LAN mode" is enabled, the browser will trust the router's public key to sign SSL certs for any other domain. Then these signed SSL certs will be given to the servers that are running apps on the local network, and the peersky browser will consider them valid certs.
Describe alternatives you've considered?
Alternatives are using completely different networks and setups and browsers that are built on top of completely different custom tech requiring rewriting all apps using those other toolkits, e.g. Holochain and related.
Approach to be followed (optional):
Think I described above, please let me know if you have questions or ideas.
Define You:
Is your feature request related to a problem? Please describe.
Right now we don't have a good solution for addressing offline situations. Say you're at an event like dweb, and the Internet goes down. It would be simple to self-host apps on the router on the LAN but browsers today don't support verifying local SSL certs. Without too much difficulty, the router could be updated to redirect local app-based domains to the IP of the server on the LAN, but the HTTPS verification won't work.
Describe the solution you'd like...
We need to invent a protocol for trusting the local router/gateway to act as the certificate issuer.
So there needs to first be a way of identifying the router's IP address (shouldn't be hard). Then trusting that entity to sign certificates for other domains in a "LAN mode". I.e. when this "LAN mode" is enabled, the browser will trust the router's public key to sign SSL certs for any other domain. Then these signed SSL certs will be given to the servers that are running apps on the local network, and the peersky browser will consider them valid certs.
Describe alternatives you've considered?
Alternatives are using completely different networks and setups and browsers that are built on top of completely different custom tech requiring rewriting all apps using those other toolkits, e.g. Holochain and related.
Approach to be followed (optional):
Think I described above, please let me know if you have questions or ideas.