Grain ques requests, ad maybe events but I have to check. Either way, rate limits and size limits may come into effect. I'll make sure grain handles events in ques but you may have to run your own to get around rate and size limit. But I'll certainly host the bible if you contact me beforehand and turn off the limits while you do it.
nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku nostr:npub1zmc6qyqdfnllhnzzxr5wpepfpnzcf8q6m3jdveflmgruqvd3qa9sjv7f60
It just occured to me that we need to maybe make sure relays can handle lots of people uploading publications as big sets of events, as per the draft NIP-62. Might be thousands or tens of thousands of events, per book, if it's something like a Bible, technical guide, or dictionary. Complete works of William Shakespeare. 😬
Is there some way to batch-process this, or que it, or something?
Discussion
We want to host our own. I think they were eying grain more for the vector embeddings stuff, but was curious how all of the relays handle this, as it'll be a more common use case.
I think we're starting to see more relay specialization, which is interesting.
Multiple grain instances for different purposes is probably a lot better than a big relay to do it all. The configurability is what makes it all possible.