王一博1号 (@illusia) • Hey
王一博是明星
Publications
- 柴多火旺。 水涨船高
- Allow us to reintroduce ourselves...meet the native hyperscaling solution for Lens, Momoka! Momoka is an Optimistic L3 scaling solution, that will process transactions at hyperscale, and is designed to support the next generation of web3 social users.
Data availability layers are utilized to prevent storing information on-chain. While content on Lens may include an on-chain transaction, the content data is linked to a data availability location, like Momoka.
Momoka serves as a scaling solution that processes Polygon transactions off-chain, achieving hyperscale and reducing costs. Unlike L2 solutions, Momoka doesn't compress transactions into L1, it sends and stores them on a data availability layer.
The main challenge for decentralized social networks is to ensure that users have control over their content, while still being just as user-friendly as traditional social networks. Momoka makes the future of decentralized social possible.
We've worked relentlessly with the @bundlr-network.lens and Arweave teams to ensure scalability by providing Data Availability (DA) guarantees, allowing the use of Ethereum Virtual Machine (EVM)-supported wallets to save DA logic and facilitating the rapid publishing of data.
Permissionless innovation is at the core of everything we do on Lens. As we approach one year on mainnet (still in beta), we have been blown away by the talent and passion in our dev community but we realize in order to scale to the masses, we need to build new solutions.
Since yesterday, Momoka is already being beta tested on Lenster, Lenstube, Orb, Buttrfly and Phaver.
We look forward to seeing more applications roll out Momoka.
To make it easier to find any transaction made with Momoka, we built the Momoka Explorer (http://momoka.lens.xyz) to track and find Momoka transactions and to monitor the throughput speed of Momoka.
Join our Spaces today at 15:30pm UTC to hear from @stani.lens, @wagmi.lens, @nader.lens, and special guests from Bundlr and Arweave: https://twitter.com/i/spaces/1nAKEryXyDYGL/peek
- **Lens SDK 1.1 - Improvements in this release**
1) Momoka support
2) Self-funded transactions fallback
3) Bi-directional pagination traversing
4) Supports limited free collects
5) Several `LensClient` improvements
6) Bug fixes and minor improvements
**What's new?**
**Momoka support**
The Lens SDK React hooks now support Momoka publications. To start using Momoka today just upgrade to `@lens-protocol/react-web@latest` and the SDK will take care of the rest.
The Lens SDK will choose Momoka posts over on-chain posts automatically based on your collect settings. It will also know when comments and mirrors need to be on Momoka infrastructure based on the referencing publication.
**Self-funded transactions fallback**
Occasionally gasless transactions might not be available for a given profile. To provide continuity in your user experience you can now fallback to execute transactions using the user's funds to cover gas costs. More documentation is available here: https://docs.lens.xyz/docs/self-funded-transactions
**Bi-directional pagination traversing**
It's now possible to traverse paginated results in both directions (older and newer results).
This allows you to implement functionalities such as "pull to refresh" on a mobile app or fetch newer feed entries. See this example as a reference: https://github.com/lens-protocol/lens-sdk/blob/main/examples/web-wagmi/src/discovery/UseFeed.tsx#L63
**Supports limited free collects**
Last month we launched a new collect module called `SimpleCollectModule`. In this SDK release, you can leverage all its potential. For example, you can define a Free Collect with a limited number of NFTs to be minted.
**`LensClient` improvements**
We added `client.authentication.verify` and `client.authentication.getAccessToken` methods to enable extraction and verification of someone's API credentials.
- Until next time, Tokyo ✌️
Featuring: @ethglobal.lens, @galverse.lens, and DAO Tokyo
- 总不能要求我都是好的吧
- 啊啊啊啊 小猫咪也太可爱了叭!!!
- 某年某月某日,我看了你一眼,并不深刻。
某年某月某日,意外与你相识,无关心动。
怎知日子一久,你就三三两两懒懒幽幽,停在我我心上
- Lens Hackathon presentations happening now at @ethglobal.lens Tokyo!
- Look deep enough
- Limited edition Lens PopSockets available at @ethglobal.lens Tokyo
- 别回头,身后的万家灯火,都不是你的归宿,前面的万丈深渊,都是你的必经之路
- I can't believe Justin Timberlake actually said this in the movie
- Analyzing your audience on @lensprotocol
I'm going to start posting more ideas on the Lens ecosystem, it's a fascinating environment to watch and its potential excites me the most.
I'm hoping that the collects I bring to each post will emphasize the importance of these ideas coming to life and hopefully spark a sense of excitement in the current and future builders of this space.
The community is just getting started and the possibilities are endless.
0.69 matic to collect, only open for 24 hours and 10% goes out to @alense.lens for her wonderful idea.
- LensGarden NFT is the first dynamic NFT collection on Lens Protocol, it is a unique blockchain-based platform that is part of the LensProtocol ecosystem. It rewards users for creating and curating high-quality content, providing incentives to engage with the LensProtocol community and build their profiles.
Users can earn XP by completing activities such as joining liking, commenting, following Lens users, and completing challenges. As they progress through the levels, they have the opportunity to mint exclusive NFTs that cannot be traded on marketplaces, adding further value to the platform.
Here are some tips on how to increase your XP:
Gain followers: For each new follower, you'll earn 50 XP points.
Create new posts: Every post you create on the Lens Protocol ecosystem will get you 30 XP points.
Leave comments: For every comment you leave, you'll earn 20 XP points.
Collect : Each post of yours that is collected on the Lens Protocol ecosystem will get you 20 XP points.
Mirror other users: Each time you mirror another user's post, you'll earn 30 XP points.
Lens Garden NFT presents an exciting opportunity to invest in a growing blockchain ecosystem that rewards engagement and incentivizes high-quality content creation. The potential for growth and innovation is significant. Additionally, in Q2, you can look forward to the launch of Lens Tunes and an exciting new game.
Join us today and become a part of this innovative and exciting ecosystem.
- 明人不放暗屁
- 2 more days until @lensgardennft.lens 🪴is open publicly. Get ready because we are about to blow up activity on @lensprotocol.lens 🌿
- 有心不在迟
- "Bear markets give entrepreneurs time. It takes time to talk to users, test, and iterate. There is no such thing as an overnight success." @stani.lens at #ETHDenver w/ John Paller and @vitalik.lens
- Who is creating great content?
Tag your favorite creator on orb app.
The most interesting creator will win an exciting prize.
- Ronnie uses Collateral Swaps.
Available across all V3 markets on app.aave.com. Powered by ParaSwap.
- 🌌
- 总有人会爱上你的清澈,
也会拥抱你的不堪。
- Spend sometime playing with the lens client sdk and made the following graph diagram check it out at https://lensgraph.sserrano.com
- hi。互相关注吗
- Create funny and dank Lens memes. We’ll mirror and highlight our favorites.
We are running a competition on @memester-xyz.lens! Go to https://memester.xyz to submit your entry!
- lens Garden in my dream
- Our friend Alex got an invite to a big event we were all excited about.
You were there too!
Do you remember who Alex met that was so special?
- Sun lovers 🌞
- For our fellow New Yorkers out there
- 这个世界乱糟糟的
- 7788
- This is Lenny
- 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 🤯
- 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
- Here's everything you need to know about our 0.2.0 Lens SDK Update
https://github.com/lens-protocol/lens-sdk
- **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)
- 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**
- 1111com
- # 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
- hh
- From @mrmattmccarthy: "She Ain't Heavy, She's My Kitty 🍁"
- The Lens API Team have received a proposal from @yoginth.lens @ellie.lens @phaver.lens @asian.lens @cesare.lens @m1guelpf.lens @wagmi.lens for a new version of the metadata standard.\n\nThe proposed metadata standard (version 2.0.0) is copied below, please comment with any changes or suggestions!\n\ntype Markdown = string;\ntype Url = string;\ntype AppId = string;\n\ninterface MetadataV2 {\n /**\n * The metadata version.\n */\n version: '2.0.0';\n\n /**\n * The metadata lens_id can be anything but if your uploading to ipfs\n * you will want it to be random.. using uuid could be an option!\n */\n metadata_id: string;\n\n /**\n * A human-readable description of the item.\n */\n description?: Markdown;\n\n /**\n * The content of a publication. If this is blank `media` must be defined or its out of spec.\n */\n content?: Markdown;\n\n /**\n * IOS 639-1 language code aka en or it and ISO 3166-1 alpha-2 region code aka US or IT aka en-US or it-IT\n * Full spec > https://tools.ietf.org/search/bcp47\n */\n locale: string;\n\n /**\n * Ability to tag your publication\n */\n tags?: string[];\n\n /**\n * Ability to add a content warning\n * enum properties = NSFW, SENSITIVE, SPOILER\n */\n contentWarning?: ContentWarning;\n\n /**\n * Main content focus that for this publication\n * enum properties = VIDEO, IMAGE, TEXT, AUDIO, LINK, EMBED\n */\n mainContentFocus: MainPublicationFocus;\n\n /**\n * This is the URL that will appear below the asset's image on OpenSea and others etc\n * and will allow users to leave OpenSea and view the item on the site.\n */\n external_url?: Url;\n\n /**\n * Name of the item.\n */\n name: string;\n\n /**\n * These are the attributes for the item, which will show up on the OpenSea and others NFT trading websites on the \n item.\n */\n attributes: {\n // enum properties = number, string, date\n displayType?: MetadataDisplayType;\n traitType?: string;\n value: string;\n }[];\n\n /**\n * legacy to support OpenSea will store any NFT image here.\n */\n image?: Url;\n\n /**\n * This is the mime type of image. This is used if you uploading more advanced cover images\n * as sometimes IPFS does not emit the content header so this solves the pr\n */\n imageMimeType?: MimeType;\n\n /**\n * This is lens supported attached media items to the publication\n */\n media?: {\n item: Url;\n /**\n * This is the mime type of media\n */\n type: MimeType;\n\n /**\n * Add alt tags for accessibility\n */\n altTag?: string;\n\n /**\n * Cover for any video or audio you attached\n */\n cover?: Url;\n }[];\n\n /**\n * Legacy for OpenSea and other providers\n * A URL to a multi-media attachment for the item. The file extensions GLTF, GLB, WEBM, MP4, M4V, OGV,\n * and OGG are supported, along with the audio-only extensions MP3, WAV, and OGA.\n * Animation_url also supports HTML pages, allowing you to build rich experiences and interactive NFTs using JavaScript canvas,\n * WebGL, and more. Scripts and relative paths within the HTML page are now supported. However, access to browser extensions is not supported.\n\n */\n animation_url?: Url;\n\n /**\n * This is the appId the content belongs to\n */\n appId?: AppId;\n}