🚀 Neuer intuitiver #lxmf #messenger für #android der #bluetooth LE nutzt:
https://github.com/torlando-tech/columba
#Reticulum #reticulumnetwork #columba #bitchat #sideband #meshchat

#Reticulum #MeshChat
A simple #mesh network communications app powered by the Reticulum Network Stack.
https://github.com/liamcottle/reticulum-meshchat
#Linux #Windows #macOS

@Em0nM4stodon
All this reads like a signal-generated campaign.

It’s much more future-proof to go for serverless/distributed systems like #reticulum / #meshchat #jami and such.

No us-jurisdiction, not a single person to rely on. _Meredith_ this, _Meredith_ that - do you _want_ to be in yet another person cult?

#reticulum #tcpip #network voice calls (of a certain sound quality) using #meshchat encrypted (free) #telephony #rns #reticulummeshchat
https://youtu.be/j4J2rRpYzLw

#reticulum #rns in #nixos
A beta #flake that installs (amongst other things) #meshchat #reticulummeshchat and #nomadnet
https://codeberg.org/adingbatponder/reticulum_nixos_flake
#derivation #nixospackages
The flake was hammered out using chatGPT iteratively from a non-AI base flake. #reticulumnetworkstack #reticulumnetwork
See my take on the context and Why NixOS here: https://www.loramesh.org/#nixos

A #nixos #flake that builds a #derivation that #package & install #nomadnet 0.1.0 & #meshchat 1.1.0 from #github python source code. For #reticulum #network. This is a beta work in progress, done using chatGPT iteratively, and is my first attempt at packaging something for nixos. Time will tell if this holds up. Uses python #setuptools & #buildPythonPackage
#lxmf ver 0.8.0
#rns ver 1.0.0 https://codeberg.org/adingbatponder/reticulum_nixos_flake

#nixospackages This is experimental and beta - see readme file for issues

#meshchat #reticulum #LoRa
It seems that it is important for all #rnodes in a given #meshchat based #loramesh #mesh to update to the latest #meshchat version to ensure all rnodes can function as intended.
https://newreleases.io/project/github/liamcottle/reticulum-meshchat/release/v2.1.0

Has anyone managed to make a message #bridge between different #spreadingfactor #sf #lora #rnodes using #reticulum #rns : either using the same single computer and two different #rnode radios (on the same frequency), or using two rnode radios on 2 different computers connected by #wifi? I seem to get this not working "out of the box" because of #collisions of lora packets of the two rnodes. Has anyone managed to bridge lora rnodes by putting in a transmission delay in #reticulum e.g. #meshchat ?

Peer-to-peer chat via Bluetooth is the hype with (apparently poorly designed) #bitchat

Wouldn’t #reticulum #meshchat (https://github.com/liamcottle/reticulum-meshchat) do that, but
- mature
- well-encrypted
- (massively) scalable
- without the limitation to Bluetooth

?

#askfedi

🔒✨ Oh, look! Jack Dorsey's back at it again, this time with a Bluetooth LE mesh chat app that screams "IRC nostalgia" while trying to convince you it's the future of secure messaging. 📡💬 Because clearly, what the world needs now is yet another messaging service to fix vulnerabilities — we just hope it won't crash faster than a GitHub Actions script. 🚀🤦‍♂️
https://github.com/jackjackbits/bitchat #JackDorsey #BluetoothLE #meshChat #secureMessaging #IRCnostalgia #techNews #HackerNews #ngated

Getting reports of #reticulum #meshchat version 1.22 not being able to message nor ping #version 1.21 . Anyone else get this?
#reticulummeshchat #meshchat1dot21 #meshchat1dot22
https://github.com/liamcottle/reticulum-meshchat

This is probably the simplest and most user-friendly introduction to #RNS (#Reticulum network stack)

https://github.com/liamcottle/reticulum-meshchat

It even builds network maps for you on the fly.

Right now I'm just using my internet service, but it would also route through a LoRA radio transceiver properly configured. Or any other communications interface.

#MeshChat #Mesh

Connected and tapping! With the Raspberry Pi Zero W 2, a Waveshare e-paper touch hat and a decent amount of coding, we have a device that can read the announce stream for NomadNet.

#Reticulum #MeshChat

A first & second #reticulum #rnode each on a #raspberrypizero each providing their own #wifi #hotspot & running #meshchat on http://<IP_1> :8000 & http://<IP_2>:8000 (different hotspot IP addresses)
using these instructions https://medium.com/@thakuravnish2313/how-to-set-up-a-persistent-raspberry-pi-hotspot-with-dhcp-f2519c3d5898 & https://loramesh.org/subpages/pi_install.html & two wifi adapters https://amzn.eu/d/6SzEJww
in a #nixos #thinkpad allows both rnodes' meshchat GUI interfaces to be used at the same time on one laptop. Useful for monitoring multiple rnode radios outside or in the attic.

How can #reticulum #meshchat on an rnode X suddenly lose the ability to send/receive messages from one particular #rnode A, when all other rnodes B & C continue to work fine and communicate with X? When restarting the rnode X the problem goes away....
Never seen this before. Normally either every message route between A & X and C & X and B & X works or nothing works.
Is there a routing issue? (Announces were made from all radios and plenty of time taken).

If a #reticulum #meshchat instance with a #lxmf address on one computing device has 4 identical #lora #rnodes #rnode interfaces, each with same settings of frequency #spreadingfactor #sf, each rnode having a #directional #yagi #antenna in close vicinity, will transmission to a sender of a #deliveryconfirmation (#downlink) from 1 antenna to the sender's direction, be messed up due to local #collision at rnode 1 of different attempted #acknowledgement signals of the other 3 near rnodes?

Setting a decent #deliverylimit in #reticulum #meshchat for an #rnode interface that matches a given radio parameter set (or sets) (#spreadingfactor #sf etc.) helps avoid the sad scenario that an rnode uses up its 10% maximum legally permitted #dutycycle allowance for that #radio #ismband when trying to send or resend payloads that stand no chance of 100% delivery in a reasonable time frame. https://loramesh.org/SF

With a #RaspberryPiZero2W & #usbhub https://www.waveshare.com/wiki/USB_HUB_HAT_(B) possible to use 4 #lora #radio #rnodes at same #reticulum #meshchat interface. Can use 4 different sets of radio parameters at one #LoRa #radio interface. Can use 1 radio with low #spreadingfactor #sf for short transmissions at high data rate for large payloads like images or accessing #nomadnet #pages and 1 with larger SF for longer range. No need to choose between #meshtasic presets https://meshtastic.org/docs/overview/radio-settings/ ! just use them all ! Magic

It seems to be possible to set a message size delivery limit as defined by the parameter lxmf_delivery_transfer_limit_in_bytes
in https://github.com/liamcottle/reticulum-meshchat/blob/b8d388fa56d4528b1e7311e4210edcc0c15ee959/meshchat.py#L3261
to let each #rnode have its own limit suiting its own #spreadingfactor #sf
#reticulum #meshchat

Can one set the #lxmf #reticulum delivery limit in #reticulum #meshchat on a per #interface basis i.e. per connected #rnode interface? https://github.com/markqvist/LXMF/blob/c426c93cc5d63a3dae18ad2264b1299a7ad9e46c/LXMF/LXMRouter.py#L38
#deliverylimit #DELIVERY_LIMIT
This might help stop #lora #radio channel blocking in case one #rnode of a set of #rnodes at one end-point device use a high #spreadingfactor #sf #lorachannelblocking