mleku on Nostr: i can imagine an uploader that swallows EPUB3 documents and cuts them up on the fly ...
i can imagine an uploader that swallows EPUB3 documents and cuts them up on the fly into segmented, annotated events complete with all the metadata events in between grouping it though
one thing that you could run into as a problem is if your text-to-event functions are using non- nip-1 compliant escaping, realy will not save the events, but using the realy libraries would solve that issue, the escape/quote functions in there always get it right - the issue is that generic JSON codecs some of them use all kinds of other escaping for special characters and UTF-8 and nip-01 basically just uses the short single letter ones for sub-32 control characters and everything else is blanket tolerated, some older JSON implementations don't play nice with UTF-8 extended 4 byte characters because they are using nonprintables and such
one thing that you could run into as a problem is if your text-to-event functions are using non- nip-1 compliant escaping, realy will not save the events, but using the realy libraries would solve that issue, the escape/quote functions in there always get it right - the issue is that generic JSON codecs some of them use all kinds of other escaping for special characters and UTF-8 and nip-01 basically just uses the short single letter ones for sub-32 control characters and everything else is blanket tolerated, some older JSON implementations don't play nice with UTF-8 extended 4 byte characters because they are using nonprintables and such