Sideband
meshnet-lab
Our great sponsors
Sideband | meshnet-lab | |
---|---|---|
9 | 2 | |
231 | 134 | |
- | - | |
9.5 | 8.3 | |
29 days ago | 4 days ago | |
Python | Python | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Sideband
-
Meshtastic: An open source, off-grid, decentralized, mesh network
yggdrasil can use WiFi on Android, I haven't tried it yet - https://yggdrasil-network.github.io/. yggdrasil gives you the ability to use TCP/IP applications over its mesh network but doesn't offer any end-user functionality itself.
Manyverse can use WiFi for decentralised social networking - https://www.manyver.se/. They're currently in the middle of a rewrite of the backend and a protocol switch away from Secure Scuttlebutt to their own protocol currently named PPPPP.
Reticulum/Sideband offers a P2P messaging system over WiFi or other mediums - https://github.com/markqvist/sideband
- Sideband v0.4.0 - with Paper Messaging and better hardware support - has been released
-
Reticulum Development Roadmap
Related programs such as Sideband and Nomadnet has also had their repositories updated with more visible roadmaps.
-
A comparison of various anonymity/privacy focusing networks
Mobile support: Yes, Android only for now though. There is an example Android messaging app that uses Reticulum here: https://github.com/markqvist/sideband. The app source code can be used as an example for others that want to use Reticulum on Android, at least until I get around to writing a full Android development guide. There is some preliminary info in the manaul on the topic here as well: https://reticulum.network/manual/gettingstartedfast.html#reticulum-on-android
-
3 mile text coms no license
While it still requires a few more steps to set up, a system based on Reticulum, using a client like Sideband is a lot more flexible. You can mount the radios in optimal positions, for examples on your roof or another high spot, and Reticulum can automatically bridge the LoRa and your home wifi network, so everyone on the wifi network can share the single radio on your house, without having to connect anything directly to their phones/devices. Here is how one user have utilised this during hurricane Ian.
-
⟳ 0 apps added, 6 updated at apt.izzysoft.de
Sideband (version 20221005): LXMF client
-
⟳ 4 apps added, 10 updated at apt.izzysoft.de
Sideband: LXMF client
-
Are any of you actually working on privacy-related projects?
I have built a few simple communications tools with Reticulum, Nomadnet and Sideband.
-
Internet/ Mobile outage preps
https://reticulum.network https://github.com/markqvist/sideband https://github.com/markqvist/nomadnet
meshnet-lab
-
Meshtastic: An open source, off-grid, decentralized, mesh network
Most of the mobility testing has been performed either in the meshnet-lab[1] or the pineconesim[2].
As the original author of that documentation, it's quite entertaining to have it quoted back to me. :-) In any case the routing "prefers" links labelled as the internet when there is a tiebreak between two peerings between the same pair of nodes, i.e. you are connected to some other device via Wi-Fi and Bluetooth simultaneously.
And while it is true that Pinecone cannot necessarily always make the best routing decision based on public keys alone, aggressive queue management attempts to provide the best QoS for all flows and it scales very well because nodes maintain only a small amount of state about their position in the spanning tree and their position in the SNEK. Importantly, shortcuts can and often are taken when Pinecone switches to tree-based routing as the geometric distance to the destination on the tree is evaluated at each hop. Routing "by the SNEK" is used primarily to find the remote node and as a fallback in case the tree routing fails.
[1] https://github.com/mwarning/meshnet-lab
-
XMPP, a Comeback Story: A Protocol for Robust, Private and Decentralized Comms
Lots of interesting stuff there - thanks :) We're using https://github.com/mwarning/meshnet-lab rather than imunes.net for network simulation currently, but will take a look.
Power usage is looking pretty positive so far; as long as we route the Matrix traffic over the routing topology rather than going full-mesh it should minimise radio usage (the main battery suck, other than screen).
For store-and-forward, honestly using P2P Nodes as intermediaries is an okay approach other than exposing metadata to them. Our plan in the longer term is to switch to loopix-style mixnets to obfuscate the store and forwarding, a la nym.
In terms of joining the network by deriving a private key from a passphrase... yup, that could be cute, although slightly terrifying in terms of the risk of weak passphrases :)
We're hoping to get the P2P network stable in the coming year (although we were also aiming for this year originally :P)
What are some alternatives?
TranslateYou - Privacy focused translator app built with MD3
cinny - Yet another matrix client
Reticulum - The cryptography-based networking stack for building unstoppable networks with LoRa, Packet Radio, WiFi and everything in between.
NomadNet - Communicate Freely
sucks - Simple command-line script for the Ecovacs series of robot vacuums
fake_contacts - Create fake phone contacts, to do data-poisoning.
polyjuice_server
quetre - A libre front-end for Quora
matrix-bifrost - General purpose bridging with a variety of backends including libpurple and xmpp.js
libremdb - A free & open source IMDb front-end.
Element - A glossy Matrix collaboration client for the web.