848eth (@848eth) • Hey

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
Lens devs keep shipping 🛳️ 💨. A lot of cool things have been added with 1.26.0. **Features** ·Ability to create Nft galleries ·Added support for data availability for mirror with signed typed data (staging only) ·Add support for data availability for comment with signed typed data (staging only) ·Added support for 'ar://' protocol in metadata ·Added support for 'ar://' protocol in metadata ·Added support authentication with EIP1271-compatible smart wallets ·Added indexes to the database ·Added support for MultirecipientFeeCollectModule ·Added support for AaveFeeCollectModule ·Added support for ERC4626FeeCollectModule ·Added more relays to load balance to spread out traffic ·Enabled **hasTxHashBeenIndexed** to be accessible without auth token ·Moved the Follow Proxy action to RabbitMQ. ·Moved the Collect Proxy action to RabbitMQ. ·Removed Internal endpoints ·Rewrote the notification service to improve performance ·Removed wallets from showing in the **of** follower list ·Handle validation internal extensions ·Lensqueue granular error handling ·Rabbitmq metrics and alerts ·Improved speed latency on redis ·Improved Estimate of gas ·Improved Contain memory spikes ·Whitelisted new apps for gasless transactions **Bug fixes** ·Added optional pretty name to whitelisted currencies ·Added block timestamp to indexer ·Added optional pretty name to whitelisted currencies ·Fixed typo in GraphQL schema doc ·Fixed collect records mismatch on the backend ·Fixed typo in GraphQL schema doc ·Fixed nft population in nft gallery ·Fixed Internal error counts ·Fixed typo in GraphQL schema doc ·Gated working on the dispatcher ·Resolved issue on collect modules circular references ·Resolved issue: When using the **whoMirroredPublicationId** field in the request and querying a publication with multiple mirrors by the same profile profiles repeated in the response ·Resolved issue on collect modules circular references ·Resolved uncaught exceptions for graphql validation errors ·Redis expiry times made dynamic ·Resolved deadlocks on db ·Stopped supporting kovan, rinkeby and ropsten testnets ·Validation metadata fixes **Breaking changes** ·**Feed** and **feedHighlights** now require auth to call them **Breaking changes actioned** ·ACTIONED: breaking change: **timeline has been removed**
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 🌿
Guten mergen. Here’s a little something from us, to you. Lots of hidden secrets to find. Catch it on a rare tee or some stickers at ETHBerlin, snap a pic and share it below. Until then, collect our poster on Lens. Yours truly, GROCERY WORLD 🧾 🧾 🧾
🔊 **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 👀