I do not like infinitely nested quote posts. I think one note depth down looks best with some sort of que that there are additional notes.
Discussion
Infinite nesting is what happens when devs build things that make sense to devs without talking to users or designers.
If what you are trying to do is keep a catalogue of related/themed notes: kind 1 is not the way. i argue for having "modular articles", but the concept could apply to themed groups of notes.
Nested notes kill the experience (and occassionally, the app), same thing with publishing a lot of notes in a short time to the user's feed, that are all related.
Solving it? We need two event kinds:
Kind 30040 - article header: this is what renders to the main feed of users on the typical clients. It displays the name of the article (or group name) and whatever other metadata about the text you care about. As a tag it contains a list of existing notes that make up the article of group, and these events could be any type of event that can be rendered.
For articles,
kind 30041 - article note: The content of the article as multiple notes representing sections of the article. These notes typically would only be rendered when the article header ia selected (kind of how notes that kind30023 (habla.news) renders a note when its clicked on.
make sense?
I can understand. I think many devs are running solo or have a few helpers. All of these things will get better with time, I'm positive.