42N3 on Nostr: Why? It is the same stream. Temporarily locking the stream across multiple operator ...
Why? It is the same stream. Temporarily locking the stream across multiple operator << invocations? A thing you do not want to have with any stream object.
If one needs it - e.g. logging from multiple application threads - one has to lock the stream for the next output anyway.
Published at
2025-03-10 09:24:22Event JSON
{
"id": "5e6821425a00b42cfff880232e41866bb0c55caaf3c05d797cb4c8322eb4ba04",
"pubkey": "cc33d9331c022da690a714db2cfb57c36a7a09dbbc8d512d1375483e0347fdcc",
"created_at": 1741598662,
"kind": 1,
"tags": [
[
"e",
"cf4499ba231cc5018885dff546300a07dad1219255faff6afab717bfda17308b",
"wss://relay.mostr.pub/",
"root",
"f173ca7ed8f3adf61d35abb4915401c1d01b59463e62ab7afdac428612559580"
],
[
"e",
"cf4499ba231cc5018885dff546300a07dad1219255faff6afab717bfda17308b",
"wss://relay.mostr.pub/",
"reply",
"f173ca7ed8f3adf61d35abb4915401c1d01b59463e62ab7afdac428612559580"
],
[
"p",
"f173ca7ed8f3adf61d35abb4915401c1d01b59463e62ab7afdac428612559580"
]
],
"content": "Why? It is the same stream. Temporarily locking the stream across multiple operator \u003c\u003c invocations? A thing you do not want to have with any stream object.\nIf one needs it - e.g. logging from multiple application threads - one has to lock the stream for the next output anyway.",
"sig": "3f458d0e510c26c73670d47f993915436c951b5c3f6f5c6d7970f16b04a81b821b3ad56c83018e22e53f857f735f54c9ffa55aa9319320f64cc9e5134950e554"
}
