Also, a lot of nodes tend to flood their battery state for the entire network, which uses up the airtime for something that could be more important like routing information, and also wastes their battery.
Even though things like AlohaNet have been around for years, Meshtastic chose to reinvent the wheel. The primary difference is that Meshcore started with "routing" first, and then save the airtime and therefore battery for routing messages.
geerlingguy did a video on it, and it's highly worth while checking it out. I think he was kind enough to use the term "Beta".
Supposedly the new firmware from Meshtastic fixes a lot of this, but it's gonna be a while for people to upgrade, and I'm not too keen on wasting time again on something if it's not fit to work for it's stated purpose originally.
Meshtastic can also communicate over long distances by relaying through other nodes.
So what's the difference?
MeshCore started out with the concept of static router nodes as well as clients, so it performs better if there is a router nearby to use, otherwise it falls back to flooding.
It was something like this:
1. Router repeats first
2. Weakest repeating device by signal strength next
What if both of those options are in a basement, or say have a damaged antenna, or are miles in the opposite direction of where you want the signal to go?
By simply putting up a router somewhere you might be severely impacting the comms of people at your edge.
I struggled to get messages delivered with Meshtastic in my location. I'll try Meshcore when I get some time.
You can read between the lines here.
I believe the most important is to keep an option to be able to setup gateways between the different networks and if possible the messaging systems.
Like for example yggdrasil, tor, I2P dn42 and the clearnet are interconnected. What is really cool.
Have folks ever tired to even communicate with the devs? They are the most toxic group of individuals that I have ever encountered. Saying that they act like children is insulting to little kids.