funny enough, the idea of adding a batch save event function to the realy eventstore interface was something i have thought about repeatedly when implementing import
i already have an import function that you pump with a .jsonl (line structured JSON) file, like the kind that many clients have for import or exporting events, but because of thet need for auth it currently is only exposed on localhost by default
i didn't know there was a batch event message type in the protocol... no, there isn't
if auth is required or not makes no material difference, the client can simply stream them out, the "ok" replies don't have to be received before another can be pushed, it would just be used by the client to know if an event failed to be saved by the relay for some reason... there also may be rate limiting issues in this, that may or may not be documented in the nip-11
if you control the relay, and it has an admin http listener like #realy does, you can just dump the events up to it that way, it has no rate limiting and doesn't require to receive acks at all, but it also doesn't tell you on the wire whether the events were accepted
there could be a bundling extension on the EVENT message type that lets you string multiple event objects comma separated in one go, or you can just write an uploader that works with the normal event/ok cycle to make sure it all goes up, it may be a little slower but probably won't be a big deal most of the time, i mean, 2 minutes versus 10 minutes is not gonna kill you probably, especially considering you can parallelise these uploads or do something else in the meantime
Tester: The thingy doesn't do the thing. Well, it does the thing, but like weirdly. Or something. Dunno.
Dev: Hmm... Did you remember to do the thing to the other thing, first?
Tester: Yup.
Dev: Hmmm... Yo, OtherDev, the thingy doesn't do the thing, even though she did the thing to the other thingy.
OtherDev: Works on my machine.
Tester: 🥺 Pwease check thingy.
OtherDev: *groans* * rolls eyes* Oh, okay... just this once... Hmm. You're right. Doesn't do the thing. That's odd. Hmmm. 🤔
Dev: Yeah, see, I was thinking we could do the watchmakalit to the thingamabobber with the whatnot and the doodad.
OtherDev: Whoa. Don't know if I'd go full doodad. A bit of dolittle would probably be enough. Never go full doodad.
Dev: Well, you little #sissydev, you have to consider the underlying effect on the jakamobile and the etceteraster...
Tester: *groks nothing* *slinks out*
Showing page 1 of
2 pages
