For a laugh I looked into compiling the safe-api into wasm and creating a simple SAFE:GET function in a normal browser so I could look at text and pictures on the SAFE network in a browser without needing to proxy it. It’s not that simple of course!
That exercise took me down the path of trying to do a simple SAFE:GET from golang, nodejs, python etc without depending on any maidsafe code, just using quic libraries.
I managed to connect to the vault but quic is still very experimental so I never got past the handshake. Honestly even being able to connect was above my expectations, so please consider this topic very experimental.
It made me wonder, what’s the full spec for doing something like a GET on SAFE, without using rust or maidsafe.
It’s not something I have a clear answer on (or expect to have one any time soon) but here’s some brain dump. If anyone has anything to add that would be cool.
- Uses quic protocol
- Vault offers quic versions of 0xa1a2a3a 0xff00001b
- Looks like messages are serialised with serde using bincode, not sure how cross-language bincode is…?
Anyway, just taking notes on my experiments, if you have any other info or experiments would be cool to hear it.