melvincarvalho on Nostr: This use case was always possible, and has already been standardized at the ietf in ...
This use case was always possible, and has already been standardized at the ietf in RFC 6920 for a decade. Blossom doesnt really standarize it, imho. It proposes an api which pollutes the namespace, and wont fly in certain deployment scenarios. But it is a system that works, and could perhaps be future-proofed with the use of reverse proxies. I wouldnt get too wedded to the system tho. There is sufficient technical debt that further iterations will be needed, imho.
Published at
2024-07-23 09:24:03Event JSON
{
"id": "e804044b9134f15f8596f4904010327f6d5463c151701897d5f8921f00121fe7",
"pubkey": "de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645",
"created_at": 1721726643,
"kind": 1,
"tags": [
[
"e",
"287d7cda2468ff63b730e9f412b56d3952be6cba9102ac6c5b5c531c5660c54a",
"wss://relay.primal.net",
"root"
],
[
"e",
"0bc1bc198fef6d1b3a2fc74648965dc99a9d6961d7556986388040880849b0a1",
"wss://relay.primal.net",
"reply"
],
[
"p",
"de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645"
],
[
"p",
"8f44c56131b362668b0e01be8c71b24786598bb68fb909cfd78fabfb058dd0f0"
]
],
"content": "This use case was always possible, and has already been standardized at the ietf in RFC 6920 for a decade. Blossom doesnt really standarize it, imho. It proposes an api which pollutes the namespace, and wont fly in certain deployment scenarios. But it is a system that works, and could perhaps be future-proofed with the use of reverse proxies. I wouldnt get too wedded to the system tho. There is sufficient technical debt that further iterations will be needed, imho.",
"sig": "fd4ec0be6f1507d99d994404e7e2a025db4513b955f26756dca5bf681a58f6858887465b3ed519d1657724d21cd6e5fda79414d026549a3edc371767cd5a296c"
}
