Sure, in some cases! Though, the notorious flakey internet connection of phones adds complexity and difficulty. Local messaging use cases could also benefit from wireless connections (e.g., LoRa/Bluetooth/Wi-Fi). In other cases, relays with low latency and high availability would be useful to bolster reliability. For example, with redundant-powered SBC or VPS relay servers with multiple internet connections/transports.

A structured network strategy to sync Nostr relays I think can greatly help the persistance and reliability of messages. Negentropy is a huge help. For example, if all admins independently run relays and have write policies exclusive to members/admins, the relays can sync and secure only those messages between each other. Strfry has some support here with a router. However, last I remember, the features were new and could be optimized. I would need to look again.

The reliability of message delivery of commit messages is the main difficulty, even in the case of a single admin?

For example, if Alice creates a group, she can act as the admin without a need for consensus; coordinating messages can be distributed across several relays. No?

This post also observed that:

https://simonwillison.net/2026/Aug/16/qwen-38-27b/

Apparently, the default is `xhigh` and `reasoning_effort` can be changed to `medium` and `low`.

Has a single coordinating key been implemented already in Marmot? I'd imagine that this is desired in some use cases and serves as a good starting point.

It's astonishing that the Moon and Sun are nearly equal in relative size from the perspective on Earth.

End-to-end quality assurance testing using the Kolmogorov–Smirnov method, and not just for the TRNG chips, would enhance product reliability.