Panda_

Overall this post seems a bit like you've got a grudge against the project. Is it related to the fact you made a post about your vibe coded SPORE project which looks inspired by Reticulum?

Not including a link is quite odd...

Try disabling the default AutoInterface in the config, that can cause problems due to some routers choking on UDP. If it still crashes anything, that's almost certainly a bug you can report

> robust protection against abuse

I would say it has a fairly reasonable number of protections with things like being able to prioritise certain interfaces and controlling the announce rate from a node and rate limiting the number of announces a destination makes. What in particular is abusable?

Mark accepts outside contributions over LXMF using git patches. The main communication method is over Reticulum Relay Chat using clients like NomadNet (made by Mark, unintuitive but works well) which is basically IRC and is purely sending messages to everyone in that channel at that time and is centralised around self hosted servers.

Reticulum packets include a hop count of how many nodes it’s been through (to prevent packets looping indefinitely) and the destination address. Two way links use tables on each node to reverse the route back to the origin and don’t use origin addresses.

The worst part privacy wise could be the announce packets which include a hop count and the address for the origin so if you had enough interfaces you could roughly say where a node is on a network graph (geo locating that is an entire other problem)

Privacy also depends on what interfaces you communicate over, eg TCP reveals IP addresses to the nodes you directly connect to (combine with hop counts to see if a packet definitely originated from that node), LoRa gives an idea of how close it might be because of its range limits and the fact radio emissions can be located.

The author of Reticulum's take is that the implementation is the specification, so if another implementation works with the standard Python one and implements enough of it's features then it implements Reticulum.

I suppose it means it's easier to develop the protocol only having to update one Python codebase but it does mean other implementations are kinda in a state where there isn't anything to properly verify they work.

There's also a issue with quite a few vibe coded implementations that don't actually properly work filling the space.

People do use it but it's definitely a small community. It has the NomadNet Page protocol which is basically small no client side script webpages (forms and links only) in a fairly bandwidth efficient form.