2025-12-31T10:32:22Z https://yabu.me Kurt https://yabu.me/npub16tcglj962wpz7sefdjgr3y6aquf3pggvvkzgyp8x3gfd95tm09tqx0hu0q https://cdn.masto.host/autonomouszone/accounts/avatars/111/811/960/690/091/837/original/f69eca80ac6cc67d.png https://cdn.masto.host/autonomouszone/accounts/avatars/111/811/960/690/091/837/original/f69eca80ac6cc67d.png https://yabu.me/nevent1qqs8p8jc3psj3duwhl7ed3lqzjgx374m2fe3d27kcymqgk3y9q9eckczyrf0pr7ghffcyt6r99kfqwynt5r3xy9pp3jcfqsyu69p95k30du4vcc7324 In reply to <a href='/nevent1qqsfrezckszrnagqv3j06s62xezzy4hlgkq2zeel5mc0g2nnuf6yzncrp3n8c'>nevent1q…3n8c</a><br/>_________________________<br/><br/>Given that communication channel capacity is the most constrained resource in most Meshtastic deployments, I wonder whether the traditional BBS paradigm, i.e., mostly stateless on the client side, is ideal. Menu systems, when navigated using a stateless client, involve a fair bit of back and forth over the channel. A system where clients hold state is way more complicated but opens up many possibilities. Here&#39;s someone dreaming along those lines: <a href="https://thomask.sdf.org/blog/2022/01/01/in-search-of-a-modern-packet-radio-bulletin-board.html">https://thomask.sdf.org/blog/2022/01/01/in-search-of-a-modern-packet-radio-bulletin-board.html</a> 2024-12-17T06:27:43Z