David @mleku - 9mo
well, just a thought... aggregating things into groups is a general purpose that cuts across many use cases
Silberengel @Laeserin - 9mo
Yeah, that's why we didn't limit 30040s to 30041s. You could aggregate any event kind and use any tags, so long as you have the mandatory ones. If your 30040 doesn't include any other 30040s, then it's an ordered list of whatever events. If it does, then it's a nested hierarchy of indexes, like for a ToC. ``` Kind 30040 MUST have events listed in e tags in the order that they appear in the article. The events may be any already-existing event (including nested kind 30040s). ```
eBooks are just our first use case because we want to start off with the Bible, but obviously, I can think of a gazillion different types of collections. A photo collage, or a playlist, or an audiobook, a "best of" grouping of someone's long-form articles, related wiki pages, or etc.
yeah, arbitrary binary blob segments is an interesting one too i'm not a big fan of the idea of serving data as events per se but they are ok as segmented blobs i think, they can even be additionally blockcahined so the entire set can't be tampered with
Easy way to get people to store kiddy porn and stuff on your relays tho, isn't it?
