if it were up to me it would be a top priority to make this an international community. I don't want warpcast to remain "English speaking" at its core.

This a great opportunity for another client.

Warpcast is a US-based team. No plans to expand internationally. We think we can build a great client for English speaking users. Don't have enough bandwidth to do a good job for international users. 

I know @phaverapp @fireflyapp have large communities of international users. Also @supercast.

(I ran international expansion for Coinbase for several years and learned that the hard way.)

Everything app for Web3 natives, founders, marketers, and influencers by Mask Network. Support → https://t.me/+mz9T_4YOYhoyYmYx

https://supercast.xyz — have fun on farcaster

The largest multiprotocol web3 social app 📲

With cross-posting to both Farcaster and Lens 🟣🌿 https://phaver.app.link/phaver

This a great opportunity for another client.

Warpcast is a US-based team. No plans to expand internationally. We think we can build a great client for English speaking users. Don't have enough bandwidth to do a good job for international users. 

I know @phaverapp @fireflyapp have large communities of international users. Also @super.

(I ran international expansion for Coinbase for several years and learned that the hard way.)

Would you consider supporting i18n at the protocol level?

Maybe have a value in casts to indicate language (set by a client), empty value defaults to English. And/or subchannels for language specific discourse. i.e.

/food/jp
/farcaster/es

father, husband, css golfer, ux engineer, silently defining variables as /sdv sdv.wtf

Makes sense! I’m sure they can get there without the protocol changes, and maybe a second international client in the mix could help shape the protocol changes when appropriate

maybe at some point

I'd be convinced if there was another client that had large user base of international users.