MeshChatX
MeshChatX is a maintained Reticulum mesh communication client for mesh users that combines LXMF messaging, LXST voice calls, voicemail, contacts, and offline…
Platform availability
Available on 4 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
75/100 Good
- Maintained
- 100last commit 20 days ago
- Popular
- 44164 GitHub stars
- Easy to install
- 654 install platforms, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today, links checked 15 days ago
- GitHub stars
- 164
- Open issues
- 0
- Last commit
- 2026-11-01
- Latest release
- v4.10.7
- Activity
- declining
Checked 20 days ago - source: GitHub (Quad4-Software/MeshChatX)
Resources & Compatibility
Requirements not published yet.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Install the package, then start it Install the wheel with pip, then start it in headless mode (runs without a built-in screen) with meshchatx --headless --host 127.0.0.1. This skips building from source and keeps the first run private, because 127.0.0.1 is the machine itself. source
- Use a separate Python sandbox Create a virtual environment (a separate Python sandbox) before doing a manual install, so MeshChatX’s dependencies stay in their own folder. This reduces the chance of breaking your system Python or other apps. source
- Check plugin permissions first In Settings -> Plugins, preview the plugin’s permissions, signature (a trust check), and findings before granting capabilities and enabling it. This helps you avoid giving an add-on access you didn’t intend. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives (10)
- Briar - Censorship-resistant peer-to-peer messaging that bypasses centralized servers.
- Delta Chat - Uses email as a decentralized chat platform with modern interface, open source code, no central servers, strong privacy controls, and no ac…
- Element
- Element X - It is the brand new, and fastest ever, Matrix client.
- FluffyChat - Multi-platform encrypted messenger supporting one-to-one and group chats, file and image sharing, decentralized open-source design, and ad-…
- MeshCore-Self-Hosted - Self-hosted MeshCore web application with automatic updates.
- Meshtastic - Meshtastic is a project that enables you to use inexpensive LoRa radios as a long range off-grid communication platform in areas without ex…
- SimpleX Chat - SimpleX Chat is a private messaging app that protects your identity by not using phone numbers or usernames.
- Tox - With the rise of widespread government monitoring programs, Tox is an easy to use application that allows you to connect with friends and l…
- bitchat - Decentralized peer-to-peer messaging app offering secure Bluetooth mesh communication, end-to-end encryption, channel-based chats, and priv…
Checked 54 days ago - source: AlternativeTo
Common questions
What host address should I use when starting MeshChatX in headless mode?
Use the command meshchatx --headless --host 127.0.0.1. This runs without a built-in screen and keeps the first run private because it binds to the local machine.
How can I check a plugin before enabling it?
Open Settings -> Plugins and preview the plugin's permissions, signature, and findings. Do this before granting capabilities and enabling the plugin.
Do I need to back up the original Reticulum MeshChat folder before using MeshChatX?
Yes, back up the reticulum-meshchat folder before using MeshChatX. It attempts to auto-migrate what it can from the old database, but keeping backups is recommended.
Why should MeshChatX-Client follow Electron's stable release cycle?
Electron has to be kept up-to-date with a stable release cycle to get CVE fixes for the bundled Chromium. It also helps with other Electron-related security and performance fixes.
Answers sourced from github.com, github.com, github.com, github.com
Community
Collected 49 days ago - public community threads