Hey all - just wanted to share some of my concerns about the public nature of our casts/behavior on FC.

Hoping for an open dialogue on where we think this is headed, and in the long run, how to provide privacy protections from a user content perspective.

Hey all - just wanted to share some of my concerns about the public nature of our casts/behavior on FC.

Hoping for an open dialogue on where we think this is headed, and in the long run, how to provide privacy protections from a user content perspective.

https://paragraph.xyz/@barrycollier/farcaster-content-graph

perpetual learner • curious builder • art lover | bazvault.eth | barrycollier.com | hosting /baz /givingflowers

Thx for writing and sharing. Really great perspective. I am a bit of a reformed privacy maxi. I ended up giving up what I thought was a losing battle. The rewards and incentives against it were too strong. Is there a world where data can be public but the antibodies for protecting us happen at the UX/client level? 🤔

Cohost /gmfarcaster livestream Farcaster news show 🎙️💬 Founder Tenger Ways, bringing joy into work with DevOps practices 🤗 mom x 3 💗

DMs and private messages aside, what’s the point of encrypting at rest of a public social network though?
I  love the idea of a potential privacy focused client that uses farcaster protocol data (username and social graph) but all messaging happens outside of hubs on proprietary servers with more privacy/security

Ty Adrienne - this is exactly my question

There are some old data stewardship principles that still feel valid to me, one of them being data should be encrypted at rest (eg hub) and decrypted at the client level (eg Warpcast)

When I install a client, I grant what permissions I want to allow to my onchain/onhub data