Following up with this talk, since an event is immutable. It makes no sense to have a stream of immutable data of 1 item.
put in programming term:
get(event_id) -> stream
get(event_id) -> event | nothing makes sense
Then, we should just have
http get/post for read/write a single event.
Web Socket everything is overrated.
The only use case that might justify stream of 1 event is that at the moment of querying, the event is not in the relay, but in the future the event might be published to this relay by other clients or relays.
But, in order for a user to even know the ID of an event, the event has to exist in some relay before the time of sharing.
http get(nevent) always makes more sense.