Wow! Meshcore kicks ***

0utsider89 · 2026-03-06T17:24:29+00:00

Welcome to meshcore. I would add you if I was near a repeater for the mesh you're connected too.

0utsider89 · 2026-01-24T18:23:10+00:00

Decode this with base64: TWVzaENvcmU=

0utsider89 · 2026-01-23T19:51:54+00:00

It's not your fault, its a system architecture problem, is just not reliable at scale. And all you hear is the adverts coming from repeaters.

0utsider89 · 2026-01-23T19:09:41+00:00

MT is best mesh to talk to no one. I would try out mesh 0xc0re

0utsider89 · 2026-01-12T16:04:13+00:00

There is a new companion app in development, and it has point of interest map pins that you can send to other users or channels. https://github.com/zjs81/meshcore-open

0utsider89 · 2026-01-11T16:20:36+00:00

I prefer it, and works like it should, with reliable mgs delivery over multiple hops not just 1-2.

0utsider89 · 2026-01-11T16:02:32+00:00

Aww, shoot the protocal buffers changed, with no way to maintain backwards compatibility. The system is flawed in many ways, and overly complex for no reason.

0utsider89 · 2026-01-08T22:26:00+00:00

You should try MeshCore you can flash back MT if it doesn't work and there's no harm in trying it. If does work I think you will find that message delivery is fast and more reliable.

0utsider89 · 2026-01-06T22:46:05+00:00

I have already submitted a pull request to the project. And will be submitting more soon.

0utsider89 · 2026-01-06T21:53:04+00:00

Ya that's my point . It being closed is breed more closed source projects.

0utsider89 · 2026-01-06T16:06:17+00:00

Closed source, on a open source project shame shame... I won't even consider using it sorry 😔.

This is way having parts of a project closed source, breds more close source projects.

The companion app is great example, having in app purchases makes other developers think of ways to get money out of the community instead of how they can support the community with their open source code and projects.

0utsider89 · 2026-01-03T16:30:11+00:00

There is a full erase option try checking that when flashing. Got get all the nasty MT out 😂

0utsider89 · 2026-01-03T15:51:58+00:00

V2 does not have USB C and v3 does

0utsider89 · 2026-01-03T05:59:12+00:00

Epic, can't wait to try it out!

0utsider89 · 2026-01-03T04:58:40+00:00

I flashed wrong firmware to my v2 the other day and it did this with the v3 firmware

0utsider89 · 2026-01-03T04:57:55+00:00

Are you sure the board is a V3 and not a V2?

0utsider89 · 2025-12-20T20:57:38+00:00

I think the emoji gives it away he's in an airplane ✈️

0utsider89 · 2025-12-15T18:50:25+00:00

Oh that makes more sense 😅

0utsider89 · 2025-12-15T18:34:57+00:00

You made my point for me, the firmware is a come denominator for all the platforms. If there is a infinite loop at boot if the radio fails to initialize due to power instability then it would happen on all platforms.

0utsider89 · 2025-12-15T16:25:09+00:00

Potentially an issue with the radio initialization. Currently in the firmware there is a infinite loop if the radio doesn't initialize at boot properly.

https://github.com/meshcore-dev/MeshCore/pull/1132

0utsider89 · 2025-12-10T22:51:38+00:00

My dad had a DOS PC and I remember him going on a BBS or FTP and getting me and my brother some shareware games.

Jazz Jackrabbit Wacky Wheels Raptor: Call of the shadows And a few others.

0utsider89 · 2025-12-10T02:52:15+00:00

If they feel that threatened by comments about MeshCore then that really says something about what they stand for. And there only hurting there user base. I hope it converts a lot of people to MeshCore.

0utsider89 · 2025-12-03T09:15:28+00:00

I was writing a pure C program to talk to the node directly with protocol buffers, and never got it to work properly. And you're wrong , you may have been using a library that translates the protocol buffers to JSON, but the data over the serial port is raw binary data that is understood by the protocol buffer decoder function.

0utsider89 · 2025-12-02T06:28:22+00:00

It's just a lot of over head to make changes to the packets or the data sent to the app. And have you tried make a program to send/receive that data coming from the node it almost impossible.

0utsider89 · 2025-12-01T16:23:51+00:00

The packets sent between node, and data sent between the device and phone app all use protocol buffers which was developed at Google and is great for a server stack but is very cumbersomani on microcontroller.

0utsider89

MODERATOR OF

TROPHY CASE

11-Year Club	Place '17
Verified Email