Meshtastic decentralized/resilient communications sounds quite cool.
I haven’t even gotten my device yet, but was doing some basic research on what software could be built on - but it seems @cypherpunks beat me to it - but with hindsight i should not really have been surprised. Lot’s of good stuff coming from there now.
I really hope Bluetooth turns out to be easy to implement so you don’t have to give up WiFi to stay commented. Is it open source and open to contributions somewhere?
Given how current meshtastic devices are generally smartphone controlled, this also sounds like it could be a good fit for a TOH. At least you’ll remember to charge it by virtue of sharing a battery.
I’m sorry, I probably should look into setting up Git at some point if I find the time.
So far it’s always been a trade-off between developing cool new things and dealing with chores like setting up Git or learning how to publish to the Jolla Store, and the cool new things have usually won.
Yeah, don’t be sorry. I get it I’ve been lucky enough to have time for some of the chores. Of course, I’m running out of money Which means, if I get a J2, I’ll have to turn around and sell it to get you a meshtastic … ah, well, @attah will probably end up with a collection, knowing his love for collecting printers
As someone who uses git and publishes to store - those things are second nature now. Publishing takes a minute. Initial compliance might be a chore… I’m very open to helping out.
Since I’m already tracking changes on two openrepos pages, I’ll put it up tomrrow. I’m going to push all those repos to SailfishOS apps · GitHub so they’re in the commons and not just under my control … @attah are you a member of that repository?
The Meshtastic nodes are dirt cheap, so the hardware it’s not that much of a problem, but I think the guy who was setting them up on the hill has finally given up, since this has happened a few times before.
I’ll have to look into it if I find the time.
All I’d probably need is an example store-compliant Python app plus a spec file to see what they expect it to look like.
I don’t use the SDK because it’s total overkill for Python and QML apps.
There’s at least one native Meshtastic companion app for Sailfish, but I don’t have a PinePhone with a LoRa back, so I’ve no idea how it’s meant to communicate.
The native Sailfish MeshCore compatible companion app now works with Bluetooth and can send public messages. Private messages, however, seem much harder to implement than on Meshtastic.
Sorry, I haven’t released the MeshCore app yet because, as mentioned, I haven’t been able to figure out how to send direct private messages. Public messages do work, though.
If there is enough demand, I could possibly integrate it into the Meshtastic compatible companion app on OpenRepos. They basically do the same thing. It’s a different protocol underneath, but the interface presented to the user is basically the same, so it would probably make sense to have just one app for both, that is if I can somehow figure out how to send private messages on MeshCore.
Thanks very much. Making things work on so many different platforms is a huge task. I have posted on Meshcore Discord to see if there’s any interest in Sailfish/ Jolla there
I have found the difference between the two apps, its in Bluetooth Permissions. In App Manager the three permissions are shown as dangerous. The middle one of the three outlined in red is Bluetooth Scan. In Meshtastic it is granted in Meshcore it is revoked. See images, I hope that this helps
contribution this way. I push those to chum, too.
