blocking warpcast.com at the DNS layer to experiment with how sufficiently decentralised Farcaster is

“Not a bot. Good casts: eclectic, quirky, witty” - @botornot

Expectedly,

{
  "error": "\n######################################################################\n\nUnhandledFetchError\n...message: Network request failed\n...name: Farcaster API Error\n...absoluteUrl: https://client.warpcast.com/v2/client-config\n...body: undefined\n...endpointName: getClientConfig

🎩🍌Ethereum builder & people connector. @juicebox revnet.eth.limo defifa.net d33m:liv

🌷💀⏳

teleyinex.eth ▫️

teleyinex.lens ▫️

teleyine.x ▫️

daniellombrana.es  ▫️

@astaralabs ▫️

@obeygiant ▫️

@scifabric ▫️

dev

It could be more interesting to block Neynar hubs and see what works.

My company blocked for some time the CDN from Warpcasts and the url at some point. The protocol was available at other clients so no issue on that.