mleku on Nostr: oh, yeah, now that's a separate thing... and it would require a separate kind, also ...
oh, yeah, now that's a separate thing... and it would require a separate kind, also would need to use those d tags and such and a tags to find them
the thing is that this obviates the replaceable thing
this is partly why i defined in the #realy protocol that instead of making kinds bound to replaceabliity, that this operation was part of the publish API, - either it's new (and can't replace), or it replaces - with the id specified, or it should not be stored - ephemeral, is all a separate version of the client-side EVENT envelope in nostr
you may run into trouble because you locked these events into the most permissive form of replaceable... i know that the spec has additional metadata , but actual replacement needs to be an intentional action
anyway lol i'm still stuck on this damn unbounded http upload problem, i just learned about a method on http.Request i didn't see anywhere in my searches that relates to faking the "close" of the stream
the thing is that this obviates the replaceable thing
this is partly why i defined in the #realy protocol that instead of making kinds bound to replaceabliity, that this operation was part of the publish API, - either it's new (and can't replace), or it replaces - with the id specified, or it should not be stored - ephemeral, is all a separate version of the client-side EVENT envelope in nostr
you may run into trouble because you locked these events into the most permissive form of replaceable... i know that the spec has additional metadata , but actual replacement needs to be an intentional action
anyway lol i'm still stuck on this damn unbounded http upload problem, i just learned about a method on http.Request i didn't see anywhere in my searches that relates to faking the "close" of the stream