tldr me and @junghwan started work on a curation management tool to support all the efforts on our Blog Era – and it quickly turned into what I think can be PA’s blog aggregator that can support + provide discovery for all of the mint houses, personal websites, neosound forks, etc that are coming
recorded a loom describing whats going on, see below for other relevant links
would be dope to drop consistent educational videos natively, a lot of web3 education is mostly done natively, and most times that audience large, which eventually would lead to on-chain education content
@valcoholics gonna work tomorrow to get this UI looking way better, and then will turn back to Assembly Press to get the rfc i started wrapped up and deployed !!
Speaking to Christina at Lens earlier today, she mentioned that curation is a big target for them. I mentioned the work that PA is doing and she was very interested about how there may be shared space, “We want more of this and need more tools built on Lens that can curate our content…Do you think we could have Public Assembly index lens content and curate UGC music?”
does media on Lens follow typical contract address + tokenId patterns ? if yes then yes we technically would be able to with our curation protocol since there’s a field for chainID as well, but if they have some non contract/tokenId heuristic for addressing media objects (which I feel like I’ve seen they do?) then it might not be compatible
Yes, exactly. There are complications w.r.t this - from what I understand, rather than a tokenID there is a “pubID”. We are going through this process with neume now though to integrate Lens drops, so maybe some learnings could be applied across.
ok cool. do u happen to know what solidity type pubID is? could perhaps use the existing tokenId field in the Listing struct as a workaround to incorporate Lens stuff
