4 ms·
I don’t really like this from the Reticulum repository: “[…] The Reticulum Protocol is defined entirely and authoritatively by this reference implementation, […
by kurokawad 7mo ago
I don’t really like this from the Reticulum repository: “[…] The Reticulum Protocol is defined entirely and authoritatively by this reference implementation, […]”.
The reason there are so many apps trying to solve offline decentralized communications is that there’s no standard protocol or path for it. Everybody tries to sell their app as the real solver.
Also, OS-dependant (iOS/Android only apps) won’t give any progress to the state-of-the-art.
- Sabrees 7mo agoThe repo defines the protocol it authored. Is it better not to define stuff and leave it fuzzy? Unclear why you formed the impression this was only iOS/ Android? That is not in fact the case https://github.com/samuk/awesome-meshcore https://github.com/samuk/awesome-meshcore
- khimaros 7mo agoMeshcore != Reticulum, but you are right that it is not limited to those platforms.
- kurokawad 7mo agoBecause the linked app (columba) is an Android app. I should have specified I was referring to that. But I don't follow why you quote MeshCore, it has nothing to do neither with columba nor Reticulum (the protocol columba uses).
- bigfatkitten 7mo agoWhile not ideal, it’s better than the usual situation with new RFCs etc, where no implementation actually exists, and the specification is unusable for the purpose of properly defining how an implementation should actually work.