Without us purposely doing this, we have effectively created 3 different blog templates all relying on the curation protocol over the past 6 months: Neosound (music/audio focused), Mint house (generic drop focused), & River (written/video editorial focused)
Figuring out a way to tie the development of all of these product primatives together will let us move towards a much more shared working environment towards each product direction, while still allowing for individuals/teams to work on the specific surface area that is most interesting to them.
I’ve put together a figma that illustrates how all of these platforms can actually be built around roughly the same infrastructure – with the one missing piece atm being a robust indexing solution that is equipped to handle this (zora indexer could work ~fine~ for this, but I believe a more dedicated solution such as Neume integration cc @djfnd might be needed to enable enhanced discovery across all of these as well)
an additional rlly cool thing about all of this, is that the curation protocol is just one example of a shared data standard to build apps around. see the screenshot below for what the data of a curation receipt token looks like
I’m very interested in contributing to this effort on both the Neume and PA side.
I think Neume could become an ideal source of data for curation by expanding it’s scope to index all the things. On top of this, curators provide a valuable service by separating the signal from the noise, something that is hard for an indexer to do while remaining neutral. Neume could then index the curators, exposing that signal as an input for further curation or UIs for discovery and consumption.
wanted to bump these three articles about online identity, digital spaces, + platform design for us all to keep in mind as we build this stuff out
there is so much design space to work with here, and so many historical patterns to dive deeper into / try to pull out of. one of the more interesting questions is “persona or subject driven profiles” ?