To wrap it up, 90% of degens voted that Lens needs a very specifically tailored version of bird app Community Notes (lenster.xyz/posts/0xe30c-0x9e-DA-6e929bf4). We probably do not need it now, as there's not much to review yet, but when Lens starts blowing up exponentially, it would be handy to have something ready.
Now, here's the next important part and another poll (please vote only after reading the full text) 👇.
Community Notes, even when centralized, are quite complex. To make it decentralized and verifiable is even harder. How can Lens Notes come to life, practically?
🖐️Lens team makes it as a native asset:
➕ Available for everybody
➕ Universal usage policy
➕ Native support
➖ Removes resources from elsewhere
➖ Priority is unclear
➖ May come much later than expected/needed
🖐️Some Lens app makes it for themselves and (maybe) opens it up for others too:
➕ We still get Lens Notes
➖ Murky control dynamics, even if open-sourced. Can work only if handled carefully, but can go wrong in many ways.
➖ Big stress on a single team with much less resources than the protocol itself.
➖ Will never be the team's primary focus, hence possible quality and support issues down the road.
🖐️It is created and maintained by the independent NotesDAO, which is supported by a consortium of Lens protocol itself, other ecosystem apps and (hopefully) wider community:
➕ Burden is shared
➕ Available for everybody
➕ Universal usage policy
➕ Team with primary focus
➕ Maximum neutrality
For me, the NotesDAO wins both worlds. It maximizes neutrality, availability, focus and probably speed to market as well, while making the burden of this public good shared.
Let’s have another temperature check. Please vote on the poll below. This time, be sure to tag the sh*t out of @stani @wagmi @nicolo @christina @nader and other usual suspects 🙂. It is still not clear if any of them even saw the previous poll. Let’s make sure they see this one 🙂.
Given all the above, how would you prefer Lens Community Notes to be developed and maintained?