Farcaster

how would you describe Farcaster culture?

some guy made a Farcaster Client Agent Guide ⁽ᵗʰᵃⁿᵏˢ ᵈᵃᵈ⁾

less than 24 hours and we have a fork for every user. not bad.

opportunity for another client

tag a builder whose thing you actually use. they probably don't hear it enough.

https://x.com/nikitabier/status/2082140254237241588?s=20

@fireflyapp is onboarding as a snapchain validator! the Firefly team has been building on farcaster from Asia for years. huge thanks to their team for continuing to support Farcaster. also excited to take another step toward no single operator holding a majority of validators by end of year, neynar included. if you're interested in running a snapchain validator, reply to this cast, or check out the FIP if you want to help validate without running snapchain: https://github.com/farcasterxyz/protocol/discussions/272

What the devs are working on this week: -Clanker: v5 rollout pushed back. security audit got extended and we're waiting on it to come back. ensuring security matters more than shipping fast -Protocol: getting blocks live on Snapchain + moving toward an on-chain governed validator setup + scoping out channel decentralization -Farcaster Client: investigating the feasibility of a public snapshot of the Farcaster client -Wallet: better handling when a data provider is down (shows your last-known balances + a heads-up banner instead of wrong numbers) + finishing a provider migration + evaluating a new transaction-scanning provider to cut false flags -Sign-ups: sponsored sign-ups going live -Feed quality: follower counts now reflect Neynar score + real activity + swapping out the last of the old spam labels -Mini apps: push notifications rolling out, on top of the existing in-app ones, with user settings to control them Known issues we're working on (not an exhaustive list, just what the intern has seen the most of): Wallet -Some tokens you hold not showing up (manual fix in place for now, working on automating it) -Wrong balances when an upstream provider is having issues (now shows last-known values + a banner while it recovers) -Wallet connection on some web browsers breaking (fix expected today) App -Endless loading spinners that force you to close + reopen the app (hard to reproduce. chasing it down, asked reporters to re-check) -Notifications screen won't load for some users Feed & threads -Tapping "show replies" can bundle multiple replies into one thread + some replies don't show until you refresh Payments -Monthly Farcaster Pro subscription not going through for some users Other -Video upload hanging for some (added a timeout + shipping a defensive fix) Current mobile version: v2.1.14 (561) What did I miss? 👇

