Litecoin (@zenezenee1) • Hey

Publications

What are the things that are neglected in daily life?
Do you like this screensaver?
Man of Crypto: Vietnam - 16M Crypto users, Growing Economy, Young Population In this video, we'll take a look at the exciting crypto world of Vietnam. With 16 million crypto users and a growing economy, this is one country you don't want to miss out on. We spoke 🙊 with Binance, ETH Vietnam, and Coin98 We tried to exchange ETH 💰 for food 🦞and local services 🏄🏻‍♂️ Take a look 🎥 how far did we go! Follow us on socials: @manofcryptoxyz
fengxuewangguo
RELEASE - 1.9.0 - August 22nd, 2022, 11:15 ## Features - feat: add some new indexes - feat: free follow and free collect logic in the `proxyAction` and `proxyActionStatus` - feat: speed up explore profiles sql - feat: add spam to the reporting - feat: ability to validate your publication metadata before you submit it `validatePublicationMetadata`. This allows devs to not submit broken metadata standards and easily debug. - feat: ability to check the status of your metadata after you upload and its mined `publicationMetadataStatus`. This will give full visibility if its not queryable. - feat: speed up the explore publication query ## Bug fixes - fix: resolve notification mirror profile You can now follow people who do not have a follow module or collect publications which are free without doing an approval modal. Enjoy!
Lens BigQuery Public Dataset is Live 🔍 Read more about unlocking new possibilities in our blog https://mirror.xyz/lensprotocol.eth/L-VyE549sOOdi4nBgos6XNAUgf3H1oErfkAtndU6RHY Learn how it works in our developer docs https://docs.lens.xyz/docs/public-big-query
Do not drop your Lens handle below 👇 (social experiment)
Accept Lens handles for collect recipients
Serious question, why do you buy NFTs?
So... whats the best proof that universal basic income could work?
very energetic
Stani for a boy
Cool audio features from @buttrfly.lens nice work @0xmoe.lens 🦋🎧
Need some help with baby names, share below your most favourite (boy n girl) 👇🏼
To all my Persian homies and girlies
# 1.0.14 - June 13th, 2022 3:27 PM ## Features - feat: whitelist lenstube to use gasless - feat: add `TOP_MIRRORED` to `explorePublications` ## Bug fixes - fix: hide `hidden` publications from explore
# 1.0.15 - June 14th, 2022 4:28 PM ## Features - feat: add nonce management on periphery contract and follow nft contract ## Bug fixes - fix: resolve search on partial matches for hashtags
# 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
**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
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 🤯
Spring deployed in Hyde Park London
some things are really laughable
大家好
# 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
How is the currency circle forwarding?
Argentina's secondary market is booming. You can buy fiat with stablecoins at better rates. Someone was offering Lens swag at significant premium and there are already quotes for the next rAAVE tix
@teaparty.lens
bored
So… who is having a merge party this week?
Institutions are coming is the all time best crypto meme
# 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.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
send a barrage
Recent @memester.lens excitment meme post on me minting Memester's Follow NFT tokenID #180 got me thinking of an interesting application where Lens Protocol Follow NFT holders could trade their Follow NFT up or down the rank. I would love to own @memester.lens tokenID #1 but would probably need to first swap 180 to 90 and then to 30 and to 7 and to 1 to climb the ladder. Especially valuable since users can set different collect rules based on Follow NFT token ids and create scarcity. My next question is... any devs here want to build this small app? I can help on guiding throught kickass leaderboard design ideas.
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!
RELEASE - 1.9.1 - August 22nd, 2022, 16:00 Features - feat: all dApps on testnet can use gasless + dispatcher within the API freely! Happy building!
The sad part about the Finnish PM dance gate was that no one was able to collect it as NFT
The sad part about the Finnish PM dance gate was that no one was able to collect it as NFT. That would have been a culturally relevant piece.
# 1.2.0 - June 20th, 2022 17:45 PM ## Features - feat: expose `hasCollectedByMe` field resolver on all `Publications` - feat: expose `mirrors(by: ProfileID)` field resolver on `Post` and `Comment` - feat: expose `isFollowedByMe` field resolver on the `Profile` - advised to use the above on using `DoesFollow` - feat: expose `isFollowing` field resolver on the `Profile` - advised to use the above on using `DoesFollow` - feat: extend metadata input to include `image` - feat: allow `addReaction` to toggle the reaction ## Bug fixes - fix: lowercase the `AppId` so sources work - fix: update profile metadata issue - fix: explore top collected and top commented acting odd when no random - fix: return on-chain profile metadata link and not snapshot link ## Breaking changes - 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.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
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"])
How is the currency circle forwarding?
City of Buenos Aires just became even more cooler https://www.coindesk.com/policy/2022/08/11/buenos-aires-city-to-deploy-ethereum-validator-nodes-in-2023/
Argentina's secondary market is booming. You can buy fiat with stablecoins at better rates. Someone was offering Lens swag at significant premium and there are already quotes for the next rAAVE tix
@teaparty.lens