Oh, I will have to check that out. I was only aware of the official proprietary crapp and meshcore-open.

I feel like I need to clarify my position a little bit. I'm actually in no way against meshcore, and from what little I have used meshcore open, I actually think it does some things way better than meshtastic, that they could definitely learn from. The two biggest things right now that come to mind are 1. Mesh core companions don't relay messages except in that new outdoors mode, which takes them off of the standard mesh and puts them all together on a separate frequency. Makes total sense to me. Though I can see where meshtastic is coming from, making every client also repeat messages, I would think a better option would be for a compromise, where meshtastic would do a 50-50 split, when you very first created the node, and it would choose a 0 or 1, and if it was set to 0, it would be client mute, and if it was set to 1, it would be a client, and therefore, re- so you'd have the best of both worlds, and if it was set to 1, it would be a client, and therefore, re-lay messages, so you'd have the best of both worlds. 2. The region scopes seem like pure gold to keep area specific chatter in that area and reduce congestion on the wider mesh outside that area. This is a feature that I absolutely think meshtastic should adopt in some way.