David @mleku - 6mo
funny side note, when i saw that word kanban just now i thought "kankan" anyway, yeah, so, i guess the point is this: the structuring parts of the data are a unit, even if they are a set of layered events (eg book, chapter, verse) in effect there is no actual sense in NOT combining them into a single event structure, because they have to be changed all at once anyway, atomically if i may suggest, to simplify the atomic unit of a book, just make the entire structure spec into a single event, since it's gonna be a LOT more work for a relay to handle the vomit of new events that are required to update or add a new version i would also question whether to make them replaceable, perhaps if the version code was the parameter then ok, and you did make them 30k numbers so that all fits, this lets you do both, so you can update a branch independently of another, but then you might need to have human readable identifiers associated with the versions, as well as displaying who made the update on the version
Silberengel @Laeserin - 6mo
You often only have to change one event, with the version, though. They aren't linked lists, or anything, and they're replaceable. If you put the entire structure into one event (which might be simpler, yes), then you can't have fine-grained content or large structures. The Bible has over 30k versus, for example. You'd have to list them all within one event.
People kept wondering why it was taking us so long and it's like... Yo, this is a math 🧩. This is not tweets. Nobody has ever done something like this, before, which is why we're going to write up a scientific paper about it. We're inventing the structure, as we go along. We're still discussing the architecture and it may change some more 🙈, but we decided to just go for it, anyway.
I think that's something for the relay to handle. Trying to stuff it into events is inefficient.
We're the first team to have an actual use case that _needs_ Nostr. That's why this isn't just a clone of something in existence. This couldn't exist before Nostr. #GitRepublic will also be a doozy, but we have to get Aedile to at least v0.2.0 before we can design that.
