rns.recipes

I think it is time to connect the scattered users in DK, and inform collectively about agreed upon LoRa frequency, etc.

If someone here holds the reticulum.dk domain please send a message on my LXMF address stated here (6f4a9614574b726773cb1bda54bef948) so we can talk to get some info on it! Or I will probably buy another domain soon-ish.

I think we should run united frequencies across reticulum in europe per the rationales from lew palm (see 9d7531049009043e23c395e391811b8e or https://leviculum.network/posts/united-frequencies-of-europe):
frequency = 869463000
bandwidth = 125000
spreadingfactor = 8
codingrate = 5

I also created the room #reticulum-copenhagen here on rns.recipes RRC channel (feel free to add rooms for other DK cities of course or one for DK is maybe good, but personally I like more narrow localities and work towards the potential to dissolve national borders).

Lew Palm's "rationales" he can keep to himself. Frequencies and settings are very much a question of locality, laws, availability, interference, and also there can be multiple LoRa nets on a local basis. So pretending to talk for everyone on a continent is very much Lew-Palmy immature - it commands respect, that is undeserved, obedience, that is totally absurd and thinking, that we all "should" put a specific frequency and go with it shows understanding of the radio world, that is basically very shallow. Also, the word "governance" rings wrong in the RNS world. We have already had many governors pass and go here...

aetherlab wrote:

Also, the word "governance" rings wrong in the RNS world. We have already had many governors pass and go here...

My personal favorite are the group that took over Matrix, renamed everything "R2ticulum", and established the "Reticulum New Governance". They seem to be LARPing Soviet Union style committees, have meetings where there is a 'Chairman' of rns who makes decision on how the protocol should operate, they even take notes and everything and share it with the other 'official members'.

Makes me wonder if they go around wearing jackboots and matching uniforms while holding skype calls. Some serious nutjobs out there.

Hi, this is so nice!! - I have been going around not knowing how to connect with people :) So seeing this thread is a huge joy. So ANY chatter is highly needed.

I am not asking for something to be a specific way. It is just right now it is completely darkhole out there and I would love to build up a net with others- and have some potential guidelines or encouragements.

Within the next half year I expect to put up 2-3 nodes in CPH area and on Vestsjælland area and do some testing if I can reach Fyn.

I know there is also #nordisk on the rns.recipes RRC - just in case we want to connect with some of our upstairs neighbors.

My primary worry was mostly just to figure out what not to put your settings on. Right now the Meshcore and Meshtastic communities are pretty well established in most of Denmark.

I am not experienced enough to know and recommend what not to do - but it has just been one of my main concerns. But maybe it is not as big of a problem as I think it could be?

I've seen those roles being taken on by various people over the years in an attempt to "govern" and "properly organize" local mesh networks. More often than not, it just fragmented and splitted the communities, so I stopped worrying about it too much. We have radio settings published on our pages and in discovery announces for reference mostly. I think what matters is actually making contact with your neighbors with whatever settings are attainable and then go from there. Full radio RNS meshes are still not common, so most people in our area run hot-spots or point-to-point links. And that usually warrants individually picked settings.

That said, Sideband has a map feature that can match your tranceiver settings to a nearby RNode.

Nickie wrote:

I've seen those roles being taken on by various people over the years in an attempt to "govern" and "properly organize" local mesh networks. More often than not, it just fragmented and splitted the communities, so I stopped worrying about it too much. We have radio settings published on our pages and in discovery announces for reference mostly. I think what matters is actually making contact with your neighbors with whatever settings are attainable and then go from there. Full radio RNS meshes are still not common, so most people in our area run hot-spots or point-to-point links. And that usually warrants individually picked settings.

That said, Sideband has a map feature that can match your tranceiver settings to a nearby RNode.

Problem is right now there are no neighbors and little to no rnodes up in Denmark. I want to set up something but I don't know what to setup as there are no other reference lol

Properly organize in my case is just making a public announcement to say "hey i am here and i am broadcasting here" which I think this thread covers perfectly!

jalict wrote:

Nickie wrote:

I've seen those roles being taken on by various people over the years in an attempt to "govern" and "properly organize" local mesh networks. More often than not, it just fragmented and splitted the communities, so I stopped worrying about it too much. We have radio settings published on our pages and in discovery announces for reference mostly. I think what matters is actually making contact with your neighbors with whatever settings are attainable and then go from there. Full radio RNS meshes are still not common, so most people in our area run hot-spots or point-to-point links. And that usually warrants individually picked settings.

That said, Sideband has a map feature that can match your tranceiver settings to a nearby RNode.

Problem is right now there are no neighbors and little to no rnodes up in Denmark. I want to set up something but I don't know what to setup as there are no other reference lol

Properly organize in my case is just making a public announcement to say "hey i am here and i am broadcasting here" which I think this thread covers perfectly!

