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.

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

nook.social - track, review, and share your favorite content

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

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

I want my @buoy notifications to open in @nook or @super, and not force me to @warpcast.

@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?)

Most usage is on mobile.

Most users don’t care.

What app is forcing you to Warpcast?

Building @warpcast and @farcaster, new dad, like making food

it’s ok but creates a worse best case UX

from click opens apps

to click opens a browser which loads a page and then the user gets prompted to open in their selected app (sometimes the last prompt isn’t there depending on OS/browser) then the app opens

farcaster.id

cypherpunk wannabe, engineer working on @frames /open-frames /opencast
https://stephancill.co.za create stories at https://stories.steer.fun

It looks like it's not about individual casts. Also it has its own pages, I don;t want this, I want to be automatically redirected to my pref client. And finally, I don't mind the domain, but it has to be something that will eventually be owned by the protocol at some point.