Thanks! Let 100 flowers bloom. But the congested network was meshcore or meshtastic? I think at that time it should have been meshtastic and this is exactly the reason why everyone is migrating from there to meshcore right now.

50m from the entrance to the building in dense urban neighbourhood with my lora32 board as bridge inside the apt on n-th floor without any external BT antenna. Quite decent for BT I would say.

v2 is working FLAWLESSLY with lilygo lora32 (v2.1.1.6) for bridge. Reconnecting automatically, keeps connected. My congratulations and big thanks.

Have you witnessed the congestion in LoRa (on meshtastic? or?) in Portugal last year at the apagon day? Or this is just calculations? As I remember people mostly just were listening to FM radio, but I'm not sure what was the real situation in 868mhz that day as I didn't have meshtastic installed.

I 100% agree that reticulum is muuuuuch more work of art, starting from rnode and finishing with apps. I'm missing it every time I open MeshCore. Bitchat is also quite good - sleek and fast, but as to the MeshCore........ - this is a mess as of now, especially with the web app on mac, bugs on bugs on bugs... Though working somehow.

Working with Lilygo Lora32. Need to reload 3 times before the bridge is visible in the mesh group of bitchat, but finally bridging ) Cool )

wow, really cool!! )) Here there are not so many MeshCore nodes yet, especially outside of big cities. But it's really kind of start merging - Nostr, Bitchat, MeshCore, ... What is lacking right now - is coverage (not so many nodes even in cities, maybe in central Europe is different) and inter-city/inter-countries connectivity (virtually absent). Finally to bridge these local clusters into one network we will need either kind of signal towers - radio nodes placed on some mountains, within direct line of sight (with all the restrictions like power consumption, line throughput, vulnerability etc.) or kind of exit nodes with satellite comms. As the satellite network is growing, maybe this will be the simplest way in some years. But this would increase already big dependency on Musk's services, which is not good.

also we are quite used to the async mode of communication since 200x (signal, emails etc.), it's hard to accept that if the receiver is not online and reachable right now (and with LoRa this is almost never the case) they just miss your ping or message forever. This is the next big thing for the mesh networks IMO - how to make the async messages work.

Found the dynamic map of MeshCore nodes, here it is, much better than the standard one - can be filtered on last 7/14/30 days visible nodes, much more reliable: https://analyzer.letsmesh.net/map also there are another views at the same site - packets, channel, nodes lists etc. Very useful.

I somehow was not able to answer in thread, but just quoted and the client created a separate note ))))) Here is it: https://njump.me/

Here I also see huge amounts of MeshCore nodes popped up about 1-1.5 months ago, but they are in different locations from the Meshtastic nodes, so it seems that this is not that all old Meshtastic nodes just switched over during a couple of weeks, it's really a new and growing adoption. Did we have some big event with MeshCore presentation around the October-December? You need time to buy and install nodes. ) BTW, the similar map of Reticulum nodes does not have it's page on the Reticulum site as far as I can tell, but need to be searched separately: https://rmap.world/ Maybe this is also one of the small but important adoption things which make the difference. Here is the map for Meshtastic: https://meshmap.net/ (also separate site) Here is for MeshCore: https://meshcore.co.uk/map.html (here is for MeshCore, integrated) BTW, why MeshCore is trademarked?? How sure we are about the trustworthiness of the developers, of the map and the quality of the software (e.g. in terms of encryption)?