That's not really a problem, that's actually freedom to choose whatever is best for you and work off of it. Open your local radio laws and regs and see what you could use with maximum TX power available. It is usually 869.40-869.65, but you better check.

The SF/CR is up to you to decide based on your link-budget and requirements.
Using RNS discovery announces will help other potential neighbors to find your node and establish comms with it.

That's how it works here. Now that Mark has added an operator LXMF address to the announcements, they can even contact you to negotiate on radio settings or just say hi.

that's actually freedom to choose whatever is best for you and work off of it

And I see this thread as a way to invite people to come and experiment and establish some relationships <3

The SF/CR is up to you to decide based on your link-budget and requirements.

I actually haven't found much resources on this - do you have any recommendations in material to read on this?

The recommendation for looking for announces is great. I have been looking around, but again, there are none here - unless I am greatly misunderstanding. I mostly looked at rmap.world and the directory here on recipes.

Really appreciate all the help :)

aetherlab wrote:

Lew Palm's "rationales" he can keep to himself. Frequencies and settings are very much a question of locality, laws, availability, interference, and also there can be multiple LoRa nets on a local basis. So pretending to talk for everyone on a continent is very much Lew-Palmy immature - it commands respect, that is undeserved, obedience, that is totally absurd and thinking, that we all "should" put a specific frequency and go with it shows understanding of the radio world, that is basically very shallow. Also, the word "governance" rings wrong in the RNS world. We have already had many governors pass and go here...

Thanks for this feedback, and to everyone else. They all give depth to this conversation, and I think it is just a step on our way to figure out exactly this in a place with little to no RNS deployment. I can not see the problem with local governance, as it does not exclude other frequencies to be a part of the mesh, that aspect is a built-in in RNS anyway, so it is merely a way to establish a reliable first local connection. A personal aim is to pass on packets reliably from A to B outside TCP, and if I can agree with my LoRa and HAM neighbours what frequencies (also in multiplicities, as I understand different frequencies can can work together in the mesh) are best for my locality, whether it is the same as Netherlands, and it does not interfere, or a disturbed - also by law for that matter - I find it useful. You say that 'governance' rings wrong in the RNS world, but by doing this I also perceive that you are speaking on behalf of RNS as a singular entity, when my aim with this post is to bring together my locality, and figure out our frequencies - on a more collective basis than before - so we are able to communicate. I think the RNS world can be a plurality of networks that can work together, but here we need some - perhaps - organising rather than governance, then. I did not write the blog post, but refer to it to have something to relate with others as a starting point, I did nowhere write that the blog post was a single source of truth. On a second reading, tho, I do see that I reproduce the demanding language in "I think we should...", that was not my intention. I respect your stanzas and also potential history that I am not aware of (since you write Lew-Palmy like as well known phenomenon), but I do hope this reply has brought more clarity to my intentions with this thread.

jalict wrote:

that's actually freedom to choose whatever is best for you and work off of it

And I see this thread as a way to invite people to come and experiment and establish some relationships <3

The SF/CR is up to you to decide based on your link-budget and requirements.

I actually haven't found much resources on this - do you have any recommendations in material to read on this?

I hope this helps a bit to understand radio links:
https://rns.recipes/forum/help/what-do-q-and-s-mean-on-the-rnode-interface#post-1159
And some things about LoRa modules, is you are interested:
https://rns.recipes/forum/build-guides/inner-life-of-a-lora-module-the-e22-400m33s
Mark's writeup about LoRa and a calculator:
https://unsigned.io/understanding-lora-parameters/

https://rmap.world has some nice info for existing LoRa deployments, I've also added a better map to the directories page. Some ops have their LXMF address added too which means you can get in contact with them

Using a single shared parameter set is not ideal. As others in the thread have said, SF/CR are link budget dependent and there is no universal preset that would fit a Reticulum deployment.

For many years, mainly out of laziness lol, I referred to Reticulum as a mesh network. While nodes can "mesh" together, real life Reticulum deployments are usually point to point or a system of hub and spokes versus the traditional flood routed mesh network systems like Meshcore or Meshtastic used as LoRa applications. This gives you a lot more flexibility in choosing just what exactly you can configure.

Also don't forget that you can have more than one RNode interface on a Transport with independent parameters. It would be really neat in the future if point to point links started to make use of 2.4 GHz LoRa more.

spirit I an hanging out in the proposed RRC so we can talk a little more :)

I recently bought a Bobcat Miner 300 which I intend to convert to a Reticulum unit and put it somewhere near Vesterport.

re. frequencies, I landed on this setup here in norway:

frequency = 869431250
bandwidth = 62500
spreadingfactor = 6
codingrate = 5

narrow band to avoid the most common frequencies used by meshchat and meshcore, and a pretty low SF to get the bitrate for nomadpages with more than one or two users.