Yes. Need to all be on the same implementation page.
Should we write a guide of how to implement the outbox ("gossip") model? Is that a good idea? What should that guide contain? nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
Discussion
no, the outbox model benefits from competing implementations because we haven't figure out the best approach yet
Then figure out the best approach and implement that way so that we don't have interoperability issues.
an implementation would need to be incredibly stupid for interoperability to become problematic; the outbox model doesn't really suffer from issues like event nomenclature or formatting or stuff like that where how one client behaves affects other clients
Bookmarking for future use in case someone does something dumb. 😂
