Doman

You totally can use Meshcore without repeater, and companions can be used like routers. This functionality can be enabled any time using one checkbox in app. It switches the radios to slightly different frequency and enables repeat mode in personal nodes, this gives you one small network. No repeater needed. And in this mode you don't clutter "main" mesh with your local mesh.

The main difference between Meshcore and Meshtastic is how telemetry is handled. In Meshcore to get telemetry the other party needs to request it, whereas in Meshtastic telemetry is sent in flood mode in configured intervals. That's why Meshtastic is better suited for (A)TAK [1]. But because Meshtastic sends telemetry anyway there is less and less airtime for chat messages, and it gets to the point where you can't talk to people. For small groups this is fine, for bigger groups/meshes this is no bueno.

[1] https://tak.gov/ - (A) stands for Android app.

Files can be downloaded here: https://huggingface.co/CohereLabs/cohere-transcribe-03-2026/...

And someone has already converted it to onnx format: https://huggingface.co/eschmidbauer/cohere-transcribe-03-202... - so it can be run on CPU instead of GPU.

Scroll Lock is really good key for that in my opinion. If your keyboard does not have it exposed then you can use some remapping program like https://github.com/jtroo/kanata

I am using a window manager with Waybar. Voxtype can display a status icon on Waybar [1], it is enough for me to know what is going on.

[1] https://github.com/peteonrails/voxtype/blob/main/docs/WAYBAR...

bunny.net is not reachable for me too... really funny

https://imgur.com/a/8gh3hOb

Awesome! Could you please elaborate how to do it or post some good/not outdated links?

Really cool, but please work a bit on controls for smartphones. Holding a button pops up a browser's menu.

> This leaves higher application code to handle duplicated messages.

True, better send twice than never.

> the client connects later than the server send

Server only responds, never sends anything.

> overwhelming the network

"broker" is handling it nicely

I strongly agree that zmq will not fit in every use case. Always search for best option.

We implemented KISS state machine based on TCP timeouts and server response.

Pseudocode:

  Send msg to server
    if socket timeout:
      reinit socket and send again
  Recv from server
   if recv.msg != 'ok':
     send again
   else
     remove msg from storage

One message has from few to few hundreds Kilobytes. Messages are stored and sent as custom binary data for better compression (better that protobuffs). ZMQ takes complexity of raw tcp sockets away and this is what we needed it for. As much and as little.

We are using 0mq for monitoring of electric vehicles fleet. Millions of messages every day (hundreds of GB), zero problems with bad internet connection (common in moving vehicles). Every sent message is received regardless of connectivity issues. Just a little implementation annoyances here and there but it is serving us well since 2015.

Someone is sending spam via YouTube. Link is already disabled. Sent from: https://vgy.me/NdJHGg.png. Really creative. Think twice before You click anything.

We are using this for addon synchronization in our community through Arma3Sync. On server side we need to "build" repository - it just generates .zsync files, then clients are downloading just diff. Update size came down from 10-15GB to <3GB.

Really nice tutorial is being made here: https://simpleisbetterthancomplex.com/series/beginners-guide...

Author uses recent version of Python and Django and is building with You something useful.

They are already programmed to avoid being smashed from behind. Watch these two cases [0:47, 1:54] https://youtu.be/JwknRVjUBCg?t=47 https://youtu.be/JwknRVjUBCg?t=114