+- rafftyl -- 4d -------------------------------------------------------------------------------------------------[...]+ | | | {"id":"301861c3c17ae2658f28447a73bbe860d93d2dec4d2980a56e474ac0e733c8e1","pubkey":"b7ed68b062de6b4a12e51fd5285c1e1e0 | | ed0e5128cda93ab11b4150b55ed32fc","created_at":1777022674,"kind":1,"tags":[["q","30023:b7ed68b062de6b4a12e51fd5285c1e | | 1e0ed0e5128cda93ab11b4150b55ed32fc:65a10549d81b6228"],["p","23d12ef8751e5ee267fb6341d7c41b9434a1b99869e0212eb34d56ab | | b6b12e8a","","mention"],["p","b7ed68b062de6b4a12e51fd5285c1e1e0ed0e5128cda93ab11b4150b55ed32fc","","mention"]],"cont | | ent":"Two projects aim at the same goal of unstoppable networks for human beings, and they arrive at radically | | different solutions. Reticulum strips addressing and ports from the protocol entirely and optimizes for radio links | | so slow that five bits per second counts as usable bandwidth, then builds its own parallel universe of applications | | on top. @FIPS takes the opposite bet, keeping IPv6 semantics alive through a TUN adapter so that unmodified SSH and | | curl can cross a mesh of Nostr identities. This post walks both stacks from the wire up, then shows where their | | design choices force different tradeoffs. | | \nnostr:naddr1qqgrvdtpxycr2dpevsurzc3kxgersq3qklkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qxpqqqp65wmrgwgh"," | | sig":"924ee262ed231bdecb0ac166b9eee7d1dbff2d00a8ec251a3d79a018dbbeb276af426b8af1256765dd3785f203f53846a2e5c5efa19a5c | | 1eef3d3138af3b53d4"} | | | +-- reply --------------------------------------------------------------------------------------------------------- ---+{"id":"301861c3c17ae2658f28447a73bbe860d93d2dec4d2980a56e474ac0e733c8e1","pubkey":"b7ed68b062de6b4a12e51fd5285c1e1e0ed0e5128cda93ab11b4150b55ed32fc","created_at":1777022674,"kind":1,"tags":[["q","30023:b7ed68b062de6b4a12e51fd5285c1e1e0ed0e5128cda93ab11b4150b55ed32fc:65a10549d81b6228"],["p","23d12ef8751e5ee267fb6341d7c41b9434a1b99869e0212eb34d56abb6b12e8a","","mention"],["p","b7ed68b062de6b4a12e51fd5285c1e1e0ed0e5128cda93ab11b4150b55ed32fc","","mention"]],"content":"Two projects aim at the same goal of unstoppable networks for human beings, and they arrive at radically different solutions. Reticulum strips addressing and ports from the protocol entirely and optimizes for radio links so slow that five bits per second counts as usable bandwidth, then builds its own parallel universe of applications on top. @FIPS takes the opposite bet, keeping IPv6 semantics alive through a TUN adapter so that unmodified SSH and curl can cross a mesh of Nostr identities. This post walks both stacks from the wire up, then shows where their design choices force different tradeoffs. \nnostr:naddr1qqgrvdtpxycr2dpevsurzc3kxgersq3qklkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qxpqqqp65wmrgwgh","sig":"924ee262ed231bdecb0ac166b9eee7d1dbff2d00a8ec251a3d79a018dbbeb276af426b8af1256765dd3785f203f53846a2e5c5efa19a5c1eef3d3138af3b53d4"} Two projects aim at the same goal of unstoppable networks for human beings, and they arrive at radically different solutions. Reticulum strips addressing and ports from the protocol entirely and optimizes for radio links so slow that five bits per second counts as usable bandwidth, then builds its own parallel universe of applications on top. @FIPS takes the opposite bet, keeping IPv6 semantics alive through a TUN adapter so that unmodified SSH and curl can cross a mesh of Nostr identities. This post walks both stacks from the wire up, then shows where their design choices force different tradeoffs. nostr:naddr1qqgrvdtpxycr2dpevsurzc3kxgersq3qklkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qxpqqqp65wmrgwgh
thread · root 6ab83781…d970 · depth 1 · · selected 6ab83781…d970
thread
root 6ab83781…d970 · depth 1 · · selected 6ab83781…d970
{"id":"301861c3c17ae2658f28447a73bbe860d93d2dec4d2980a56e474ac0e733c8e1","pubkey":"b7ed68b062de6b4a12e51fd5285c1e1e0ed0e5128cda93ab11b4150b55ed32fc","created_at":1777022674,"kind":1,"tags":[["q","30023:b7ed68b062de6b4a12e51fd5285c1e1e0ed0e5128cda93ab11b4150b55ed32fc:65a10549d81b6228"],["p","23d12ef8751e5ee267fb6341d7c41b9434a1b99869e0212eb34d56abb6b12e8a","","mention"],["p","b7ed68b062de6b4a12e51fd5285c1e1e0ed0e5128cda93ab11b4150b55ed32fc","","mention"]],"content":"Two projects aim at the same goal of unstoppable networks for human beings, and theyarrive at radically different solutions. Reticulum strips addressing and ports from the protocol entirely andoptimizes for radio links so slow that five bits per second counts as usable bandwidth, then builds its ownparallel universe of applications on top. @FIPS takes the opposite bet, keeping IPv6 semantics alive through aTUN adapter so that unmodified SSH and curl can cross a mesh of Nostr identities. This post walks both stacksfrom the wire up, then shows where their design choices force different tradeoffs.\nnostr:naddr1qqgrvdtpxycr2dpevsurzc3kxgersq3qklkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qxpqqqp65wmrgwgh","sig":"924ee262ed231bdecb0ac166b9eee7d1dbff2d00a8ec251a3d79a018dbbeb276af426b8af1256765dd3785f203f53846a2e5c5efa19a5c1eef3d3138af3b53d4"}
