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.

farcaster.id

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

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.

Ideally, we would move to farcaster URIs, something that starts with farcaster:// but there are various complexities to this.

And it also depends on a backend. Backends need constant maintenance, which means that if it goes down, it costs too much to maintain, there is a bug, etc, every service depending on it, will stop working. No reason to have this dependancy.