An aggregator can appear to have smaller hashrate than what's behind the scenes. This is useful for remote mining where connectivity might be less robsut. Small amount of data up and out. Biggest concern would be latency if you're too remote, but bandwidth is minimal.

What wireless comms protocols/bands have low latency and low bandwidth? #asknostr

CC nostr:nprofile1qqszw48usckkhs9hcwt3q3np9k2z2c73s8qc0gu3uxqw66cqlq88ukcpz9mhxue69uhkummnw3ezuamfdejj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uq36amnwvaz7tmjv4kxz7fwd46hg6tw09mkzmrvv46zucm0d5hsg27kqm how fast are HF comms?

Reply to this note

Please Login to reply.

Discussion

HF packet runs at 300 baud.

Oof. Maybe for emergency comms. 🤔

You could run something like Reticulum + LXMF over airMAX to WAN links

https://store.ui.com/us/en/category/wireless-airmax-5ghz

Think like a SV2 proxy that does a couple of airMAX hops to some point that has internet access.

Reticulum packets are under 300 bytes, by far the least amount of bandwidth of any protocol I've seen.

https://github.com/markqvist/LXMF?tab=readme-ov-file#wire-format--overhead

Will require a lot of integration work with SV2 and RNS

You can pipe RNS over TCP & UDP

Saw they were working on a reticulum ATAK plugin

Also I saw another person with a Neros handle in the matrix group chat. I think the MIC has found #Reticulum

https://www.neros.tech/

Makes sense. I know some spooks that track FOSS projects for stuff like this.

Prolly good they're keeping up with things

I learned of reticulum via a now-deceased DoD contractor’s posts.

Natural causes?

😬

I know! 😅

Just need a byte stream that can turn into r/w halves.

Both LXMF and Reticulum can ensure message reliability

As I understand it, LXMF is an abstraction layer built on top of the Reticulum API that allows for more featureful applications. Not dissimilar to how Nostr runs on top of TCP/IP.