818eth (@818eth) • Hey
818eth
Publications
- Hi, frens on Lens,
t2.world⏳ in the house!
We are building a transparent, decentralized and collaborative social network around reading and writing.
More exciting news to come, follow us to stay updated!
#genesispost #writing #creators #reading
- # 0.1.0 - 23rd December 2022\n\nThe Lens Core Team is excited to announce the first Developer Preview release of the official Lens SDK.\n\nThe Lens SDK will greatly improve the developer experience of building with the Lens API. It allows you to integrate with the Lens Protocol in seconds and gives you full control over the UX of your app.\n\nThis is just the beginning for the Lens SDK. We are starting with a collection of React Hooks and will add a low-level API Client for more advanced integrations, beyond React.\n\nTry out the Developer Preview release and tell us what you think!
https://github.com/lens-protocol/lens-sdk\n\nIn this release:
\n- feat: authentication w/ transparent token renewal\n- feat: React Hooks to:\n - fetch publications\n - fetch profiles\n - fetch followers/following\n - create post\n - fetch feed\n - notifications\n- feat: wagmi integration
\n\nSee the initial documentation at: https://docs.lens.xyz
- Here's everything you need to know about our 0.2.0 Lens SDK Update
https://github.com/lens-protocol/lens-sdk
- The Lens team continues to ship 🚢 hop aboard! 💨 0.3.0 💨
**Improvements in this release**
We added new hooks to enable some useful features for our community, some highlights below 👇
🪞Ability to Mirror a publication
👋Ability to report publication
⚡️Consolidated interface of several hooks for better consistency and ease of use
🫣Hide publications can now be enabled
👌More features to manage your profiles
🚀 Get Started https://docs.lens.xyz/docs/sdk-react-getting-started
🛠️ Get Technical here https://github.com/lens-protocol/lens-sdk
**What's New?**
- Added capability to filter by event type in useFeed hook.
- Added isValidHandle validation helper
- Added signless support to useUpdatedProfileImage hook
- Added useProfilesOwnedBy hook
- Added useReportPublication hook
- Added useWhoCollectedPublication hook
- Added useCreateMirror hook
- Added useActiveProfileSwitcher hook
- Added useProfilePublicationRevenue hook
- Added useUpdateDispatcherConfig hook
- Added useHidePublication hook
- Added useUpdateFollowPolicy hook
- Added useUpdateProfileImage hook
- Added useEnabledModules hook
- Consolidate useWalletLogin, useWalletLogout, and useActiveWallet interface
- Simplified async error handling
- Quick update for quicker load times. The Lens Protocol core team has rolled out some big improvements and now the Lens API notification server is 1000x faster 🤯
- **Improvements in this release**
We have added several new hooks in this release to help our community, highlights below 👇
📰 Ability to collect a publication
✅ Enabled approving modules (gas efficient with support for EIP-1559 gas estimation)
🪞 A new feature that allows you to see who mirrored a publication
💬 Expanded the filtering of feed, with explore publications and comments data
**What's new?**
Added **`useCollect`** hook enables the collection of publications
Added **`useApproveModule`** and internal toolings for EIP-1559 gas estimation Added **`useWhoMirroredPublication`** hook Added **`metadataFilter`** to **`useFeed`**, **`useExplorePublications`** and **`useComments`** Added **`IStorageProvider`** **`StorageSubscription`** **`StorageProviderSubscriber`** and **`IObservableStorageProvider`** to the package exports
Removed the **`walletType`** argument from the **`login`** method of **`useWalletLogin`** hook Removed **`IStorageProvider.subscribe`** method (use **`IObservableStorageProvider`** when custom subscription logic is required)
- gm lens frens 👋
Today I have made an important decision in my life 📢
I quit my job today and going to focus full-time on maintaining the first-ever open-source frontend @lenster.lens 🌸 powered by @lensprotocol 🌿.
Building social media was my dream since 10th grade, I built more than 4 social media in public but all failed, Lenster is my 5th one and it’s going crazy ⚡️.
I believe building in public is key 🔑 to the success of a product.
We have a lot of items queued up in the roadmap, be excited about it 🕺
**Collect this post for 2 WMATIC and support Lenster’s development 🙏**
- Yesterday Lens Protocol announced the CultivatorDAO (👩🌾,👨🌾) to establish community driven content curation for Trust & Safety. Going to share our vision below on how we see the web3 social stack evolve 🧵
First, Lens Protocol is a decentralized social media protocol that acts as a registry to point content and followers. Users can link to any content which can be stored on-chain & off-chain. Most of the content is off-chain (stored in IPFS or Arweave etc).
The Protocol is flexible enough to link the content even to a private cloud or to a self-hosted environment. This is an interesting use case for follower and token gated content. It's up to the applications and users to choose how they use Lens Protocol.
Lens Protocol design guarantees users the access to their own social network. You don't need to trust centralized or off-chain platforms with your followers. Meaning every user has their own social network.
Not only you own your own network, but you also have the ability to broadcast content in a permissionless and censorship resistant way. Anyone you grant the access to your content has the ability to explore your creativity and self expression. This is decentralization by design.
While decentralization is groundbreaking for web3 social, the amount of information and finding relevant peers and content for you to discover would be a time consuming mission. This reason is why we would see another stack evolve - the middleware - where curation lives.
The middleware layer already exists on Lens Protocol, there are tools such as Graph Protocol, RSS3, Sepana and the Lens API. The middleware layer consists from widely decentralized appoaches to being progressively decentralized depending on the use cases they serve.
The latest addition to the middleware are communities such as the CultivatorDAO, focusing on curation with Trust & Safety in mind. Where code cannot solve everything, we need communities to reflect their values and govern.
The DAOs of the Lensverse will serve the application layer for various tasks ranging from building discovery algorithms, content moderation and solving various challenges that social media faces today.
The key difference between the web2 and web3 social stack is that in web3, the stack is completely open. When you don't like a policy or an experience, as a user you should be able to find a new experience without leaving behind your accumulated social capital.
Hopefully we will see small communities evolve across the web3 social ecosystem, being utilized for tasks that would benefit from community governance.
I would even imagine that every social media application built on top of Lens Protocol would have its own DAO consisting of its community members voted by the community that reflects the their own values.
Most importantly, these DAOs can operate transparently and since the measures taken by these DAOs are public, there should not be any shadow banning (see here: https://lenster.xyz/posts/0x05-0x0417).
By ensuring human assessment and the design that leads to decentralization, we are able to ensure that web3 social doesn't become a closed platform and users are able to access to open social networks that are driven by community engagement & stewardship.
Building a decentralized stack is a harder exercise than starting from a centralized approach, but brings the benefit of fully verified content linking on-chain wherever you store your content, ownership to your social graph, ability to use timestamps and create programmability.
And most importantly: decentralized and on-chain content and follower registries opens up the programmability and composability to another level. Imagine pairing Lens with tools like Simo, Lit Protocol, DeFi, NFTs, ReFi and DAO governance.
Besides reachitecturing the social stack, part of the mission for the Lens team is to make the social stack more accessible. Now with all interactions across the Lens Protocol, users do not need to sign or pay any gas. Blockchain on the backend, party on the frontend 🥳
Next Monday, you will be able to vote for CultivatorDAO with your Lens Profile to signal your support for community driven stewardship https://snapshot.org/#/cultivatordao.eth/proposal/0xd512345eb6c9b7bbf57b28a8b4f7dc46d31ab6c19ac8ad5de4605fa52fcb9e98
If you love our vision and what we are building, collect and mirror this post to retain your early user flexing rights 🌿
- web 6️⃣9️⃣
- 🔊 **POAP** 🌠 for early @lenster.lens bloomers coming soon, it will be distributed in the Snapshot app ⚡️
Followers snapshot will be taken in couple of weeks so make sure to follow @yoginth.lens and @lenster.lens 🌸 to receive your unique POAP 💜
- Drop your `.lens` handle here, so you won't regret it later 👀