From bac0113096779bfd6263a43cff5ec4a4d2a4f45a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alic=CE=9E?= <158374539+punkess@users.noreply.github.com> Date: Sat, 17 Feb 2024 13:56:30 +0100 Subject: [PATCH 1/5] Create lip-10.md wip v0.01 --- LIPs/lip-10.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 LIPs/lip-10.md diff --git a/LIPs/lip-10.md b/LIPs/lip-10.md new file mode 100644 index 0000000..88b75c7 --- /dev/null +++ b/LIPs/lip-10.md @@ -0,0 +1,22 @@ +#LIP-10 “3 birds with one LIP” - bring LIPs back to @lens/lens x enable full content search x strategic app grants / development initiatives. + +“As Lens Protocol is a neutral and flexible technology stack for social networking use-cases, LIPs provides the basis to ensure that Lens Protocol remains flexible and uniform across all potential use-cases, improvements and ideas within the community.” … and therefore the home for LIPs should be @lens/lens. +advantages: +(1) accessibility: literally every lens user can join discussions and add ideas without any barrier of entry. (Status quo: setup of a GitHub + profile, getting used to the app and the (technical) workflow coming with the process currently implemented). +(2) visibility: based on the amount of comments and the profiles participating in the discussions so far, LIPs will get an amazing visibility in the broader lens community. + +Disadvantages: LIPs won’t be easily accessible as soon as they are in the lower end of the feed. -> workaround: use of the #LIP hashtag eg #LIP-10. solution(s): +#LIP-10b1 full content search. +#LIP-10b2 grant for a lens based developer platform. + +#LIP-10b1 #hashtags and profiles are the only elements searchable on lens at the moment. Trying to find content (posts and especially comments) again is a very time consuming and challenging endeavour. +The goal of this #LIP is to enable full content search on lens (via the lens API). + +Lens Ecosystem (Standard) +#LIP-10b2 hackathons are great but have you ever tried incentivising the development of “strategic apps”? +I don’t think that “web2 but decentralised” is a (user) winning approach. In this specific case the combination of a developer platform app with a decentralised general purpose social graph AND leveraging the “internet of value” - rewarding devs building open source code (project X uses code from dev Y and compensates dev Y if project X succeeds) sounds interesting (imo). +Independent of this specific case, having a lens fund supporting and incentivising projects being built on lens might be worth trying. + + + From 3b7ab61be00210baf7351597bb2fb89e85f64d7c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alic=CE=9E?= <158374539+punkess@users.noreply.github.com> Date: Fri, 8 Mar 2024 10:48:55 +0100 Subject: [PATCH 2/5] Create lip-42.md --- LIPs/lip-42.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 LIPs/lip-42.md diff --git a/LIPs/lip-42.md b/LIPs/lip-42.md new file mode 100644 index 0000000..af8efd4 --- /dev/null +++ b/LIPs/lip-42.md @@ -0,0 +1,5 @@ +# make lens collects great +goal of this LIP is to enable creators to create posts on lens that result in NFTs appealing to secondary market customers. (= look (headline, description) and feel (attributes) must be comparable to state of the art media NFTs available on OpenSea e.g.) +Nice to have: enable collections on lens. + + From aba92538e0805de0665dbf5017839cf2696266e6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alic=CE=9E?= <158374539+punkess@users.noreply.github.com> Date: Fri, 8 Mar 2024 11:06:59 +0100 Subject: [PATCH 3/5] Update lip-42.md LIP-42 --- LIPs/lip-42.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/LIPs/lip-42.md b/LIPs/lip-42.md index af8efd4..170c3f5 100644 --- a/LIPs/lip-42.md +++ b/LIPs/lip-42.md @@ -2,4 +2,19 @@ goal of this LIP is to enable creators to create posts on lens that result in NFTs appealing to secondary market customers. (= look (headline, description) and feel (attributes) must be comparable to state of the art media NFTs available on OpenSea e.g.) Nice to have: enable collections on lens. +##motivation +thanks to $BONSAI and lens going permissionless, paid collects get some attention (again). Creators start minting on lens (again) and #lensfrens collect (with $BONSAI). Thats great and an important first step. The next step to keep the momentum is a thriving secondary market for lens collects. Imo state of the art NFT meta data is prerequisite to "make it" on market places. +## status quo +Collect: https://hey.xyz/posts/0x018ec4-0x0194 +OpenSea: https://opensea.io/assets/matic/0x5d891e31b19285336cf6ba9d7643935bb1f3ee8a/1 + +## goal +https://opensea.io/assets/ethereum/0x524cab2ec69124574082676e6f654a18df49a048/11671 + +We saw the discussion around collects, meta data and market places over and over again on lens. @lens/chaoticmonk , @lens/carstenpoetter , @lens/ryanfox and many more posted frequently regarding the importance of this topic. + +I'm neither from an technical nor from an artist/creator side knowledgable enough to push this any further. BUT I'm convinced that it's an important topic and this LIP should bring all the relevant people together - from a tech and creator side - to find an amazing solution. + +(LIP 42a: we need full content search on @lens/lens !) +(LIP 42b: let's bring LIPs on @lens/lens !) From 8804608590d9207243a477c83f8770775fbf55e0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alic=CE=9E?= <158374539+punkess@users.noreply.github.com> Date: Fri, 8 Mar 2024 11:25:35 +0100 Subject: [PATCH 4/5] Update and rename lip-42.md to lip-17.md LIP 17 --- LIPs/lip-17.md | 34 ++++++++++++++++++++++++++++++++++ LIPs/lip-42.md | 20 -------------------- 2 files changed, 34 insertions(+), 20 deletions(-) create mode 100644 LIPs/lip-17.md delete mode 100644 LIPs/lip-42.md diff --git a/LIPs/lip-17.md b/LIPs/lip-17.md new file mode 100644 index 0000000..a1fe80d --- /dev/null +++ b/LIPs/lip-17.md @@ -0,0 +1,34 @@ +* title: make lens collects great +* description: enable creators to create posts on lens that result in NFTs appealing to secondary market place customers. +* author: @lens/punkess (inspired by @lens/carstenpoetter @lens/chaoticmonk @lens/ryanfox ) +* status: Draft +* type: Protocol +* created: 2024-03-08 + +# [LIP-17] make lens collects great +The goal of this LIP is to enable creators to create posts on lens that result in NFTs appealing to secondary market customers. + +(= look (headline, description) and feel (attributes) must be comparable to state of the art media NFTs available on OpenSea e.g.) + +**Nice to have**: enable collections on lens. + +## motivation +Thanks to $BONSAI and lens going permissionless, paid collects get some attention (again). Creators start minting on lens (again) and #lensfrens collect (with $BONSAI). Thats great and an important first step. The next step to keep the momentum is a thriving secondary market for lens collects. Imo state of the art NFT meta data is prerequisite to "make it" on market places. + +### example +Lens collect: https://hey.xyz/posts/0x018ec4-0x0194 + +* status quo: https://opensea.io/assets/matic/0x5d891e31b19285336cf6ba9d7643935bb1f3ee8a/1 +* goal: https://opensea.io/assets/ethereum/0x524cab2ec69124574082676e6f654a18df49a048/11671 + +We saw the discussion around collects, meta data and market places over and over again on lens. @lens/chaoticmonk , @lens/carstenpoetter , @lens/ryanfox and many more posted frequently regarding the importance of this topic. + +## next steps +This LIP should bring all relevant people and ideas together - from a tech and creator side - to find an amazing solution shaping the future of NFTs on lens. + + +* (LIP 17a: we need full content search on @lens/lens !) +* (LIP 17b: let's move LIPs to @lens/lens !) + +## Copyright +Copyright and related rights waived via CC0. diff --git a/LIPs/lip-42.md b/LIPs/lip-42.md deleted file mode 100644 index 170c3f5..0000000 --- a/LIPs/lip-42.md +++ /dev/null @@ -1,20 +0,0 @@ -# make lens collects great -goal of this LIP is to enable creators to create posts on lens that result in NFTs appealing to secondary market customers. (= look (headline, description) and feel (attributes) must be comparable to state of the art media NFTs available on OpenSea e.g.) -Nice to have: enable collections on lens. - -##motivation -thanks to $BONSAI and lens going permissionless, paid collects get some attention (again). Creators start minting on lens (again) and #lensfrens collect (with $BONSAI). Thats great and an important first step. The next step to keep the momentum is a thriving secondary market for lens collects. Imo state of the art NFT meta data is prerequisite to "make it" on market places. - -## status quo -Collect: https://hey.xyz/posts/0x018ec4-0x0194 -OpenSea: https://opensea.io/assets/matic/0x5d891e31b19285336cf6ba9d7643935bb1f3ee8a/1 - -## goal -https://opensea.io/assets/ethereum/0x524cab2ec69124574082676e6f654a18df49a048/11671 - -We saw the discussion around collects, meta data and market places over and over again on lens. @lens/chaoticmonk , @lens/carstenpoetter , @lens/ryanfox and many more posted frequently regarding the importance of this topic. - -I'm neither from an technical nor from an artist/creator side knowledgable enough to push this any further. BUT I'm convinced that it's an important topic and this LIP should bring all the relevant people together - from a tech and creator side - to find an amazing solution. - -(LIP 42a: we need full content search on @lens/lens !) -(LIP 42b: let's bring LIPs on @lens/lens !) From c371327c35715b553005d07a3c19c7e310a02ec5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alic=CE=9E?= <158374539+punkess@users.noreply.github.com> Date: Fri, 8 Mar 2024 11:33:43 +0100 Subject: [PATCH 5/5] Delete LIPs/lip-10.md --- LIPs/lip-10.md | 22 ---------------------- 1 file changed, 22 deletions(-) delete mode 100644 LIPs/lip-10.md diff --git a/LIPs/lip-10.md b/LIPs/lip-10.md deleted file mode 100644 index 88b75c7..0000000 --- a/LIPs/lip-10.md +++ /dev/null @@ -1,22 +0,0 @@ -#LIP-10 “3 birds with one LIP” - bring LIPs back to @lens/lens x enable full content search x strategic app grants / development initiatives. - -“As Lens Protocol is a neutral and flexible technology stack for social networking use-cases, LIPs provides the basis to ensure that Lens Protocol remains flexible and uniform across all potential use-cases, improvements and ideas within the community.” … and therefore the home for LIPs should be @lens/lens. -advantages: -(1) accessibility: literally every lens user can join discussions and add ideas without any barrier of entry. (Status quo: setup of a GitHub - profile, getting used to the app and the (technical) workflow coming with the process currently implemented). -(2) visibility: based on the amount of comments and the profiles participating in the discussions so far, LIPs will get an amazing visibility in the broader lens community. - -Disadvantages: LIPs won’t be easily accessible as soon as they are in the lower end of the feed. -> workaround: use of the #LIP hashtag eg #LIP-10. solution(s): -#LIP-10b1 full content search. -#LIP-10b2 grant for a lens based developer platform. - -#LIP-10b1 #hashtags and profiles are the only elements searchable on lens at the moment. Trying to find content (posts and especially comments) again is a very time consuming and challenging endeavour. -The goal of this #LIP is to enable full content search on lens (via the lens API). - -Lens Ecosystem (Standard) -#LIP-10b2 hackathons are great but have you ever tried incentivising the development of “strategic apps”? -I don’t think that “web2 but decentralised” is a (user) winning approach. In this specific case the combination of a developer platform app with a decentralised general purpose social graph AND leveraging the “internet of value” - rewarding devs building open source code (project X uses code from dev Y and compensates dev Y if project X succeeds) sounds interesting (imo). -Independent of this specific case, having a lens fund supporting and incentivising projects being built on lens might be worth trying. - - -