Noé G (@0xnoe) • Hey
Co-Founder at White Loop Capital
Publications
- Gm + also trying @philand quests ! #Yasai
- ✨Phi🏝️ × Lens🌿✨
"Yasai Lens Festival", an Official Campaign Collabs with @lensprotocol 🌿 & @lenster 🌸, is now live on Phi🎉🤩
📅 Campaign Period: 7th Feb ~ 21th Feb 2023 12:00AM UTC
Yasai Lens Festival has 2 parts:
1) Yasai Quests🌿 - Taskbased Quests dedicated to @lensprotocol 🌿 & @lenster 🌸
2) Good Lenster Post Race🏁 - A Community Race for Good Lenster Posts
Check out the details 👀🧵↓
https://quest.philand.xyz/campaign/lens-yasai
- Gm
- We will always have Paris, anon
- 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}
- USA :
- Whitepapers should be written using LaTeX, it should be a standard, it's much more pleasant to read...
- Hello World