Farcaster Devs

Proposal: 
1. Use farcaster.xyz as the default domain for farcaster URLs
2. Deploy a simple browser app there. Cookie-based prefs will set a redirects to my client of preference.

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

Most usage is on mobile.

Most users don’t care.

What app is forcing you to Warpcast?

Search Engine for Farcaster. Save your search and get realtime alerts for new results. Download for iOS & Android on buoy.club · web beta.buoy.club

@buoy 
I know the argument. My concern is "most users use Warpcast", "most users don't care", "most users are on mobile" becoming a self-fulfilling prophecy. Not leaving space for alternatives (clients, environments, use cases, UX flows).
(BTW, if "most users are on mobile", why do we still have short WC URLs?)

If you put it as a prioritization issue, I agree.

(For the short URLs I don't, I think they are creating a significant debt and dev overhead for no good enough reason.)

The existential issue is getting someone to open up a Farcaster app every day. Not which one. That will change with time, but not there yet.

I think it's higher priority to have protocol-focused resources on Hub stability, decentralizing channels and then DCs.