Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Reticulum, a secure and anonymous mesh networking stack

github.com

Post reply on HN
Print view View original

21–30 of 99 posts

Re: Reticulum, a secure and anonymous mesh networking stack

#21

Post by gpm »

promiseofbeans wrote: post #14
dotty- wrote: post #13

Earlier quoted context omitted.

I saw this too and immediately thought: well, they published this on GitHub which surely has a clause that grants it a license to use the code for training Copilot for Microsoft at a minimum, sooo should've published on another Git platform.

> This repository is a public mirror. All development is happening elsewhere. So if I have code on a personal (but publicly exposed) git server with a license that includes the above quoted terms, and someone decides they want to be helpful and publish a public read-only mirror of my code to GitHub, then they’re allowed to accept that license on my behalf? I never did a thing and yet I’m now in a contract with Micros…

Not a lawyer but I'm pretty sure:

1. Microsoft does not gain the license, but will be able to argue that they aren't intentionally committing copyright infringement in the cases where that distinction matters.

2. If Microsoft does something resulting in damages because they thought they had a license, their indemnification clause kicks in and they can recoup those damages from the user who uploaded it (to the extent that that user doesn't go bankrupt anyways)

3. Likely none of this matters because your license can't prevent activities that weren't prohibited by copyright in the first place, and training doesn't appear to be a prohibited activity at least under US law.

Re: Reticulum, a secure and anonymous mesh networking stack

#22

Post by gpm »

avodonosov wrote: post #16
dotty- wrote: post #13

Earlier quoted context omitted.

I saw this too and immediately thought: well, they published this on GitHub which surely has a clause that grants it a license to use the code for training Copilot for Microsoft at a minimum, sooo should've published on another Git platform.

Not sure GitHub has such a clause. Just looked at their terms and don't see it.

See term D.4., the relevant part of which is

> You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like [...] or otherwise analyze it on our servers; share it with other users

Re: Reticulum, a secure and anonymous mesh networking stack

#24

Post by pwndByDeath »

fooqux wrote: post #7

Anybody have any experience running this on a tdeck? I'm kinda toying with the idea of ordering a couple just to play with.

It is not yet like meshtastic in that. Rnode is more of a lora modem than a lora server. There is a micro recticlum project but not out yet.

Re: Reticulum, a secure and anonymous mesh networking stack

#25

Post by agent86 »

SuperMouse wrote: post #20

I've never seen a bigger network with Reticulum in the wild. And I'm deep into Mesh stuff with several local communities. One of the main reasons of the communities not jumping onto the ship was that it's mostly a one-man-project and most of its Git changes are "Update" "Better Version" "Update" "Cleanup" which makes it basically impossible to track changes.

And, as of 3 weeks ago, the one man is "stepping back from all public-facing interaction with this project".[1]

Further, "Occasional updates may appear at unpredictable intervals, but there will be no support, no responses to issues, no discussions, and no community management in this or any other public venue."

Nothing salacious here - just another one man open source project with a burnt out maintainer :(.

[1] - https://github.com/markqvist/Reticulum/discussions/1069

Re: Reticulum, a secure and anonymous mesh networking stack

#26

Post by agravier »

SuperMouse wrote: post #20

I've never seen a bigger network with Reticulum in the wild. And I'm deep into Mesh stuff with several local communities. One of the main reasons of the communities not jumping onto the ship was that it's mostly a one-man-project and most of its Git changes are "Update" "Better Version" "Update" "Cleanup" which makes it basically impossible to track changes.

So what mesh stuff do you recommend for the uninitiated?

Re: Reticulum, a secure and anonymous mesh networking stack

#27

Post by 405nm »

agent86 wrote: post #25
SuperMouse wrote: post #20

I've never seen a bigger network with Reticulum in the wild. And I'm deep into Mesh stuff with several local communities. One of the main reasons of the communities not jumping onto the ship was that it's mostly a one-man-project and most of its Git changes are "Update" "Better Version" "Update" "Cleanup" which makes it basically impossible to track changes.

And, as of 3 weeks ago, the one man is "stepping back from all public-facing interaction with this project".[1] Further, "Occasional updates may appear at unpredictable intervals, but there will be no support, no responses to issues, no discussions, and no community management in this or any other public venue." Nothing salacious here - just another one man open source project with a burnt out maintainer :(. [1] - ht…

it’s a bummer, but according to folks in the matrix chat, he’s still developing and in touch with some of the community devs.

Re: Reticulum, a secure and anonymous mesh networking stack

#28

Post by agent86 »

agravier wrote: post #26
SuperMouse wrote: post #20

I've never seen a bigger network with Reticulum in the wild. And I'm deep into Mesh stuff with several local communities. One of the main reasons of the communities not jumping onto the ship was that it's mostly a one-man-project and most of its Git changes are "Update" "Better Version" "Update" "Cleanup" which makes it basically impossible to track changes.

So what mesh stuff do you recommend for the uninitiated?

In the LoRA/radio device sense, Meshtastic[1] is probably the easiest to get started with. It's the biggest player in the space, has devices that come pre-installed and configured, the most likely chance of making contact with someone else, etc. MeshCore[2] is the other major player. It's newer and tends to have been adopted by communities that have run into issues with large Meshtastic networks.

If you meant PC-based mesh networking, I'll leave someone more knowledgeable to speak about that :).

[1] - https://meshtastic.org/

[2] - https://meshcore.co.uk/

Re: Reticulum, a secure and anonymous mesh networking stack

#29

Post by AceJohnny2 »

gpm wrote: post #22
avodonosov wrote: post #16

Earlier quoted context omitted.

Not sure GitHub has such a clause. Just looked at their terms and don't see it.

See term D.4., the relevant part of which is > You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like [...] or otherwise analyze it on our servers; share it with other users

That could be boilerplate legalese for "obviously we need access to your code if we're to display and share it (as is the purpose for a public git host)"

Re: Reticulum, a secure and anonymous mesh networking stack

#30

Post by blep-arsh »

agent86 wrote: post #28
agravier wrote: post #26

Earlier quoted context omitted.

So what mesh stuff do you recommend for the uninitiated?

In the LoRA/radio device sense, Meshtastic[1] is probably the easiest to get started with. It's the biggest player in the space, has devices that come pre-installed and configured, the most likely chance of making contact with someone else, etc. MeshCore[2] is the other major player. It's newer and tends to have been adopted by communities that have run into issues with large Meshtastic networks. If you meant PC-base…

I've had some experience with both Meshtastic and Reticulum, and Meshtastic software was mostly unusable for me even with 3-node networks. E.g. a node sends a message and gets a successful delivery notification from the receiver but the receiver fails to display the message to the user. Reticulum was mostly working fine. Haven't tried MeshCore yet.
Post reply on HN