"If at all applicable to your intent, you must design your applications to embrace Store & Forward.

Instead of demanding an immediate answer, your application should act as a patient participant. You create a message for someone or something in the mesh. The network holds it. It carries it from node to node, perhaps over hours or days, waiting for the recipient to appear. When they finally surface, the message is delivered."
https://reticulum.network/manual/zen.html#design-patterns-for-post-ip-systems

#Reticulum #StoreAndForward #Patience

Tolerating Delay with DTN https://hackaday.com/2026/01/19/tolerating-delay-with-dtn/
#Featured #NetworkHacks #Space #Delaytolerantnetworking #Dtn #Nasa #Networking #Storeandforward

Tolerating Delay with DTN

https://web.brid.gy/r/https://hackaday.com/2026/01/19/tolerating-delay-with-dtn/

#Question How would you reimagining, reinventing email & usenet in 2025?

An open, terminal native, low-resource, slow pace, textual/unicode, store & forward, self-configuring, delay & disruption tolerant, inherently private & secure, spam-free, peer-to-peer, trivial to self-host, with self-generated self-owned addresses (eg: ssh public keys) which you can take with you from system to system?

#NomadicIdentities #SelfHosting #StoreAndForward #DelayAndDisruptionTolerant
#EMail #UseNet #ReImagined

#meshtastic #solar #storeandforward node test - just to see if it works 24/7 in winter.... details here https://github.com/orgs/meshtastic/discussions/40#discussion-7416511

Solar node on a 9 m pole trying to run store and forward for #meshtastic #solarnode #storeandforward
see details here https://meshtastic.discourse.group/t/solar-store-forward-pole-node-test/14956

launching a node out of a velux window on a 10 m pole on a foggy bank holiday #meshtastic #solarnode #storeandforward

#meshtastic #solarnode #storeandforward on a 9 m telescopic pole, details see https://meshtastic.discourse.group/t/solar-store-forward-pole-node/14956

You see, (as an example) #GMRS is not allowed to do "#storeAndForward" but does "#linkedRepeaters" which are not considered "store and forward" by the FCC

@mike805 @jeffcliff @brewsterkahle Additionally, for such hostile environments high-latency store & forward networks are better suited than either #Tor or #I2P.

Unfortunately #AsynchronousCommunication generally gets shafted in people's prioritization & considerations, so there's much less work done on those at the moment.

#DTN #StoreAndForward #DelayTolerance #DelayTolerantNetworking

@dalias @DanielMicay I think you're more arguing about data consumption than bandwidth per se.

The vast majority of synchronous networking protocols account in exactly no way for data limitations.

That type of adverse condition is largely ignored in the design of basically everything other than #DelayTolerant #networking where limitations in #StoreAndForward nodes' storage (which is actively involved and limits data) or data simply cannot be ignored.

#DTN #DTNs #AsynchronousCommunication