#meshchat — Public Fediverse posts

#reticulum #munich #germany #de #lora is using the same settings popular in #thenetherlands #holland #nl which has a developed LoRa radio #mesh #rns #reticulummesh #meshchat
[[ReticulumNet LoRa]]
type = RNodeInterface
port = e.g. /dev/ttyUSB0
frequency = 869463000
bandwidth = 125000
spreadingfactor = 8
codingrate = 5
see also https://loramesh.org#settings
#frequency 869463000 Hz = 869.463 MHz
#Bandwidth: 125 kHz
#TransmitPower: 22 dBm (max allowed)
#Spreadingfactor #sf: 8
#codingrate: 5

I seem to be seeing that the #ip #ipv4 addresses of some legit #reticulum #nodes are being included in some of the lists used by #suricata #IDS #intrustiondetectionsystem to #blacklist IP addresses, and so they might well end up blocked by your #firewall or #IPS #intrusionprotectionsystem
in particular e.g. database #CINS might be flagging mesh nodes
Please take steps for port 4242
#port4242 normally used by #rns #reticulum to not let bad data spoil the #mesh #nomadnet #meshchat #meshchatx

Ik zag in #MeshChat de mogelijkheid voor relay chat , heb deze als test ook aangemaakt :
ID : b83eb3e5369d00f1bdf5b341ff417ed8
naam : Nederlandstalig
rooms : algemeen / software / hardware / en alle provincies

#reticulum

#reticulum lora #rnode #stationG2 set up to connect via bluetooth to linux #nixos laptop machine which uses #meshchat as the messaging gui.
Gruesome details here https://codeberg.org/adingbatponder/reticulum_nixos_flake/src/branch/main/docs/StationG2setup.md
based on fabulous https://codeberg.org/kraven/g2_rnode_firmware
(with Claude Code to the rescue).

#reticulum #rns network stack update has landed ... https://github.com/markqvist/Reticulum/releases/tag/1.1.5
We are very lucky to get this. Thanks so much to Mark and anyone who helped. #meshchat #loramesh

@debacle they are indeed, some less focussed on just chat than others.

Let me see for links:

- https://github.com/markqvist/LXMF
- https://github.com/liamcottle/reticulum-meshchat
- https://meshtastic.org/

#lxmf #meshchat #meshtastic

@debacle cool chart! The stuff the internet was made for! 🙂

I scanned it and couldn’t see #Meshtastic, #Meshchat or #LXMF .

Are they out of scope?

@dexternemrod @pocketvj Yes but updates do sneak in .....I think. This can be.monitored via alerts from Github. Strangely I had more problems when the #reticulum stack was being updated because making things backward compatible and compatible with all #meshchat versions was not really achieved if even possible... so now, with the "maintenance mode", so long as you can indeed flash your radios (plural, use two to at least be able to talk to yourself 😂) everyone will be on the same "page".

✨️ Nomad NetBrowser v0.2.0 is out!

NOW WITH #LXMF MESSAGING BUILT IN.

Browse Nomad Network µ-pages over Reticulum, right in your web browser.

📨 Send & receive LXMF messages compatible with #Sideband #MeshChat & #NomadNet
📡 Propagation node support for offline recipients
🔔 Unread badge + delivery tracking
💾 Optional message persistence

No Python knowledge required.
Simply install and go.

🪟 Windows installer (.exe)
🐧 Linux .deb package

https://codeberg.org/node-star/nomad-netbrowser/releases/tag/v0.2.0

Best leuk , #Reticulum is niet enkel een chat protocol, het is meer .. zelfs pagina's :-)

Hier een screenshot van #meshchat met een pagina nomad index.

A #reticulum mesh communication platform https://styrene.io/docs/ https://github.com/styrene-lab #styrene #meshchat

#lora #mesh #RaspberrPiZero #sdr #gui #meshchat #meshcore #meshtastic #reticulum Dashboard via http served from raspberry pi zero showing lora radio chats and spectral data https://youtube.com/shorts/Fx0lG-GzBw0?si=uOMgKMeXc8ayuJJc

Wenn die öffentliche Infrastruktur zusammenbricht, ist man auf eigene Lösungen angewiesen. Das Wichtigste vorab: Ein batterie- oder kurbelbetriebenes Radio gehört in jedes Notfall-Set. Behörden verbreiten im Katastrophenfall essenzielle Infos zu Notschlafstellen und Anlaufpunkten über Rundfunk. 📻 Für den Austausch mit Familie oder Nachbarn gibt es verschiedene Funk-Optionen. 🗣️

Zum Artikel (€): https://www.heise.de/hintergrund/Kommunikation-im-Blackout-Diese-Optionen-haben-Sie-11151061.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon

#Blackout #Notfallkommunikation #Katastrophenschutz #MeshChat

#ClaudeCode on my laptop machine can, after a couple of pop-ups, see below, #ssh into my #pizero and monkey around with it..... not bad. The pi zero #lora #rnode is connected to the laptop via a hotspot that the pi zero generates to serve #reticulum #meshchat. The laptop is connected to that hotspot via a dedicated wifi dongle TP-Link Archer T3U Plus AC1300 for dual wifi https://amzn.eu/d/04oLHUGr (running nixos but works for any device with browser). #raspberrypizero info https://loramesh.org/subpages/piboxnode/build_pi_box.html

I have an Acer laptop in the loft running a #lora #rnode on #reticulum and #meshchat on #nixos since over 200 days and it still works. So Nixos was stable did not fail for over 200 days. For info about Reticulum etc. one can consult https://loramesh.org

Does anyone have an idea if the npm worm issue affects the most recent #reticulum #meshchat packages in view of the dependencies? Can one use #meshchat version 2.3.0 without any worminess concerniness? My current version is v2.2.1-era code. The JavaScript JS dependency tree really stayed the same, so upgrading to MeshChat 2.3.0 does not appear to add new npm-specific exposure that could be relevant. It seems to leapfrog the Shai-Hulud

#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

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).