binnace (@binnace) • Hey
binnace (@binnace) • Hey
Publications
- carf gf
- I don't think social media aggregators are useful but curating content from an open social network is
- 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**
- vdfbcvb hr hfgvbh
- ASD
- You may have noticed that the Who To Follow recommendations displayed in Lenster (and other frontends that use the Lens API) are looking a bit different recently. The Lens ML team, which I lead, recently released an update to the algorithm that backs that API endpoint making it so that recommendations are now personalized to each user. Our hope is that you're now getting recommendations that make more sense based on the profiles that you already follow.
The algorithm is still in a beta period and we're looking for feedback on the recommendations. So how do they look for you — better, worse, the same? Maybe you discovered someone you didn't even know was on Lens? Maybe it's a bunch of low quality profiles? Let us know!
- When will the epidemic end
- Switched my default browser back from Brave to Firefox. AMA.
- Low Kinship by NoFuturistic
This song was created by @nofuture.lens and airdropped to all holders of the "Alchemical Drip" NFT
- 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}
- 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"])
- # 1.0.16 - June 15th, 2022 10:18 AM
## Features
- feat: make it easy to turn db logs on
## Bug fixes
- fix: search error `.toHexString()` throwing on search publication query sometimes
- Good will come.
- Post a picture of a Taco 🌮 below with a 5 Matic collect fee, will collect the most delicious looking one
- gm Phaver 🫡