Still on vaca but sharing a realization I just had about AssemblyPress and the Curation Protocol that I sent in the zora slack. tldr adds a bit more work to getting these finalized, but then the structure will be in place for limitless exploration (depending on how many contributors PA can activate)
Here are links if you want to get familiar with the most up to date versions (both are drafts) of AP + Curation Protocol code bases in the meantime
We like epiphanies.
When you’re back from vacay… could you say a bit more about what moving the curation protocol onto the AP framework looks like in practice? E.g. is there a particular component of the curation protocol that would be replaced by AP?
pretty much we needa move all the logic from Curator.sol (and associated helper files) into a separate “CurationLogic.sol” file (similar to DefaultLogic.sol), and then well have a first class support for creating Press’s using a ~curation contract strategy~ in PressFactory.sol
ERC721Press.sol proxies are initialized with an external logic file + renderer file, which lets us set up basically any strategy we want, as long as it fits this interface
Nice… tysm for the high-level explanation and links. I skimmed the code and am def excited to see how this shakes out.
I did not realize the press factory would be so generic. It will be cool to try it out with some custom logic of my own 
new understanding of AssemblyPress is that it should be the best framework for turning any data structure + access control logic into an ERC721
extremely generic…with opionated use cases (protocol → platform) developed by PA to showcase the power of the model
^with a little bit of creativity, we should be able to monetize this at the platform level for PA as well
