Andy would you do a video that explains the difference between meshcore and Reticulum? If this is just a light weight client of Reticulum. Would be good for beginners to clarify all these differences in mesh networks. Keep up the great work, meshing is the way forward for decentralized networks.
It's a bit odd yes. And if released ... hopefully not one of these "we're only 'documenting' on discord" projects... because... discord is useless for documentation. competition is great and important, but with this little information, reticulum / rnode sounds better to me personally.
Thanks for the update Andy. Ya, Scott's a great guy, I've installed two versions of his firmware so far, sounds like he's made a lot of progress lately, that's great news! I've got two T-Decks with GPS, Altimeter, Atmospheric Pressure, Temperature, and Humidity GY-BME280-3.3 Sensor Modules, ready to add the latest firmware. I wonder if it will support some or all of these sensor modules? Fun stuff!
It's like busses, you want an encrypted, bring your own grid communication network and three come along at once! I still haven't had a good play with Reticulum yet, so I need to have a think and a plan what nodes I want to run. I'm still a bit loyal to Meshtastic because it's the most fleshed out in terms of it's own grid, but I'm glad we have more things to play and experiment with!
Meshtastic have an 'our way or the highway' mentality. I tried making Meshtastic-compatible software, but they got very nasty. I'm glad, actually, because it forced a re-think of the mesh space, and was the catalyst for creating MeshCore.
I wouldn't even deal with meshtastic guys . When it first came out I tried to go on their discord and learn , but their heads are too big. They are too smart. Glad to see some competition. Good for development. And that ripple radio guy is top shelf . I'm just waiting at this point to see how all this turns out. Before investing in which system I wanna go with. That lilygo paperless looks like a good piece to get.
looking forward to trying this. although i just got meshtastic going at the weekend lol oh well. let us know when there is an android app and web flasher.
That's superb. So many questions to be answered. Is there a phone app for the heltec3? Can the module be interfaced directly via serial? How does the protocol cope with moving nodes? The guys at Meshtastic seemed concerned about how my routing would deal with moving nodes.
is it? we don't think it's robust or all that useful, but get recommended the video just the same as you, and we complain about it. i think it makes sense. given how few people use it, it'd be actually more surprising the other way around
Very cool! Nice to see the t-deck receiving some much needed love. Hope to see this routing system implemented in meshtastic as well so the two platforms can co-exist
So Q1.) Will "Meshcore" be available for all / be able to be used / flashed onto all or most "Mesh" devices Q2.) How will "Meshcore" deal with mobile units with regards to knowing the best route from device to device.
What's the gist of the routing algorithm? Distance vector multicast? Have you looked at the IETF MANET work by chance? You mentioned that it isn't always flooding. Some detail about when and why it doesn't would be great. There is no dearth of homebrew mesh routing algorithms that hit one or another scaling wall pretty hard, but there has been a lot of good work out there in places like the IETF that anyone can use.
when you send a message using meshtastic, for it to get to a remote destination the strategy is called "flood routing." This means that every node that gets the message, if it is not the destination, will send the message on to N other nodes. Hopefully then some node will happen to send it to the destination node. Simple, but not smart. meshcore sounds like (because I cannot see the code) it will be intelligent routing, where some nodes will know how to reach other nodes, and they will send the message only to where it needs to go to get to the destination instead of sending it everywhere and hoping.
@@Sylvan_dB So, in less populated areas this may not work properly I suppose (depending on the implementation, like you, I have not seen any code). Especially with mobile devices which may be out of reach of each other at any point.
@@Sylvan_dB I just saw someone ask the "mobile devices" question further down, and Andy replied that in those cases, this system will revert back to flood routing. So, doing the same as Meshtastic does now.
Does this work with current meshtastic devices on the old software or do you have to use a complete different operating system? Does it guarantee message delivery like TCP/IP? and you get message confirmation from sender /receiver?
While I am interested in Meshtastic.This seems like the natural evolution of things, and now its getting very interesting and more useful and user friendly. The GPS and mapping is an awesome feature.
Had me excited at first. I thought we might see a way to use multiple protocols on a single radio. I'm looking into running a mesh system that blends Meshtastic and RNodes and Reticulum networking but over a single radio but using the protocols as software. It's my hope to get this working with 802.11ah to help with mass adoption. My home state of North Carolina in the US is building out a statewide mesh after the Helene disaster, it's Meshtastic at the moment.
You can do multiple profiles with this tdeck firmware but theres no reticulum yet, Scott was planning on doing it but we ended up working on this idea first. Halow would be great for linking reticulum transport nodes. I've been wanting to try LoRa on 2.4Ghz for a while too.
@@andykirby It'd honestly be interesting to get 2.4ghz development going... like... if there was a way to make all those USB wifi dongles suddenly do LoRa instead with a software update. suddenly software adoption goes up even if it is an imperfect solution as it'd get more eyeballs onto a project.
We are working on software to run RAK concentrators with meshtastic to run multiple channels for. Network to get below 25% usage per channel. It’s a lot of work and very little support but if you can find a software guy..perfect
@@singletona082 you cannot use wifi chipset for lora - those are hw radios supporting only 802.11. LoRa is proprietary technology only working on semtech chips. even on 2.4 you need either sx1280 or lr1121.
You could write a custom repeater that also tunnels via the internet, and supports the end-to-end routing. (like Reticulum does) I wouldn't want a repeat of the debacle that was MQTT on Meshtastic, tho.
Posted my questions to the github. They boil down to my wanting to make use of yoru repeater and branch path model rather than amorphous to take advantage of that infrastructure for mroe than just real time SMS style communications and have more going on.
Any idea for a feature to support a mobile repeater, i.e. a repeater mounted to a vehicle or carried by a traveller, such that it can courier messages from one area to another, carrying stored messages with it. Won’t support instant messages but would be good for a fidonet-like email system that can get a message to someone distant over a few days
There's nothing stopping anyone from making a mobile repeater (a friend already has one, in a backpack). For ad-hoc deployment, out in the wilds or wherever, is perfectly reasonable use-case. It's just in a more public setting, if repeaters moved around too much the paths that get built up can become invalidated, and nodes would need to re-initiate path discovery, taxing the mesh.
@ Exactly. What i’m talking is a repeater having a dedicated “courier” mode, where the mesh sees it and says “This node can’t forward instant messages to the larger group, but it can see this list of nodes we cannot see, and can be sent direct messages for those nodes, which will be stored for a few days until it moves and can send to that node when it gets there. Mesh + sneakernet
@@andykirby why not integrate and work with the reticulum guys? I'm looking for a backbone solution that all the different mesh solutions can ride on also...
@andykirby so the messege will be routed to where the mesh think the node is, but it moved so it won't deliver, and than the messege will flood to the whole mesh?
Oh no, wish I hadn't seen this. I still not got those 2 Indicators going yet (the ones I messaged you about) and now this?!! lol it's only ££££ (Taximeterman)
Do all client devices need a screen like the T-Deck or is there an app for Bluetooth bssed devices too? Really hope there will be a WisBlock RAK4631 build ❤
I have a suggestion. Please explain at the beginning of the video why I should care about this like just 10 seconds how is this thing useful ? Because I watched the entire video and still have no idea wtf I could use this for lol .... is it a wifi repeater? Could I use this to get better wifi in my shed? What is it?
Mixed feelings. Already hard to get people to know about and use Meshtastic. Now a new protocoll which effectively splits up the community again. Which means fewer nodes, less range for everyone. Would love to hear that these can somehow work together, to keep the mesh-range.
Yep, its getting too fragmented now. If the goal is to make another messaging system that people can use, and there are people to talk to. Then just stick to one, and help it grow.
Hmm. I feel like what you're setting up relies heavily on nodes being stationary and longterm. I would imagine if you put one or two mobile nodes in your system they would either overwhelm the grid doing recalculations all the time or would simply not work. Also in most places overcrowding simply isnt much of an issue for folks when there arent many nodes around. I dont think we should split the community but rather work with the MT-developers to have a more intelligent and adaptive routing approach (or at least be compatible with MT)
I see a similar experience you had with ebikes . UNDERSTAND THE BANDWIDTH PROBLEM CANT BE JUST OVERLOOKED an cant be overcome...How about adding anti collision from drones to escooters......
Guys, just port a usable rnode front end for using the tdeck with reticulum. Cause you can use Lora, kiss modems, and ethernet to truly build an open mesh…
From what I have seen and heard, if you attempt to merely follow a specification of a published protocol thee meshtastic devs think they own your project
@@recrof I mean, the fact there is a pending PR currently targeting the 2.6 release that moves away from Flood Routing as a default, but as a fallback, means this looks to be changing.
why not contributing to meshtastic development to work on the issues it has, instead of reinventing the already widely existent wheel? i dont like that tbh.. Does it atleast stick to legal limits? Offline Maps planned? Placable pins (wich custom names)?
Nice idea but it's not possible, meshtastic have not shown willing (there's a lot of stuff behind the scenes that I'm not going to go into) Offline maps of course! The tdecks aren't connected to the Internet!
@@andykirbyon meshtastic why is there an option for hamradio. Doesn't it switch off encryption? I have it in the it in the ham position on all my nodes. Mick
@@KB1UIFyep but I don't understand why the meshtastic system has and asked if you are a radio amateur and an option to enable it or not as it isn't ham bands.
@MakeDoAndMend1 My understanding is Meshtastic can also be used on devices that work on Ham radio frequencies. Also, different countries have different regulations.
@ of course but that negates the fact everyone would have to adopt it over meshtastic to, well, make a mesh, or you will simply be using it alone. And you can on the t-deck but not on the majority of hardware current LoRa users are using
Meshtastic is power hungry. I made some prototype code just to test the range and first thing I did was to sync the nodes and use deep sleep and make them wake up in same window to exchange messages.
Legitimately I don't know any hams using 433 in the US. Nor do I know any that are running MT in "licensed mode" because they'd be an island to themselves
@@andykirby @andykirby its the new setting you tub has snuck in it changes your video to auto dubb an ai language french, spanish, german ect. over your original audio you can change it in your utube studio ,settings upload defaults ,advanced settings
what do you mean, "start" ? There are multiple different LoRa protocols for these little devices, some older than meshtastic. WiFi had dozens of forks before it was standardized. Ethernet was only one way of wired networking connecting computers. Fork them all and let the best protocol win!
Andy would you do a video that explains the difference between meshcore and Reticulum? If this is just a light weight client of Reticulum. Would be good for beginners to clarify all these differences in mesh networks. Keep up the great work, meshing is the way forward for decentralized networks.
any details on platform? weird not to have the code public at any stage of development before making an announcement... Hopefully not a bad omen.
It's a bit odd yes. And if released ... hopefully not one of these "we're only 'documenting' on discord" projects... because... discord is useless for documentation.
competition is great and important, but with this little information, reticulum / rnode sounds better to me personally.
Reticulum has been in development for 8 years and is open source. That's where I'd put my money.
Code literally went live an hour after the video 😁
Thanks for the update Andy. Ya, Scott's a great guy, I've installed two versions of his firmware so far, sounds like he's made a lot of progress lately, that's great news! I've got two T-Decks with GPS, Altimeter, Atmospheric Pressure, Temperature, and Humidity GY-BME280-3.3 Sensor Modules, ready to add the latest firmware. I wonder if it will support some or all of these sensor modules? Fun stuff!
It's like busses, you want an encrypted, bring your own grid communication network and three come along at once! I still haven't had a good play with Reticulum yet, so I need to have a think and a plan what nodes I want to run. I'm still a bit loyal to Meshtastic because it's the most fleshed out in terms of it's own grid, but I'm glad we have more things to play and experiment with!
That sounds pretty cool I'd like to try it out on my t-decks and my heltec v3s I have at home
I like this idea. I have so many different types of Meshtastic devices, what does the roadmap look like?
Why not work woth the developers of Meshtastic to impliment this into the Meshtastic firmware??
They have no interest in working with us.
@@andykirby Can you elaborate on this?
Meshtastic have an 'our way or the highway' mentality. I tried making Meshtastic-compatible software, but they got very nasty. I'm glad, actually, because it forced a re-think of the mesh space, and was the catalyst for creating MeshCore.
I wouldn't even deal with meshtastic guys . When it first came out I tried to go on their discord and learn , but their heads are too big. They are too smart. Glad to see some competition. Good for development. And that ripple radio guy is top shelf . I'm just waiting at this point to see how all this turns out. Before investing in which system I wanna go with. That lilygo paperless looks like a good piece to get.
looking forward to trying this. although i just got meshtastic going at the weekend lol oh well. let us know when there is an android app and web flasher.
Meshtastic has exploded in last 6 months in my area. Network is too bloated. Can't wait to try this out!
sounds great. Looking forward to testing that on heltec and rak
I cannot wait. I have to set up a big mesh this summer, I'll be watching closely
That's superb. So many questions to be answered. Is there a phone app for the heltec3? Can the module be interfaced directly via serial? How does the protocol cope with moving nodes? The guys at Meshtastic seemed concerned about how my routing would deal with moving nodes.
What about r-node for reticulum network ?
looks spectacular. I have some t-decks waiting to test this release.
Very cool, I use Meshtastic for my family when we go on adventures. Would be happy to try this out!!
Incredible the number of people here complaining who obviously don't even use Meshtastic...🤡🙄
is it? we don't think it's robust or all that useful, but get recommended the video just the same as you, and we complain about it. i think it makes sense. given how few people use it, it'd be actually more surprising the other way around
Can we have a video explaining how the routing works
Really cool! Solving problems🎉
Wanna test this in The Netherlands, you down??
This is incredible. Thank you very much.
This is awesome! I need it now! :P
Thank you for what you do for the Mesh community!
This looks very cool. Looking forward to seeing more information released about it and having a chance to give it a try.
Very cool! Nice to see the t-deck receiving some much needed love.
Hope to see this routing system implemented in meshtastic as well so the two platforms can co-exist
sounds really nice
please dont forget the rak&t114 support 😊
RAK is next, they are the best for repeaters 😉
Especially for solar nodes 👍
So
Q1.) Will "Meshcore" be available for all / be able to be used / flashed onto all or most "Mesh" devices
Q2.) How will "Meshcore" deal with mobile units with regards to knowing the best route from device to device.
Could you find out from Scott if its possible to do an android app to start people off with the basics of the mesh network?
Thank you for your effort. THIS, is how amateur radio is perpetuated. Good job!
What's the gist of the routing algorithm? Distance vector multicast? Have you looked at the IETF MANET work by chance?
You mentioned that it isn't always flooding. Some detail about when and why it doesn't would be great.
There is no dearth of homebrew mesh routing algorithms that hit one or another scaling wall pretty hard, but there has been a lot of good work out there in places like the IETF that anyone can use.
Brilliant guys! Can’t wait to use this.
Awesome ! Waiting for FW for other base boards and kits .. I presume Meshtastic grid will be invisible to this app ?
What would be the reason for replacing meshtastic with this thing you are talking about ? what is the improvement? totally not get it
Looks like its a bit prettier and its allegedly more reliable
@@TheHeartOfFenris also Meshtastic's routing is hopelessly broken and doesn't scale
when you send a message using meshtastic, for it to get to a remote destination the strategy is called "flood routing." This means that every node that gets the message, if it is not the destination, will send the message on to N other nodes. Hopefully then some node will happen to send it to the destination node. Simple, but not smart.
meshcore sounds like (because I cannot see the code) it will be intelligent routing, where some nodes will know how to reach other nodes, and they will send the message only to where it needs to go to get to the destination instead of sending it everywhere and hoping.
@@Sylvan_dB So, in less populated areas this may not work properly I suppose (depending on the implementation, like you, I have not seen any code). Especially with mobile devices which may be out of reach of each other at any point.
@@Sylvan_dB I just saw someone ask the "mobile devices" question further down, and Andy replied that in those cases, this system will revert back to flood routing. So, doing the same as Meshtastic does now.
I hope it'll also work as an app, and not only on the T-deck. I just sold mine 😅
Does this work with current meshtastic devices on the old software or do you have to use a complete different operating system? Does it guarantee message delivery like TCP/IP? and you get message confirmation from sender /receiver?
Sounds like a completely different system and firmware.
While I am interested in Meshtastic.This seems like the natural evolution of things, and now its getting very interesting and more useful and user friendly. The GPS and mapping is an awesome feature.
Andy any idea when Lillygo are going to have the tdecks back in stock mate ?
There’s plenty available on AliExpress…
Had me excited at first. I thought we might see a way to use multiple protocols on a single radio. I'm looking into running a mesh system that blends Meshtastic and RNodes and Reticulum networking but over a single radio but using the protocols as software. It's my hope to get this working with 802.11ah to help with mass adoption. My home state of North Carolina in the US is building out a statewide mesh after the Helene disaster, it's Meshtastic at the moment.
You can do multiple profiles with this tdeck firmware but theres no reticulum yet, Scott was planning on doing it but we ended up working on this idea first. Halow would be great for linking reticulum transport nodes. I've been wanting to try LoRa on 2.4Ghz for a while too.
@@andykirby It'd honestly be interesting to get 2.4ghz development going... like... if there was a way to make all those USB wifi dongles suddenly do LoRa instead with a software update. suddenly software adoption goes up even if it is an imperfect solution as it'd get more eyeballs onto a project.
We are working on software to run RAK concentrators with meshtastic to run multiple channels for. Network to get below 25% usage per channel. It’s a lot of work and very little support but if you can find a software guy..perfect
Same here. I imagined an underlying system that could talk to all platforms. But it seems like yet another platform.
@@singletona082 you cannot use wifi chipset for lora - those are hw radios supporting only 802.11. LoRa is proprietary technology only working on semtech chips. even on 2.4 you need either sx1280 or lr1121.
Well done Andy. Can't wait. 👍
Hi. Can repeaters be connect via the internet? Is there a possibility of a similar protocol on bluetooth or wifi that could be routed via a repeater?
You could write a custom repeater that also tunnels via the internet, and supports the end-to-end routing. (like Reticulum does) I wouldn't want a repeat of the debacle that was MQTT on Meshtastic, tho.
Is it possible to setup repeater to repeat only signed packages?
Posted my questions to the github. They boil down to my wanting to make use of yoru repeater and branch path model rather than amorphous to take advantage of that infrastructure for mroe than just real time SMS style communications and have more going on.
Sounds great, Andy!
Any idea for a feature to support a mobile repeater, i.e. a repeater mounted to a vehicle or carried by a traveller, such that it can courier messages from one area to another, carrying stored messages with it. Won’t support instant messages but would be good for a fidonet-like email system that can get a message to someone distant over a few days
There's nothing stopping anyone from making a mobile repeater (a friend already has one, in a backpack). For ad-hoc deployment, out in the wilds or wherever, is perfectly reasonable use-case. It's just in a more public setting, if repeaters moved around too much the paths that get built up can become invalidated, and nodes would need to re-initiate path discovery, taxing the mesh.
@ Exactly. What i’m talking is a repeater having a dedicated “courier” mode, where the mesh sees it and says “This node can’t forward instant messages to the larger group, but it can see this list of nodes we cannot see, and can be sent direct messages for those nodes, which will be stored for a few days until it moves and can send to that node when it gets there. Mesh + sneakernet
RAK Wisblock Support?
Exciting new project! I hope lots of others jump onboard too :)
Isn't this?What reticulum was supposed to really be solving the routing and the networking
Right? It's kinda strange 😅
Reticulum is fantastic but we wanted to build the lightest weight system with a really low overhead.
@@andykirby why not integrate and work with the reticulum guys? I'm looking for a backbone solution that all the different mesh solutions can ride on also...
How will messeges sent to mobile nodes will find their targets?
It'll revert to flood routing like it would on first discovery of a node.
@andykirby so the messege will be routed to where the mesh think the node is, but it moved so it won't deliver, and than the messege will flood to the whole mesh?
Oh no, wish I hadn't seen this. I still not got those 2 Indicators going yet (the ones I messaged you about) and now this?!! lol it's only ££££ (Taximeterman)
Do all client devices need a screen like the T-Deck or is there an app for Bluetooth bssed devices too?
Really hope there will be a WisBlock RAK4631 build ❤
Nice! Here's to giving it a try
Thank you
He’s back!
Back A-gain
Andy's back, tell a friend
you forgot to include the link to Scotts article
He's just going live
Is meshcore a separate project or something that will be integrated into meshtastic?
No
Awesome 👌
Is meshcore the new transport or is it a complete replace?
It is a complete re-think from the ground up. Works entirely differently to MT
If we already used meshtastic for atak could we use the meshcore with it? Would it need a separate plug in?
I would think so. The mesh is fully open source you can do whatever you want with it!
I have a suggestion. Please explain at the beginning of the video why I should care about this like just 10 seconds how is this thing useful ? Because I watched the entire video and still have no idea wtf I could use this for lol .... is it a wifi repeater? Could I use this to get better wifi in my shed? What is it?
It's.a messaging device (like SMS) but rather than relying on mobile networks the idea is to make it peer to peer but across the entire country.
that sounds insanely tiresome for his regular viewers. you know, the people that watch the videos
Like the old packet 1200 / aprs of old..... Close to Vara chat on FM too..
Sounds great.
Ah man... was hoping for reticulum news :(
Lots of progress on reticulum!
Is the API under CMake? I would love to see if its possible to integrate this mesh network stack with other firmwares like Tactility OS.
Very interesting. Thank you.
Mixed feelings. Already hard to get people to know about and use Meshtastic. Now a new protocoll which effectively splits up the community again. Which means fewer nodes, less range for everyone. Would love to hear that these can somehow work together, to keep the mesh-range.
Kinda like when everyone abandoned Betamax for VHS
Yep, its getting too fragmented now. If the goal is to make another messaging system that people can use, and there are people to talk to. Then just stick to one, and help it grow.
@@ChatGPT1111 Except you can re-flash your 'Betamax' hardware, and turn it into a 'VHS' :-)
Your meshtastic boys are going to be real upset with you.
When's the release?
The core Source is on github already.
@ And how about this firmware from the vid?
Hmm. I feel like what you're setting up relies heavily on nodes being stationary and longterm. I would imagine if you put one or two mobile nodes in your system they would either overwhelm the grid doing recalculations all the time or would simply not work. Also in most places overcrowding simply isnt much of an issue for folks when there arent many nodes around. I dont think we should split the community but rather work with the MT-developers to have a more intelligent and adaptive routing approach (or at least be compatible with MT)
You can _try_ to work with MT, but they won't necessarily work with you.
I see a similar experience you had with ebikes . UNDERSTAND THE BANDWIDTH PROBLEM CANT BE JUST OVERLOOKED an cant be overcome...How about adding anti collision from drones to escooters......
Meshages! - Very cool indeed! 👍😎
Guys, just port a usable rnode front end for using the tdeck with reticulum. Cause you can use Lora, kiss modems, and ethernet to truly build an open mesh…
Does it also solve the very limited capacity of users that meshtastic has?
Very interesting
There's already a thing called Meshcore
Maybe this is it?
in google there are more than one other meshcore project. lets rename... meshynet ;-)
Big news but no firmware
Standby this is a teaser. FW will be in the next couple of days.
Awesome!
Did I got it wrong? Repeaters? Really? What about "off-grid"? No point without p2p.
yes it will work p2p you dont have to use repeaters :-)
@@andykirby2:25 is it? 🤔 well, that's a relief😅
Think the discord link has expired
Any idea if this tech could be integrated with meshtastic? Did you check with them? It would save you setting up a whole new ecosystem
it couldn't be integrated, because they decided that managed flood routing is the only way.
And the MT devs have made it crystal clear that they do not play well with others.
From what I have seen and heard, if you attempt to merely follow a specification of a published protocol thee meshtastic devs think they own your project
meshtastic project owners are knobs unfortunately. Their code is absolute trash anyway. Onwards and upwards.
@@recrof I mean, the fact there is a pending PR currently targeting the 2.6 release that moves away from Flood Routing as a default, but as a fallback, means this looks to be changing.
Wow，love it
We're is firmware,!?
Why would you go against Meshtastic and not try to help and improve that network?
Let's goooo!!
why not contributing to meshtastic development to work on the issues it has, instead of reinventing the already widely existent wheel?
i dont like that tbh..
Does it atleast stick to legal limits?
Offline Maps planned?
Placable pins (wich custom names)?
Nice idea but it's not possible, meshtastic have not shown willing (there's a lot of stuff behind the scenes that I'm not going to go into)
Offline maps of course! The tdecks aren't connected to the Internet!
@@andykirby sad
If you are radio ham. I don't think you can use encrypted messages. But not 100% sure. Mick
no you cant, but this is not on the HAM bands its on ISM
@@andykirbyon meshtastic why is there an option for hamradio. Doesn't it switch off encryption? I have it in the it in the ham position on all my nodes. Mick
Correct ! No encryption on Ham Radio.
@@KB1UIFyep but I don't understand why the meshtastic system has and asked if you are a radio amateur and an option to enable it or not as it isn't ham bands.
@MakeDoAndMend1 My understanding is Meshtastic can also be used on devices that work on Ham radio frequencies. Also, different countries have different regulations.
Wont this require everyone dropping meshtastic and using a new platform? Unless everyone else adopts it, your going to simply be chatting to yourself
You can use multiprofile firmwares so you can flick between the different systems.
@ of course but that negates the fact everyone would have to adopt it over meshtastic to, well, make a mesh, or you will simply be using it alone. And you can on the t-deck but not on the majority of hardware current LoRa users are using
Why recreate the wheel. Just fork meshtastic and make it better
It's great to have options. I find Meshtastic boring.
I went off meshtastic after I started committing code to the project. The code is absolute garbage. Not forking is the best call frankly.
😂
Meshtastic is power hungry.
I made some prototype code just to test the range and first thing I did was to sync the nodes and use deep sleep and make them wake up in same window to exchange messages.
@andykirby What about t-beams
Very coooooooooooooool
wheres Scotts video?
He is just going live
@@andykirbycheers
Good. Can't wait till people find the best one and we can just use that. Creating a new mesh network is the newest p*ssing contest and it's annoying.
Snooze or lose!
they should rename meshtastic to messtastic
Cool
Thank you for this interesting and inspiring video! Seems very promising! vy73 from Hamburg/Germany, Dietmar, DL4HAO :)
433 more popular with us hams
You can run it on 433 😁
I wonder if this is really true, and if so then why?
Legitimately I don't know any hams using 433 in the US. Nor do I know any that are running MT in "licensed mode" because they'd be an island to themselves
@@garrisonsanin Israel we have almost country wide ham 433mhz mesh.. not very active though
Reticulum is better than meshtastic
Ohhhhh... ROUTING.... not sudo rooting
No auto dubb it ruins videos
Don't know what that is.
@@andykirby @andykirby its the new setting you tub has snuck in it changes your video to auto dubb an ai language french, spanish, german ect. over your original audio you can change it in your utube studio ,settings upload defaults ,advanced settings
the day the forks start, is the day the hobby dies.
it would help if the Meshtastic project moved any faster than molasses!
what do you mean, "start" ? There are multiple different LoRa protocols for these little devices, some older than meshtastic.
WiFi had dozens of forks before it was standardized.
Ethernet was only one way of wired networking connecting computers.
Fork them all and let the best protocol win!
You are blinking more times than meshtastic could bounce around Mars and back watch yourself back
concentration trying to describe a complex subject.
ROUTER_LATE role seems perfect for BBS nodes