@Edent what's so bad about <div> ... or: Why do you want to avoid them?

[freddy@social.security.plumbing]

@Edent my experience from the Berlin mesh. the berlin meshtastic network is overcrowded with badly positioned devices and the routing algorithm essentially passes messages into sinkholes. Reschability snd reliability are bad not despite but because of the many devices. Default forwarding off and limiting it to tower/rooftop locations would probably be better than every device meshing. 1/2

[tuxlife@mastodon.social]

@Edent @dan I use Meshcore in The Netherlands because it’s a much more community and network, I started with two Heltec v3’s that are USB powered and affordable, as most nodes they support both MT and MC. One is a repeater the other a companion, later I added an additional companion that is battery powered and mobile (Sensecap T1000-E). Initially I didn’t get much response on either, so I added a large external antenna.

[freddy@social.security.plumbing]

@Edent But the issue is unfixable because coordination is essentially impossible. People buy cheap, don’t care or don’t update firmwares.

I haven’t tried meshcore, but guess: the fact that meshcore isn’t a default with conscious participants has a higher chance of succeeding. 2/2

[hanscees@ieji.de]

@Edent @krahabors you have devices aimed at running of grid as a repeater. Then you need a low power device. heltec t114 will do, there are many more of course
If you have a device on constant USB power, or battery that should last a day heltecv3 or v4 are fine.

[hanscees@ieji.de]

@freddy @Edent in Netherlands people are switching to meshcore because it's better suited for busy areas: not all devices pass on all information. If you have many devices doing that the mesh, which is radio based, will physically stop working well because of overload.
And also it send further in distance

[edent@mastodon.social]

@resiliencetheatre ha! I've just had someone say go with MeshCore because Meshtastic isn't fully open 😆

[warteschleife@troet.cafe]

@Edent Of course there are technical details that could be considered when chosing between #meshcore and #meshtastic. My opinion is: If you want to communicate or use it for emergency, check what the majority in your area is using.
Even if you chose the best technology, its not much worth if you're the only one 😀

[resiliencetheatre@infosec.exchange]

@Edent I believe firmware is GPLv3 for Meshtastic. Tricky topic agree, but some features were paid only on Meshcore?

[boxly@hachyderm.io]

@Edent absolutely! Already looking forward to it so much!

[resiliencetheatre@infosec.exchange]

@Edent This is nice example of situation where I'd like to have out-of-band comms: https://www.reddit.com/r/meshtastic/comments/1qd2z97/mestastic_on_family_cruise_worked_great_for/

[warteschleife@troet.cafe]

@Edent Keep in mind that many hardware devices could run #meshcore as well as #meshtastic. So you could try one mesh and still switch if you revise your decision.

[julf@social.secret-wg.org]

@Edent MC is good for a pretty much static infrastructure if you have reliable and stable repeaters and want to reach long distances. MT is better for ad-hoc networks for a limited area (a town or an event for example) where you can't rely on semi-permanent repeaters.

[jtonline@mastodon.me.uk]

@Edent I've so far stuck to meshtastic because it seems more, well, meshy. My use case doesn't include joining a wider local mesh so it's exactly what I need.

If your use case is joining a wider local mesh then you have to go with the (local) crowd, which you'll probably need a non-mesh network to find out about. Probably Facebook but who knows!

I'm currently using Sensecap and RAK card devices which work pretty well.

[qbitzerre@unbound.social]

@Edent I want this for unicode.

[rachel@norfolk.social]

@Edent that’s the overall feeling I get, too. I get I just need to buy a device and see

[obsidian@milliways.social]

@Edent I'm much in the same boat with similar intentions so no real world experience yet.

I've got my eye on a couple of Heltec v4 devboards. v4 because they support gnss which is interesting for a few 'fun' use cases I have with friends and while it seems Meshcore is the way to go in NL as its more widely used, I understand incan switch to meshtastic pretty easily using same hardware.

Heltec appear to have decent shipping methods from their own site but I've seen similar if not exactly the same ones on usual suspect large online retail shopfronts.

[jolt@telegrafverket.cc]

@Edent I would go with meshtastic because of the bigger reach in terms of community. Meshcore has cool functions, but it's not that big yet. BUT! Since they devices are pretty cheap, especially if ordered bare from china, why not both?

[psfshr@mastodon.me.uk]

@dan @Edent I gave up on both Meshtastic and Meshcore.

(Ran MT for ~3 mo, and MC for ~6 mo)

Meshtastic was largely dead in our area (might have better luck in a more built up area).

Meshcore seemed to be mainly somewhere for people to talk about Meshcore and send “Test!” “RX” messages back and forth.

Unless you have a known, stable, local mesh I wouldn’t rely on either for emergency use…

[taylorhayis@mastodon.world]

@Edent Neither are actually open source, I used Meshtastic for a year. Great for cities / festivals / mucking around.
Been using meshcore the last year or so.
Meshcore is MUCH more reliable for permanent setups, and usable for long range. We have like 200 meshcore nodes covering our whole state. Regularly messaging people hundreds of km away 12-14 hops.
This would be impossible on Meshtastic.

[taylorhayis@mastodon.world]

@Edent I dislike Andy Kirby, and he’s investing in / building meshcore with a kiwi dev called Liam. Expecting enshittification in the future.
I trust Meshtastic devs even less 😅