David. I think you’re onto something really big here… but the iceberg goes deep. 

- The use case for “auto generated lists” (as we are imagining) is novel to Nostr. It’s not exactly “covered” by design in the NIP51 spec nor accounted for by any client developer. 
- and even as they are, lists are not really used by clients in ways that they could or should be. 
- these two facts go hand in hand … because lists are assumed to be “made by hand” then clients don’t implement them as data stores for various needs, because that would too much to ask of end users. 
- so there’s a paradigm shift we’re up against which will be more work to change than just designing a “d tag standard”.

But also… that’s a good idea. 👍🏼