999999999eth (@999999999eth) • Hey

Publications

Invites have been given to a segment of Lens accounts. See if you have invites here: https://invites.lens.xyz
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
RELEASE - 1.6.0 - August 11th, 2022, 15:00 Features - feat: metadata v2 support - https://docs.lens.xyz/docs/metadata-standards - feat: ability to filter on metadata v2 on publication queries - feat: create a cron for migration so we can execute them in code on box without ssh - feat: map dedicated lens infura to help with infura public gateway issue - feat: add notification id in the notification response to help client side caching - feat: expose endpoint to bring back all the tags filtered by popular and app - feat: profile and publications syncer now have different crons and x3 load allowance feat: Integration with ENS to enable the offchain resolve. back dated feature log: - feat: ens on-chain identity now in the database - feat: sybil.org linking for on-chain data https://github.com/Uniswap/sybil-list/blob/master/verified.json - feat: `onChainIdentity` now exists on `Profile` - feat: publication stats > `totalAmountOfComments` is a global stat of the amount of comments, if your filtering on sources some comments may not be included in what your trying to show. This means the count number would be wrong. We now have have a field resolver on the `PublicationStats` type which will return the total amount of comments for the sources you specified: 1) commentsTotal(forSources: ["app1", "app2”]) 2)postsTotal(forSources: ["app8"]) 3) mirrorsTotal(forSources: ["app8"]) 4) publicationsTotal(forSources: ["app9"])
RELEASE - 1.7.0 + 1.8.0 - August 19th, 2022, 10:00 Features - feat: dispatcher public API! (whitelisted apps) - feat: upgrade relay npm package - feat: extra info for claiming - feat: worldcoin integration https://human.withlens.app/ - feat: worldcoin on chain identity is now on the profile - feat: improve graceful shutdown of pods Posted using the dispatcher!
# 1.20.0-1.20.1 - 4th November 2022 This is a huge step forward for UX for the API. This is our first steps doing optimistic API updates, this means when you do a free follow or collect the state will be reflected straight away in the UI experience. No need for hard UI optimistic caching and this inherits on all of the lens apps instantly. The transaction then is processed in the background without the user having to wait. This means for example you follow user Y and then refresh it will still look like your following, you will start seeing them in the timeline and it just be as it is like on web2 social media sites. Optimistic API updates is something we going to be doing for all actions as we start trying to build the best UX we can from the API level. Features: - feat: optimistic proxy action follow - feat: optimistic proxy action collect - feat: improve has tx been indexed reporting error quicker
The Lens API Team has received a request from the community to open up discussion for a new version of the metadata standard. We invite the entire Lens Dev Community to join the discussion on Github and contribute your ideas to version 3 of the metadata standard! https://github.com/lens-protocol/api-examples/discussions/101
# 1.22.0 - 16th November 2022 Big release today, you can now gate your publications with access criteria. Remember your publications itself is an NFT so you can gate a publication so only people who collect can see it, same with your follow graph. Very excited in what you guys build with this. Alongside this we have also exposed an endpoint to allow you to upload videos and audios, as we have seen uploading those via IPFS and serving them can cause them to buffer and be slow. Our API endpoint will upload it and transcode it serving that file to all people who call the API. Behind the scenes it will be pinning it to IPFS so on-chain state is still decentralized. - feat: profile interests - feat: gated publications powered by LIT - https://docs.lens.xyz/docs/gated - feat: add 3 new providers to gasless - feat: if no default profile picked select the first created one to expose more profiles - feat: ability to upload audio and videos via the API and it be pinned for you on ipfs but the transcoded version will be served for better audio and video experience - https://docs.lens.xyz/docs/media
# 1.23.0 - 30th November 2022 ## Features - feat: DA base package - feat: bring in curated profiles into the database for ML - feat: make backend to be easier to run locally - feat: expose curated profiles to big query - feat: performance upgrades and scaling improvements ## Bug fixes - fix: do not get notifications for stuff once it is hidden - fix: resolve canDecrypt on nested conditions
**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 🌿
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 🧾 🧾 🧾
Some numbers 📊 from Lenster 🌸 for the past 4 days **~100,000** page views 👀 **~12,000** unique visitors 👥 **~150** countries 🌎 **~2,600,000** edge CDN requests 🌐 **~50 GB** bandwidth from image CDN 🏞 still counting... Thanks @lensprotocol for being with us from day one 🌿💚
Some numbers 📊 from Lenster 🌸 for the past 4 days **~100,000** page views 👀 **~12,000** unique visitors 👥 **~150** countries 🌎 **~2,600,000** edge CDN requests 🌐 **~50 GB** bandwidth from image CDN 🏞 still counting... Thanks @lensprotocol for being with us from day one 🌿💚
Drop your `.lens` handle here, so you won't regret it later 👀