Lectern (lectern)

With Lectern, you get a macOS UI, but you also get a CLI that is the backbone of the UI. With Lectern CLI, you can configure your accounts via code to make sure it all lands as you'd expect. You can use this configuration to manage drift across multiple accounts. For builders managing app accounts, this is the unlock. 👈 https://lctrn.app/docs/user-guide

• 0 replies
• 155 recasts
• 161 reactions

Very excited to announce Spaces integration will launch alongside Snaps, Follow Managment, Local Bookmarks, Scheduled Casts, Cast Analytics, and Airdropping features already announced. We have a plan to open source the Lectern CLI for all to fork and enjoy. Understandably, there's a lot to consider, feel free to ask your questions openly, or on XMTP.

• 8 replies
• 50 recasts
• 81 reactions

A glimpse of the Spaces UI. We're working diligently to polish and QA, but we're on schedule. Treasury is $0. $KEYNOTE pool is at ~600M tokens available for distribution. The first Pros will receive a larger first-week $KEYNOTE incentive. Be sure to register as soon as possible on launch to secure your position. Please visit https://lctrn.app/keynote for more details.

• 2 replies
• 3 recasts
• 28 reactions

Thanks @cassie. this needed to be said in public, and the framing matters. Most people don't yet track the gap between "farcaster" and "farcaster legacy" — neynar/merkle still gate the surfaces that didn't make it onto snapchain (dms, channels, signer attribution, wallet onboarding), and the protocol is routinely conflated with their single-vendor stack on top. Your point one — that clients can't meaningfully use snapchain alone — is exactly why Lectern picked hypersnap as our only read+write layer. no indexer, no neynar fees, no telemetry, no app fid tagging users' casts. keys stay in the macos keychain; we sign locally. dms run xmtp v3 + the new snapchain primitive rather than the merkle dc rail. Quorum on mobile + Lectern on desktop + Hypersnap as a validator-eligible snapchain peer is the architecture this protocol needs to actually be a protocol. Hope we can connect and work together 🤝

• 1 reply
• 0 recasts
• 19 reactions