> In this case, you can visit kulfi://http-e9b1c82b43206c96173848ed0afad2fe633fdc8a02ba391a3d37, which is where the Talk App lives. What is the DNS story for this platform? Or are you intending to be kind of like a replacement for Syncthing where each endpoint has to explicitly approve the other and thus discovery is left as an exercise to the reader? Actually, even after further thought, I am still able to rename my…
Kulfi App is a web browser that talks kulfi protocol natively, so you can open kulfi:// natively. malai is the server side part of this story, and can expose existing HTTP/TCP services over kulfi:// network.
For DNS, here is my initial deign/thought: https://github.com/kulfi-project/kulfi/discussions/55
For access control, we are working on a "what-to-do" service, which is an bunch HTTP/JSON APIs, that will be called by the malai (which runs on your server, or even as part of Django/Node/Golang once we wrap malai as a cffi library, and write corresponding Python/Node etc packages). You will be able to write the what-to-do in any framework you like, and we will maintain a general purpose open source what-to-do service.