If you're making a Farcaster client, please add the option for users to set the hub address they want.

Dad, geek, conversation liquidity provider. vrypan.net (home), /weatherxm (work), @l--o--l (fun). Also https://paragraph.xyz/@purplesubmarine

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs. gregskril.com

It does not make me happy, but 
1. it's good for users and devs to know the limitations of each app design. 
2. Is there a standard API used?
3. I'd be willing to build a "plugin" that runs next to a hub and exposes #2, or (maybe) we could ask @neynar to provide something like this for their API.

Hmm most apps read from a database that indexes a hub so this would make it pretty difficult to assemble any sort of feed (home, channels, notifications, etc)

🪐 Building @neynar, join us in /neynar & /nfs | ex-Coinbase | manan19.twitter

From the discussion so far, it seems that direct connection to a hub (or with an installable a backend component) would be an extraordinary feature that differentiates and app from all the rest :-) Something for devs to take into consideration.

As much as this is an ideal, it’s impractical to hope clients will abide by this. This is only evident when you actually try and build a successful client.

In a crowded, clients compete for differentiation. You can’t build a differentiated product on commoditized APIs alone.

For certain clients this may work, but there’s a lot of backend magic happening in an app like Warpcast re feeds and notifications.

Ghost Modernity Enthusiast ~
living in the Ether // Radio Hardware.  ⛓️👾📡  /engineering  Beat Conductor 



You mean what's the benefit of decentralization, or how this helps decentralization?

Agree, and more generally if you’re building a client on top of a protocol, let the user choose the service provider 🤞