i see no reason why to pollute an event bus with such high bandwidth content, at all, at all

there is plenty of perfectly fine ways to do it, RTP, webRTC, even bittorrent can be rigged up to do this, and it's not hard to integrate such services into a relay codebase or even simply interface them with a cluster protocol

as far as i'm concerned, events should not even make it to 64kb in size, such large objects tend to be slowly mutating, if at all, and a collaborative event stream can be separately made concrete given a strong guarantee about completeness of the events that composed into it

this is not a good enough reason to do it... at best, adding ZSTD compression to larger binary data would be a good move, compress teh data before the encryption, in the case of encrypted data, and you solve most of the size problems there

don't make the beginner mistake of letting domains between systems leak into each other, it can cause immense problems

just like bitcoin should be primarily an accounting system and not a payment system, nostr should be an event network and not a streaming media network