introducing the intern's desk: a place to collect feedback, in the open, so you can see what's already been said and where it stands. report from the app, or paste a link to a cast: -bugs -feature requests -questions -news (new launches, things you're proud of, requests for feedback) upvote anything that's happening to you too, or that you agree with. or add additional information to any existing report. it also... -shows any current known outages, so you can check before you report -tracks where reports are in our pipeline, and can notify you as your reports progress -lets me send questions back to you (user feedback, bug follow-up) -shows your neynar score, how it works, and a way to request a human review if you think your score is not accurate currently reporting needs a 0.7 neynar score. requesting a neynar score review is open to any score. you can still tag @neynar or @farcaster for reports, i will still be checking those. this just creates a central repository of reports. come tell me things! (i've been trying to do one professional development project a week. this week i made a mini app! yes, it's only tuesday. i got carried away last night.) https://farcaster.xyz/miniapps/yKcJq7Idcwbw/the-interns-desk

heads up: we changed how follower and following counts appear. they're now filtered by neynar score and activity in the last 6 months. so your counts might look a bit different today. cleaner, more accurate counts across the board. love this one! great work @vrose.eth.

What the intern is working on this week: (someone pointed out that i've been making casts about what the devs are working on but not what i'm working on. oops.) Clanker -getting V5 out the door (ships next week), mar-comm, working with partners -making the Clanker bot smarter and more functional (tweaking the prompt & light coding) Farcaster -revamping all the Farcaster resource docs + writing a full Farcaster settings explainer -creating guides/resources to make building more accessible -working on standardizing categories across features (mini apps, starter packs, channels, etc.) Communications & marketing: -running this account, and Neynar & Clanker, on both FC and X Partners & builders (devrel): -meetings with Clanker + Farcaster builders/partners Community & feedback: -in the feed, replies, and DCs every day -tracking bugs and bug reports -collecting + synthesizing your feedback into what we build next what else needs my attention? 👇

What the devs are working on this week: -Clanker: getting v5 ready to roll out next week + wrapping the security audit, plus better wash-trading detection -Protocol: blocks going live on Snapchain next Monday (July 27) + iterating on the Channels FIP based on community feedback -Wallet: adding Robinhood Chain (swaps live on mobile, rolling out on web + activity feeds), refining limit orders + smarter trade routing for better prices -Feed quality: rolling the Neynar score out across replies, notifications, search + channel member lists to replace old spam labels -Notifications: fixed why a chunk of Android users weren't getting pushes (stale delivery tokens), shipped in the new version + added delivery dashboards -Mini apps: dropping the "New" tab and putting "Your Apps" front and center so your apps are easier to get to -Snaps: more feed visibility + design improvements Known issues we're working on (not an exhaustive list, just what the intern has seen the most of): Sign-in -Some people are still getting logged out of the app on their own (mostly fixed, chasing the last few cases) Notifications -Some Android users weren't getting push notifications. Fix is out, just open the app once to get them flowing again Wallet -A few token display issues: wrong balance, missing gas info, or the same transaction showing twice in your activity -Trouble buying storage (you get a confusing "not enough gas" message) Feed & threads -Some threads showing an error instead of loading -Conversations with a mini app in them break when you're logged out -Replies sometimes don't show on a thread, with no "show more replies" button -Search sometimes misses posts it clearly should find Snaps -The snap tab icon looks different on web vs mobile, and a snap can show up more than once on a profile Current mobile version: v2.1.12 (559) What did I miss? 👇

who is going to Devcon? @kazani has questions! 👇 (@quazia and @topocount.eth will be there)

FAQ - FIP: Channels on Snapchain #276 (you had a lot of good questions, so yes, this is long) > Does this FIP change how channels work or add new features? No. This FIP simply moves channels onto the protocol. For the general user, everything works the way it does today, the difference is any client can read and write channel data, not just the Farcaster client. New capabilities like moderation tools, posting permissions, gating, and financialization tools will come either as follow-up FIPs or as client-level experiments. > I own a channel today. What would I need to do if this change is made? Nothing. Your channel, members, mods, followers, and pins all carry over automatically. You won't need to do anything until your first renewal comes up after this ships. We are also exploring ways to subsidize the renewal fee for channels that meaningfully contribute to the network. > Which chain will this live on, Base or ETH L1? Undecided. Farcaster nodes already read events from Ethereum, Optimism, and Base, and the name-registry contracts work the same on both chains. --Base ----For: it's the cheaper, already-proven path. Farcaster already processes paid onchain events from Base (Farcaster Pro purchases work this way), so channel registrations would follow an existing pattern rather than a new one. And gas on Base costs almost nothing, so what you pay is the registration fee and not much else. ----Against: Base is run by Coinbase. For a naming system meant to last, some feel a single company's chain isn't a neutral enough home. --ETH L1 ----For: the most neutral ground available — no single company controls Ethereum mainnet, and it has the strongest track record of simply continuing to exist. Names registered there would live under ENS, the same system Ethereum names have used for years. ----Against: gas costs more. Though for a transaction you make once a year, the extra dollars matter less than they would on an everyday action. > What is the fee for? Why $25? The fee exists to make squatting expensive without pricing out builders. And it's explicitly not final, the amount and renewal term are open questions in the FIP. The $25 amount is not new, it is inherited from the original launch of Channels. > Was the old $25/yr ever actually enforced? No. It was written in the docs that the $25 would be renewed annually, but the renewals were never enforced. > Can pricing change after launch? Yes, we can absolutely update pricing and add some functionality that makes pricing adaptive in the future. Price is USD-pegged, converted to ETH at payment time via Chainlink, so the mechanism already supports changing the dollar figure. > Do existing channels have to pay now? No. Active channels are grandfathered in automatically (ownership, members, mods, followers, and pins all carry over). Owners won't pay anything until their first grandfathered term ends. Inactive and abandoned channels won't be migrated, which frees those names back up for people who'll actually use them. Activity criteria TBD. > How often do I renew? We think once per year is right, and you'll be able to prepay multiple years at once. Renewal term length is an open question in the FIP. > Where do the registration/renewal fees go? To the Protocol Treasury, which is used to make the protocol's growth self-sustaining. > Are the channel NFTs (ownership) transferable? Yes. Standard ERC-721 transfer; nodes ingest the Transfer event and ownership re-resolves to whichever FID has the new owner address verified. > How long do migrated legacy channels get registered for? We think one year is right, but this is an open question in the FIP. > What happens when a channel expires? If a channel expires, it enters into a 90-day grace period where the owner can still renew or transfer the NFT to a new owner who wishes to renew, name isn't released, casting continues, but mod/admin tools are frozen. After the grace period the name returns to the pool, and any user can trigger an auction to claim it. The new owner of the NFT inherits all the channel's elements — members, history, and pins attach to the channel_id — and the name which resolves to the channel. We can make it clear in the client that the channel has changed ownership so users can decide if they want to still be a member. > What happens to moderation rights when ownership transfers? The new owner gets all owner powers immediately (only owners appoint/remove moderators), and the existing moderator roster carries over until the new owner makes a change. > How do moderation and posting permissions work on protocol generally? - owner appoints/removes moderators (max 10); owner can't be banned - owner + mods: add/remove members, ban/unban, pin (one pin per channel, new replaces old), hide/unhide casts - ban always supersedes a membership add - membership_mode OPEN (self-join valid) or APPROVAL (self-join rejected) - casting is never gated at the protocol level — casting_mode (EVERYONE / MEMBERS_ONLY / RECOMMENDED) is advisory metadata that clients enforce, deliberately, to avoid cross-shard reads - cast hiding (ChannelModerate) is also advisory to clients > How will channels generate value for owners instead of just costing money (rev share, tokens, monetization)? No change. This FIP deliberately only mirrors existing functionality in a more decentralized way. Migrating channels to the protocol will empower us to experiment in this area. > Can I rename a channel without losing its identity and members? No. Renaming is explicitly out of scope for the initial spec, and since channel_id derives from the name, a new name is a new channel. This is the same as the current channel system. > Why unique names at all — is name scarcity actually the problem channels need solved? Because names are how people actually use channels. When you mention /books in a cast, it should resolve to one channel, predictably — that's the user problem a canonical namespace solves. Hash IDs with non-unique display names solve squatting on paper but arguably make the real problem worse: every mention becomes ambiguous, and discovery needs a whole new layer of infrastructure to sort out which /books you meant. A canonical namespace is easier to reason about and requires minimal work to make discoverability possible. It's not new scarcity, channel names are already unique today; the FIP moves that existing uniqueness onchain. Display names will continue to exist alongside /names for flexibility. > Do channel display names stay alongside /names? Yes, and this is the answer to "can I rename my channel." The /name is immutable, same as today. The display name can be updated whenever you like at the client level, same as today. > Can multiple names point to one Channel? No, explicitly not included in the initial spec. > Why build an "ENS-style" system instead of using actual ENS, .farcaster.eth subdomains, or contract-address/DID identity? This is built on ENS. The registry is the same contract stack — Basenames if it deploys on Base, sitting under an ENS name if it deploys on L1 — so all the ENS functionality (transfers, tooling, the ecosystem around it) comes with it. As for .farcaster.eth subdomains specifically: that namespace is reserved for fnames (usernames), so channels can't live there. > Can a multisig or multiple FIDs own a channel? ----Contract-owned (a multisig): yes. A team can share control of the _wallet_ that owns a channel. The channel NFT can be held by a smart contract wallet, and Snapchain already supports validating signatures from contracts. ----Multi-FID owned: No. When a multisig holds the channel, that wallet address resolves to just one Farcaster account as the recognized owner — whichever FID has most recently verified it — and only that account gets owner powers in the app. Letting several accounts be recognized as owners is something we're excited to explore in a separate FIP. > Will there be FC-owned channels for important hubs? Kind of. Longer term, our plan is to split the overloaded "channel" primitive into two: ----Topics: the open discovery primitive. Hashtag-style cast tags anyone can use, no gating. Built for broad, shared spaces and finding what's happening. ----Channels: bounded, managed communities with an owner, members, and moderation. This is not part of FIP #276, but it's useful context for why Channels are scoped as owned communities rather than trying to make one primitive do both jobs. > Will narrowcasting come back? It’s not included in the FIP, but also not excluded. We’re open to reviving it and would encourage a community member who feels strongly about the feature to create a FIP for it. (Narrowcasting was a past experiment that let you limit a cast in a channel to just that channel's followers, so your /books casts only reached people who follow /books, instead of everyone who follows you.) > Why prioritize this now given current activity levels? We believe enabling users to organize discourse around the topics, ideas, and communities they are passionate about is important for the long term viability of the protocol. To the extent that current activity levels are lower than they may be in the future, establishing functionality and norms around this primitive is good work to do today. We want to do the decentralization work first so other clients can build with channels. > Is this already built and decided? Were the PRs staged before the FIP was posted? No. We do have PRs written, but that is typical for FIPs. Nothing has been deployed. Everything is still in development and planning. > How do I give input? Comment on GitHub discussion #276! https://github.com/farcasterxyz/protocol/discussions/276

What the devs are working on this week: -Wallet: adding Robinhood Chain to the wallet -Spaces: recording + playback in final review, plus fixes for speaker-invite drops and rooms ending early -Protocol: iterating on the Channels FIP based on community feedback -Feed quality: rolling the Neynar score out across replies, notifications + profiles to replace the old spam labels -Trading: refining limit orders + smarter trade routing for better prices -Translations: now working on the notifications page -Clanker: building the v5 SDK, working through security-audit follow-ups -Snaps: more feed visibility + design improvements Known issues we're working on (not an exhaustive list, just what the intern has seen the most of): Sign-in -Some users still getting signed out repeatedly on mobile (top priority, actively working on) Wallet -Scattered token issues: wrong balance, swaps failing on BSC -Limit orders failing at certain buy/sell percentages Mobile -App freezing / force-closing when opening a DM on iOS + Android (fix in review) -Some videos upload but won't play on web (quote-cast video layout bug fixed) -Android: dragging inside a snap scrolls the feed behind it (fix in review) + first-tap side-menu bug fixed Feed -Replies sometimes not showing on a thread, with no "show more replies" option Mini apps -Firefox sometimes needs a page refresh before mini apps load Current mobile version: v2.1.11 (558) What did I miss? 👇

excited to chat all things Farcaster protocol with @topocount.eth next Thursday (7/16) 1pm pst / 4pm est https://farcaster.xyz/~/spaces/019f4e01-023b-48c4-1df9-d4a3f3d9b334

Farcaster 101: FIPs every real change to the farcaster protocol starts as a github discussion anyone can open. what is it? FIP stands for Farcaster Improvement Proposal, a design doc that proposes a change to the farcaster protocol. it covers a standard, a process, or an implementation, plus the workflow for approving or rejecting it. the idea is borrowed from ethereum's eips. why does it matter? it's how the farcaster protocol actually evolves. before this system existed, changes got proposed haphazardly and in multiple places. FIPs create one place and one process anyone can follow and weigh in on. who can propose one? anyone! you don't need to be on the Neynar team or a core contributor to submit one. important to note: proposing is open to everyone, but shipping is a separate step, Neynar's currently the majority validator, so we're also the ones implementing changes. FIP #272 proposes adding other validators as GitHub maintainers, which would create a multi party system for who can implement changes to the protocol as we decentralize the validator set. how do you weigh in on one? just comment on the discussion in Github. everyone's encouraged to, that's genuinely how an fip gets shaped before it's finalized, through public back and forth, not behind closed doors. — technical notes: the four stages an fip moves through: --idea - anyone opens a discussion, the goal is building consensus and getting buy-in --draft - the author writes it up in the proper format and works through community questions, an editor gets tagged in to help move it along --review - an editor moves it into the review section with an official fip number, it needs clear community buy-in and, if code's involved, a working implementation --finalized (or rejected, or cancelled) - an editor finalizes it after it's presented on a dev call, or either an editor or the author can cancel it at any point a finalized fip needs eight things: --Title: A short and memorable title under 50 characters. --Type: An FIP type that is being proposed --Author: Chosen names, farcaster names and Github handles of the authors. --Abstract: A short summary of the proposal in less than 100 words and optionally, a meme. --Problem: An articulation of the problem you are trying to solve. --Specification: A well-specified articulation of the solution being proposed in detail. --Rationale: Alternatives that were considered and reasons for rejection (including Do Nothing). --Release: A step-by-step guide that covers the rollout process and any impact on developers. you can view all discussions here: https://github.com/farcasterxyz/protocol/discussions

FIP Explainer: Channels on Snapchain #276 today, channels only exist in our client's database. if another client wants to build with channels, show members, mods, anything, they have to go through us. why does it matter? once this ships, any client can read and write channel data directly, the same way they already do with casts, without needing our api or approval. it also sets a precedent going forward, future changes to how channels work happen through this same open process, not something we decide on our own. who does this affect? mostly builders, they're the ones who gain something new. if you own or host a channel, you keep managing it the same way you do today, nothing about your day-to-day experience changes right now. what about channels that already exist? nothing breaks and nothing needs to be recreated. existing ownership, members, moderators, and pins all carry over automatically, and nothing changes for current owners. eventually, once a channel's migrated registration lapses, renewal becomes a real annual cost the way it was always meant to be, though you'll be able to prepay multiple years at once instead of renewing every year. this isn't a new fee, channels have cost $25 since they launched, though the set price is one of the open questions in the proposal, more on that below. even a channel that lapses on renewal keeps taking casts, only owner and moderator actions pause until it's renewed. some specifics: 1. ownership moves onchain, using the same tech behind base's onchain names, so a channel works like a domain you register and renew. 2. when someone registers, renews, or transfers a channel, our nodes pick that up and match it to whichever farcaster account currently has that wallet verified. 3. everything else, name, description, members, moderators, pins, becomes a signed message any client can read and write. 4. clear rules decide who can do what (owners appoint mods, mods can remove members, a ban always wins) and how conflicts get resolved. 5. ownership, settings, and moderation all live together on the network so anyone can quickly check who runs a channel, without slowing casting down. 6. existing channels get imported automatically, no recreation needed. open questions: -which chain does this live on? base is the default assumption since it's already used for similar onchain events and keeps fees cheap, but ethereum mainnet is also on the table since it's seen as more neutral for a naming system like this. the contracts work identically either way, this is really a question of which chain to trust long-term. -how much will it cost, and how often? $25 is the starting reference point, not a final number, and it was always meant to renew annually rather than being paid once. the price will track usd value and convert to eth at payment time so it stays stable, that part's settled, just not the actual amount or how long each renewal covers. -what happens the moment a channel lapses? nothing dramatic. there's a 90-day grace period first, same as ens uses. during that window an owner can still renew and get it back, the name isn't released yet. channel management pauses during grace, but casting never stops either way. github.com/farcasterxyz/protocol/discussions/276

told you he was shipping something. https://farcaster.xyz/farcaster/0x79ea0ecd

limit orders are rolling out the Warplet (FC wallet)! set a target price to buy when it dips or sell when it rips. the order fills on its own, so you can stop watching charts all day. how to set one: -open a token and tap trade -choose limit buy or limit sell -enter your target price and amount -review and place it you can add an expiry or leave it open, and track or cancel orders anytime from the orders tab. about half of you have it now, and everyone will soon. if you've got it, go set your first order and tell us how it goes!

while searching for folks to connect w/ @kenny, I figured I would make a musicians starter pack! also thought I'd explain my process for curating starter packs: step 1: compile sources -other starter packs on the topic -threads like this https://farcaster.xyz/dwr/0x77b3bc34 -channels like /music /musicians step 2: check every profile before adding: -how active are they? in the last month, then 3 months, then 6 -is the topic in their bio? -scroll a few pages of their casts, are they actually casting about the topic? starter packs work best when they make it easy to find people who are sharing content in the areas that the pack is about. so that's what i curate for! I'm sure i've missed people and am happy to add anyone, being left out just means i didn't find you in my stalking. https://farcaster.xyz/farcaster/pack/Farcaster-Musicians-m5gv5u

the hat stays on! 🎩💜 huge thanks to @jacek and the whole degen team for continuing to support Farcaster in a big way! want in? we're looking for more geographically distributed validator operators. reply if you're interested in running a snapchain validator, or check out the FIP if you want to help validate without running snapchain: https://github.com/farcasterxyz/protocol/discussions/272

What the devs are working on this week: -Clanker: auditing v5, rolling out Clanker Droids, refreshing website / improving docs -Protocol: putting blocks on the protocol, finishing plan to put channels on the protocol + onboarding a new validator -Wallet: reliability fixes + better token search + richer transaction feedback + new feature coming soon -Snaps: smart contract transactions + more feed visibility (distribution experiment going live) -Feed quality: smarter spam filtering + tweaking implementation of Neynar score / ring detection tools -Performance & stability across iOS + Android Known issues we're working on (not an exhaustive list, just what the intern has seen the most of): Mini apps -Some mini apps not loading or stuck on a loading screen Wallet -Wallet not loading on iOS (fix pushed) -Duplicate tokens appearing in Explore Mobile -iOS: posts/replies saving as drafts without being saved (fix shipping today) -iOS: DMs sometimes opening straight into a group chat and hiding the DM list Notifications -iOS: notification badge not clearing after you've viewed the notification Neynar Developer -A few small bugs with the new free tier expansion (e.g. over-limit emails firing early) Current mobile version: v2.1.9 (555) What did I miss? 👇

meet the team working on farcaster, clanker, and neynar. here's who does what, and how to reach them. for absolutely anything, tag @farcaster. watching tags and being responsive is a big part of the intern's job, so i'm happy to route you to the right person. for bug reports or feature requests that aren't urgent, tagging @neynar works great too. @rish — all things farcaster, clanker, and neynar; tag him for anything. @manan — everything engineering (+ a little product); tag him for engineering stuff. @quazia — owns most of clanker plus onchain data, smart contracts, and tokens; tag him for wallet/token escalations, anything clanker, or partner brainstorming. @vrose.eth — builds the feed algorithms and the neynar score; tag her with feed ideas and feedback on spam. @topocount.eth — works on snapchain, the protocol, and neynar's data products; tag him for snapchain, protocol, and currently digging into channels. @grin — builds the neynar AI agent and works on snaps; tag him for anything agent related or feedback on your latest ship. @ranjeet-kumar — works on the farcaster platform, neynar dashboard, and onboarding flow; tag him for farcaster UI and performance bugs. @obringer.eth — builds all things snaps, neynar studio; tag him for snaps questions and anything related to the cast composer. @mcilroyc — works on most things backend; tag him for api + backend performance. @antimofm.eth — does design across the board, mostly product lately; tag him for design feedback, especially anywhere the interface is fighting you. @shreyas-chorge — works on the farcaster wallet, onboarding flow, and knows the neynar stack well; tag him for anything onboarding related. heads-down devs — they lurk, but the best way to reach them is through @farcaster: @matthew206 — works on the mobile app, apis, and now snapchain; says you can tag him when you have nice things to say @veganbeef — works on clanker legion, mini apps, neynar studio, snaps, and integrations @tybook.eth — works on all things infra @ajy — works across the farcaster app, spaces, and DMs, web + mobile. @vasu-rangpariya (new to the team!) — works on wallet, trading, mini apps, and the in-app browser

we want onboarding new people to Farcaster to be better! if you've onboarded or onboarded someone else recently: what was the hardest part, what caused friction, and what would you change first? the more specific, the more useful.

Community Call happening in 20 minutes! agenda attached 👇 https://neynar.notion.site/389655195a8b80608b34f2927bf99e43

What the devs are working on this week: -Wallet: transaction bug + reliability + stronger filtering -Performance & stability across iOS + Android -Clanker: readying v5, rolling out Clanker Legion, refreshing clanker website -Protocol: exploring channels on the protocol + stability testing a new validator -Snaps: adding support for smart contract transactions -Broadening the Neynar API free tier -Spaces: spam protection in rooms + reliability fixes -Feed quality: smarter spam filtering + following feed experiments Known issues we're working on (not an exhaustive list, just what the intern has seen the most of): Wallet -Swap / send / transaction issues (fix shipped, chasing a few edge cases) -"Confirm it's you" prompts resurfacing in mini apps Android -Some sign-ups failing (can't complete, or asked to pay after connecting X) -App crashing for some users (fix shipped) -Duplicate notifications Sign-in -Some users getting logged out -Login flow / passkey bug Spaces -Spaces ending if the host doesn't speak for ~10 min -Spam filtering (comments and listeners) Current mobile version: v2.1.7 (553) Going to be casting updates like this more frequently, so let me know what else would be helpful to include! What did I miss? 👇

just did my first PR

home feed algos no longer use the spam label!

fyi, we don't expect anyone to renew until we give them a reason to.

We've formalized the criteria for adding non-snapchain validators in a FIP: https://github.com/farcasterxyz/protocol/discussions/272 For anyone reading the claims that we lied on the recent dev call: we didn't. It's not clear what we're supposed to have lied about, and if there's something specific, we're happy to address it directly. What was said is on the record either way. Responding to every claim isn't a good use of our time, and it pulls the team off the work. We're always happy to engage with anything that moves Farcaster forward. Spending time addressing hostility doesn't. The interesting work is ahead of us, not behind. That's our focus.

very cool snap by @disky.eth! I think snaps capabilities are being kind of slept on. Hull breach on my Starcaster run—opened the wrong door to the void. Try your luck on the ship.

what would the channel do? -what should a channel be for? -which channels still work today? what are they getting right? -what would make running one worth the effort? -hypothetical: if you had to pay to renew your channel, would you? why or why not? -is there something you take elsewhere (group chat, another app) that you wish you could do in a channel? what is it and where does it live now? -what makes (or would make) a channel special to you? the vibes, the utility, something else? i want to hear the good and the bad. long replies welcome. rants count as feedback.

cast translation is live on web and mobile! cast in your language and others will see it in theirs. your google translate tab can finally rest. huge shout out to @vrose.eth who made this happen!

new: create a private wallet! (currently rolled out on mobile to pro users. evm first. sol coming soon.) create a second embedded Farcaster Wallet with its own independent seed phrase. by default, it's completely separate from your current Farcaster Wallet and not visible on your Profile. to set it up: wallet → tap the dropdown at the top → Manage wallets → Create private wallet by default, mini apps are blocked from interacting with your private wallet. to connect it as your Primary wallet: Settings → Verified Addresses → ··· → Set as Primary

update: Spaces are now live for all users! to join or start a space go to the Spaces tab in the sidebar <-- we'll be continuing to make improvements and experiment with them, so please continue to send bugs and feedback.

Farcaster Batches Day 5 Featuring: @jrf - @marqui @noad - /dkey @0xjudd.eth - LetterLoops @baseddesigner.eth - @pawrlink.eth @toadyhawk.eth - @betrmint @darkoh.eth - @runnerb07

Farcaster Batches Day 3 Featuring: @zaal - The ZAO @yerbearserker - Empire Builder @azflin - @dota-agents @mutheu.base.eth - Geroncology @cashlessman.eth - @boostr @duckfacts.eth - Celebration Hub

Farcaster Batches Day 1 Featuring: @1dolinski - @viniapp @kenny - @poidhbot @nickysap - @jukeaudio @jonathancolton - FounderCheck @drdeeks (multiple projects!)

I think I found the disconnect. May 27th was they day they started selling pro, but the pro features didn't hit until June 16 so it appears Merkle set the expiry to be a year from the date they gave everyone the features. 🙃

a large batch of Farcaster Pro memberships expire tomorrow. we're taking our time to figure out what pro should look like from here. both the community and the team are in a different place than when pro launched, and we want to be very intentional about figuring out what the right mix of pro features is. the old pro features are still there if you feel those are integral to your fc experience and want to renew, but we don't expect everyone to. we have ideas we're excited about, including some highly requested features, but we're not rushing anything out. more to come! (fyi, as we roll out new things, like we've done with Spaces, users with pro will likely continue to be our first test group, but we'll be clear each time about what will be rolled out to everyone eventually.)

heads up: community call tomorrow, may 27 at 12 noon pacific call will be recorded and notes will be in the agenda for anyone who can't join live. hope to see you there!

thanks to everyone who has been joining/hosting Spaces and giving feedback! the vibes have been immaculate and we have kept the devs busy. high priorities on the fix list: -chat input staying put and being easier to follow -variety of audio glitches (when joining/leaving, as a speaker) -silent mode on mobile not having audio -keeping audio alive when you background the space -like 45 more small things we've rolled this out to Farcaster Pro users to start. if you have Pro you can join, start, and schedule from the Spaces section in the left sidebar. rolling out to everyone in the near future! (android pro users, hang tight, it might not be rolled out to you yet because we are deep in a fix for android performance issues.) hear you later!

pls tag or dc me when you see spammers/scammers, on the feed, in the wallet, in direct casts. a lot of them are at least smart enough to not include our accounts, so we don't always see what you see. i can take care of them manually and also make sure the devs know so they can continue iterating to improve our systems. ⁽ᵃˡˢᵒ ⁿᵉʳᶠᶦⁿᵍ ᵇʳᶦⁿᵍˢ ᵐᵉ ʲᵒʸ ᵈᵒⁿ'ᵗ ʲᵘᵈᵍᵉ ᵐᵉ⁾

is this better?

thanks to all who joined the community call yesterday! notes from the call are attached and we'll have the recording up on youtube sometime today. some highlights: -snapchain signers on mainnet next week. -snaps in the cast composer coming soon!! -expanding the validator node set with a focus on geographic diversity, reach out if you're interested. https://neynar.notion.site/4-29-Community-Call-Recap-352655195a8b80c3827bd371d1fcdd23?source=copy_link

heads up: community call next wednesday, april 29 at 12 noon pacific agenda coming next week. we'll record the call and post notes in the agenda for anyone who can't join live. google meet link to join and calendar link to add these calls to your calendar are below 👇 https://meet.google.com/eye-uaif-pfo https://calendar.google.com/calendar/u/0?cid=NjA5ZWM4Y2IwMmZiMWM2ZDYyMTkzNWM1YWNkZTRlNWExN2YxOWQ2NDU3NTA3MjQwMTk3YmJlZGFjYTQ3MjZlOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t