I finally got reactions and reposts (NIPs 25 and 18) implemented in the Pretty Good Apps desktop client.

Next up: zaps. Probably create another release at that point.

Then back to work on a basic lists (NIP-51) implementation, which is partially working. (Took a break from that this weekend to work on reactions and reposts).

Roadmap after that, in broad brushstrokes: try to expand the use-cases for NIP-51 lists, probably ones that involve "composite" lists via importation of one list into another. (Composite mute lists? composite people lists, for use in nostr feeds? composite bookmarks lists?)

Then add more list management features (beyond NIP-51; maybe mix in some NIP-32, maybe add some nonstandard protocols if I have to) until we arrive at DCoSL: decentralized curation of simple lists. Then build on list curation to achieve DCoG: decentralized curation of graphs, which we can do bc a graph is made of two lists: one list for nodes and one list for edges. Then build on that to achieve DCoS: decentralized curation of standards, which we'll be able to do because things like schemas, verified credentials, etc can be represented as graphs. Then pick one or a handful of w3c standards and see if it is possible manage them using these tools rather than the committees that are today's standard.

That still won't get us all the way to the self-sustaining, atomic chain reaction of the decentralized web that I mentioned in a note yesterday. But it will get us a good bit of the way there. DCoP and/or DCoR: decentralized curation of protocols and/or of repositories will have to be conceptualized and achieved at the same time or maybe after DCoS. Then DCoS, DCoP, and/or DCoR can be used to manage the NIPs and other protocols that got us to this point in the first place. At that point, we can start to think about feedback loops: self-sustaining chain reactions of decentralized curation of data in all its forms.