A place for developers to talk about building on Farcaster.

/dev

A sufficiently decentralized social network. farcaster.xyz

@farcaster network architecture, correct me if I am wrong please. Hubs use gossipsub, which means one cannot run a hub on a mobile phone without burning their data plan. There is a gRPC interface defined on hubs, so one could run a client using said API...

Building @waku at Logos.co / free.technology

a) gather metadata beyond what is available on the fc network: what channels the user spend most time on, what casts the user pay more attention too etc....

b) manipule the user's timeline: shadow ban, push sponsored content, etc

c) Simply ban a user from using the app..

I wonder among these drawbacks, which ones are accepted and which ones are to be resolved?

Good read to help answer my questions: https://www.varunsrinivasan.com/2022/01/11/sufficient-decentralization-for-social-networks

... yet no peer discovery is available so developers need to hardcode the URL of the endpoint (hub) to use.
FC is "sufficiently" decentralized so a number of drawbacks are expected and accepted. With such a centralised model for mobile clients, it enable app devs to:...

building degencast.wtf /degencast, ex-synfutures, binance, bitmain

Chiang Mai, Mueang Chiang Mai District, Chiang Mai, Thailand

Hum, yes clients are always centralised. I am just not fond of the BE that proxy access to the public permissionless network.

clients are always centralised unless we adopted arweave's new fancy 'deployment by forking' workflow. I think if any client behave evil, it should be painless to use alternative clients