88888888eth (@88888888eth) • 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
# 1.0.8 - June 8th, 2022 4:40 PM ## Bug fixes - fix: cache stats
# 1.0.7 - June 8th, 2022 2:50 PM ## Features - feat: change recommended followers to be hard coded for now until ML ## Bug fixes - fix: resolve internal IPFS uploads race condition
# 1.2.1 - June 22nd, 2022 17:32 ## Features - feat: allow ability to filter on `timelineTypes` - feat: gasless for `iris`, `teaparty` and `alps` - feat: support new query `profilePublicationsForSale` to grab all publications for sale for a given profile - feat: add cache headers on some internal storage to make it faster ## Bug fixes - fix: Incorrect paginatedResultInfo when querying `whoCollectedPublication`
# 1.3.0 - July 6th, 2022 15:45 ## Features - feat: on hidden it should not bring them back on `timeline`, `search` and `profiles` - feat: add follower fees into global stats - feat: extend refresh token to be valid for 7 days to allow mobile apps better UX - feat: expose `sns` and push everywhere for third parties - feat: add `profilePublicationRevenue` and `profileFollowRevenue` - feat: huge refactor to make backend a monorepo - feat: add dev-portal-api - feat: add sns notification service to listen for streams of data - feat: be more aggressive on the indexer if our node provider is down and never give up - feat: improve error handling and tracing when indexer throws - feat: internal API if publication hidden do not allow comments or mirrors - feat: add source onto free text claim handles column ## Bug fixes - fix sync issue related with NFT profile - fix: when commenting on post pull in the `appId` if we can fetch it before the insert - fix: issue with timestamp coming back as `ms` sometimes and `unix` sometimes - fix: count was wrong for getting comments on publication - fix: issue with app id not be populated on publications - fix: `ipfs_internal_uploads_pkey` PK issue - fix: devportal: refactor how users are added in app creation and update - fix: resolve issue with approval followers total count - fix: resolve validation on metadata version - fix: throw error if `txId` is not defined - fix: make `profileId` nullable on `ReactionFieldResolverRequest` to make querying it easier on mirrors - fix: Error: Property 'token_id' doesn't exist. - fix: on the indexer to handle the bug found on prod contract - fix: issue with nft sql - refactor: indexer events clean up and more resource friendly - fix: bring back hidden publication when query by publication or query by tx for publication - fix: indexer bug if resync falls over it could end up skipping blocks without checking - fix: resolve sql error `updateProfileImageURIOnChainQuery` - fix: resolve trigger count to on conflict do nothing on some insert cases - fix: internal profile metadata updating - fix: profile metadata attributes added validation ## Breaking changes - breaking: `profileRevenue` has now changed to `profilePublicationRevenue` to make the schema clear with the new added `profileFollowRevenue` ### Actioned - breaking change: `hasCollected` is `deprecated` you should use the `hasCollectedByMe` field resolver on the publication, this will be removed from on 1st of July 2022 - breaking change: `hasMirrored` is `deprecated` and you should use the `mirrors` field resolver passing in the profile id the user is active on, this lives on the publication, this will be removed from on 1st of July 2022
# 1.10.0 - August 24th 2022, 11:00 ## Features - feat: allow unknown collect modules (sandbox incoming) - feat: allow unknown follow modules (sandbox incoming) - feat: allow unknown reference modules (sandbox incoming) - feat: improve error tracing - feat: whitelist orbs and social3 for relay - feat: bake in retries of the relay on proxyActions - feat: add `getWhoReactedPublication` so you can fetch who reacted to a publication - feat: enable `fastest` in relay mode to avoid going into secondary nodes - feat: prod API dashboard deployment ## Bug fixes - fix: issue sometimes getting back reactions - fix: extra checks if only followers can collect the free collect
# 1.10.1 - August 24th 2022, 17:30 ## Features - feat: mutual followers ## Bug fixes - fix: resolve validation on metadata bio, name, attributes - fix: relay - fix: resolve bad `bio` in metadata profiles
# 1.11.0 - August 26th 2022, 11:00 # Features - feat: deploy sandbox API to production allowing builders to have an environment they can whitelist modules and use the API
# 1.12.0 - 2st September 2020, 14:30 ## Features - feat: big query base generic package lays out the interface to query - feat: write the machine-learning base package and add the first wtf-rec logic in - feat: `recommendedProfiles` now uses ML to predict who to follow ## Bug fixes - fix: explore fix on publications - fix: profile metadata snapshot - fix: tagging searching - fix: metadata filtering and paging
# 1.12.1 - 5th September 2022, 13:00 ## Features - feat: make explore default time 24 hours not 1 week to try to explore more publications and make it more fun for UIs - feat: add new explore filter which is `CURATED_PROFILES` to allow discovery on known good content profiles - feat: order collects by default profiles first then collected times to make profiles be top - feat: order followers by default profiles first then follow time to make discovery better and wallet fall at the bottom - feat: make random on explore a bit better instead of random everything use only its context it got back
# 1.12.2 - 9th September 2022, 18:00 ## Features - feat: allow internally to use metadata v2 - feat: extend the curated profiles - feat: improve the publication building - feat: improve query speed all round
# 1.13.0 and 1.14.0 - 14th September 2022, 12:30 ## Features - feat: custom filters cron - feat: the first custom filter gardeners - feat: add more curated profiles - feat: add reactions to notifications ## Bugs - fix: resolve 5xx sometimes happening when pod is not ready
# 1.17.0/1.16.2 - 12th October 2022, 12:00PM ## Features - feat: migrate cron to rust `cron-sybil-org-rs` - feat: migrate cron to rust `cron-custom-filter-sync-rs` - feat: feed aggregator replaces `timeline` - feat: protect the amount of scanning 1 alias can do. You are now limited to 3 per query and 1 per mutation - feat: fix pods sometimes going down with 5xx due to memory issues - feat: add authentication record to get more visibility of active users - feat: improve performance and decrease hosting costs ## Bugs - fix: resolve mentions notifications not being sent - fix: degree of seperation 0 means nobody can comment even yourself - fix: locale to handle bad regions for now - fix: proxy free collect if following allow to collect ## Nullable warnings - `totalCount` on `PaginatedResultInfo` is now nullable as some queries like `feed` can not work out full total due to aggregation ## Breaking changes - incoming breaking change: `timeline` will be removed on November 15th, 2021 use feed instead - incoming breaking change: `collectedBy` on `Post` and `Comment` will be removed on November 15th, 2021 - incoming breaking change: `timeline` will be removed on November 15th, 2021 use feed instead - incoming breaking change: `collectedBy` on `Post` and `Comment` will be removed on November 15th, 2021
# 1.18.0-1.19.0 - 28th October 2022, 18:00PM Features - deployment: reorganize tags on deployment to have better visibility on our monitoring tool. - feat: feed highlights - feat: allow `profileIds` in the publication query! - feat: ability to filter on notification type to allow rich UIs - feat: allow `profileIds` with `collectBy` in the publication query - feat: support ML on big table and bring back ML recommendations - feat: content should have a max length of 30,000 chars before it can be indexed - feat: start storing the content of publication in db for ML purposes - feat: shard the relay to improve relay performance (1 of 3) - feat: extend gasless limits - feat: add more profiles to the curated Bugs - fix: bug in first_comment_id should be the first not the last - fix: resolve all the * in queries to avoid loading more stuff in memory then needed - fix: add extra validation on metadata to avoid empty content - fix: bug in first_comment_id should be the first not the last - fix: resolve all the * in queries to avoid loading more stuff in memory then needed - fix: add extra validation on metadata to avoid empty content
# 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.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
**RELEASE** # 1.23.0-1.25.0 - 22nd December 2022 Database migration to aurora is now fully complete. We hope everyone has a merry christmas and happy new year, this one is free to collect as an early christmas present from the team, enjoy all! On top of this here is everything else which is within this release. ## Features - feat: DA mirrors, comments, posts (not exposed) - feat: worldcoin SMS identity verification - feat: DA signed typed data (not exposed) - feat: extend code to handle reads and writes from different db connections - feat: increase max pool to 50 and holding connections open for 60 seconds - feat: allow ability to spread out the database reads into many read hosts to improve performance - feat: config the read and write host connections - feat: make running the backend easier and faster locally - feat: improve some publication query performance by 2x - feat: make feed only query reactions when it needs to - feat: native arweave uploads - feat: http and ethereum improvements. Http one means sharing connections! ## Bug fixes - fix: scalar on gated collect condition - fix: streamline ScalarOperator enum - fix: gated: check if erc20 token condition references a smart contract that does not exist - fix: resolve unfollowing issue sometimes happening - fix: resolve unknown follow modules working - fix: whoMirroredPublicationId results are not in order
we will be doing a database migration moving to aurora to allow our pings worldwide to be faster, general speed up of all queries, having many read databases with auto-scale, alongside having read and write separate databases for memory reasons. This will mean on 08:15AM GMT Thursday 22nd December write actions will be down for 20 minutes. - indexer will not index any new publications, profiles etc - reactions and other parts will not be able to be actioned once the migration is complete the indexer will catch up with anything it missed of course anything on-chain will still go on-chain but not be shown in the API if done in that period until it is back. Reads will continue working as normal throughout the migration process. Happy building all!
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 🌿💚
🔊 **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 👀