

Here is the homepage, and that is not what it says: https://meshtastic.org/


Here is the homepage, and that is not what it says: https://meshtastic.org/


I promise you I am not lying to you. I may be mis-understanding you.
Here is the source code for Meshtastic firmware: https://github.com/meshtastic/firmware
But I am assume that we have a different understanding of what is and what isn’t open source.


Don’t worry, I wouldn’t ban you for this.
Yes, the physical modulation implemented by LoRa transceivers is proprietary.
It is not entirely correct to say that the “mesh” itself is proprietary. Meshtastic is open source, even if it relies on proprietary radio hardware. In principle, one could take the Meshtastic codebase and adapt it to a different physical layer.
It is perfectly reasonable to reject a technology because the full stack is not open. That said, once you look closely at most modern digital and RF hardware, you are extremely likely to encounter proprietary ICs, firmware, or physical layer implementations somewhere in the stack.


Yes, you have many options. It depends on how much “from scratch” you want to go.
The simplest method is to purchase a module with the radio transceiver + microcontroller, flash it, and assemble it. If you don’t want any sensors, you can for example purchase from RAK the kit a kit with a ‘RAK19003’ base board + ‘RAK4631’ module (nRF52840 micro-controller + SX1262 transciever) . For Canada, you would pick the 900 MHz version that operates in the 915 MHz band. (https://store.rakwireless.com/products/wisblock-meshtastic-starter-kit?variant=43884035113158)
For an enclosure, you can look up ‘Project box’ or 3D print a case.
If you want to go even more “from scratch”, you can buy a module without a micro-controller (Waveshare core1262, Ra-01SH, Wio-SX1262), and interface with these using a micro-controller via SPI. At this layer it starts to become more of a hassle if you want to implement Meshtastic, because you will need to either copy an existing configuration, or modify the firmware so that it matches the way that your electronics are connected.
Then, if you do not want to purchase a module, you would buy the transciever directly (for example, the SX1262), and assemble your own module. You can look up the schematic of the basic modules to get an idea of what this looks like. For example, you can see the Waveshare Core1262 schematic here: https://files.waveshare.com/upload/c/c1/CoreSX1262_Sch.pdf
If you do not want to rely on an already existing LoRa transciever, but instead use a more general radio transciever, that is also possible. But, more expensive, and is unlikely to match performance. This is something that one might want to do if you already have an SDR transciever connected to raspberry pi and want to use it to interface with LoRa (still, it is much easier to connect a LoRa device over USB). I would not recommend building a meshtastic device from more general transcievers.
AGUCUAGCAUAC
Woah! Congratulations!!! 🥳 🎉


HEY STOP HACKING ME!!!
Ethical DDoS
AMSTERDAM TRIP: 52.37952717594758, 4.898731163397595 -> 52.373726213381254, 4.8991743688343785 -> 52.37307624236834, 4.892481840346751 -> 52.375235597713356, 4.883881824117286 -> 52.364346142549444, 4.882779439603186 -> 52.358151346039655, 4.868920785661565 -> 52.36032825423474, 4.885688072103288 -> 52.38899110197864, 4.8381014035210965
It took 3 walks to the park due to bugs and unhandled exceptions but it worked!
The python script connects to a node that is left at home. The bot can detect and process a message with the following format:
PST
Com: Meshtastic
Sub: Posting via Meshtastic
Bod: Made a python script to create posts via meshtastic messages. If you can see this, the test worked! Posting from the park with no mobile data ^_^
It will parse the message and create a post. So, as long as I can reach my home’s node I am able to create a post.
I would make use of a VPS to serve a directory with the files using Nginx. The VPS is ~$5 /month. You can share the ip or buy a domain name for ~$10/year. If you are not opposed to vibe-coding, you can probably generate the Nginx + HTML config to play through the songs without having to click them individually with little effort.