How does the page serving works again?

[Ruulul]

This question was borned by a simple detail: the description of NomadNet says it is built on top of LXMF, but... over MeshChat, I can see the NomadNet nodes have a different Aspect (nomadnetwork.node instead of lxmf.delivery)

I am interested in making an app that is more user friendly and is both compatible with NomadNet and LXMF, but trying to dig out the source code of NomadNet was not productive

So... what is going on internally? I wanna know, thanks in advance~

[Ruulul]

Okay, lemme see if I am understanding it:

• nomadnetwork.node being the address is solely a matter of how the Destination was created, and you can keep using LXMF as a protocol independent of it;
• The announces inform what the address (like lxmf.delivery or nomadnetwork.node) are, somehow...
  -# I am slightly confused on this point still because the announce has a hash of the identity+address, so I am not sure how the one hearing the announce can derive the address from the hash alone, but if it works it works
• Then, having the address, some peer in the network can know that that application is running in that address, and send an application appropriated package to that address

So far so good?

[markqvist]

All of this is explained in the manual. It's a great idea to read that before jumping straight into doing more advanced stuff.

[Ruulul]

I have read the Reticulum Manual several times until now, and while it helps, a lot of stuff is hard to grasp on the first, second or even the Nth read... and also NomadNet have nearly no reference in how it is implemented

[markqvist]

Yeah, I know. That's not really accidental, either. And I'm definitely not saying the documentation is perfect ;)

Try to think of it not as something you already have an analogue for, and can transfer with a few conceptual modifications. Think of it as though you had never heard about two (or more) machines being able to communicate before. Everything will make a lot more sense.