Kulfi is the official name of the project, and the name of the "peer to peer internet" "id52/identity based internet", so kulfi net.
Kulfi App is going to be a browser like Google Chrome, available on various app stores, and it will speak both http over tcp and http over kulfi. Kulfi app acts like client (but is also a server, so on your iPhone tomorrow you can install Kulfi, which will let you access any http over kulfi site, and also will run a web server which is exposed over kulfi net for others to access, so my Android phone's Kulfi browser can connect with the your iPhones Kulfi's web server, with no intermediary [1]).
malai is ready now, and it is a Swiss army knife toolkit for working with kulfi net. Currently malai can expose a HTTP or TCP service over kulfi net.
Malai also has a "http bridge" feature, which bridges any malai exposed http over kulfi service with the http over tcp, so people can use regular browsers to access malai exposed HTTP services.
[1]: we are using https://www.iroh.computer/blog/iroh-dns, so their caveats apply.
What's id52?
I feel like I'm missing a lot of context to understand what's being shared here.
We are built on top of https://www.iroh.computer/blog/iroh-dns, and iroh uses the public key as the node identifier. Unfortunately the iroh id is 64 char long, which can not be used in subdomains, subdomains have a char limit of 63, so we are using dnssec base32[1], which comes to 52 chars, and we use that 52 char string as the primary identifier (instead of IP:port, which is used the "old school net" (tongue firmly in cheek), and we call it id52.
e.g. https://github.com/kulfi-project/kulfi/blob/malai-0.2.5/kulf...
$ echo -n c1b2d4463e503765b7422e126ea7ff5633ba5903f97b700ac818 | wc -c
52
I figured as much, but that's an example for an id52, but not a description of what it is.
The actual answer seems to be that these are zbase32-encoded 32 byte iroh node IDs: https://www.iroh.computer/blog/iroh-global-node-discovery