A place for developers to talk about building on Farcaster.

/dev

Is private messaging in Warpcast independent to the protocol or a farcaster feature?

Use @infinex-app and thank me later - https://app.infinex.xyz?r=9RQ4I9SH

Private messaging based on double/triple ratchet is hard to do without a server that routes messages. You also want to support push notifications, delivery if your phone is offline for awhile etc.

It’s hard to do and retain the privacy properties. My FIP goes into detail on how to provide it in the decentralized context:

Working on building zkTLS infra/products. A ruthless empiricist and meme connoisseur.

/opacity

and

/eulerlagrange

It’s hard to do and retain the privacy properties. My FIP goes into detail on how to provide it in the decentralized context: https://www.github.com/Farcasterxyz/protocol/discussions/99

BDFL of Quilibrium, Eng @ Farcaster, ex-Coinbase, always opinionated, never hydrated

/quilibrium

trade-off — a client requesting notifications for specific conversations would necessarily identify to a backend which conversations it is interested in. A user which cares about privacy could instead have a background notification worker on the app itself to perform these checks and surface notifications in-app

Push notifications are driven from two sources on most platforms: server-side or in-app, sometimes both. It is not unusual for decentralized protocols with many clients to have middleware servers, Farcaster is no different — while hubs hold casts, notifications about them do not originate from hubs. This has a —

@cassie any thoughts on how push notifications could be supported in a world where hubs implement FIP 99?

Any thoughts on waku?
- see answers by @fryorcraken to @v's question below
- How well does it align with the fairly comprehensive FIP?

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

Building @waku at Logos.co / free.technology

Public space ops, App integration facilitator @brightid

Status chat protocols provide those above. They implemented double ratchet over Whisper years ago, including k-anonymity to avoid sender-recipient linkability.

https://specs.status.im/

I’d need to dig into more of the details, but at least from the thread, what was built is impressive. For parity, it would need:
- perfect forward secrecy
- repudiability
- analysis resistance
- out-of-order messaging
- all of these properties in group messaging

Any thoughts on waku?
- see answers by @fryorcraken.eth to @v's question below
- How well does it align with the fairly comprehensive FIP?
https://warpcast.com/v/0x6c0022