Content
@
0 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
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.
5 replies
1 recast
9 reactions
Dan Romero
@dwr.eth
Most usage is on mobile. Most users don’t care. What app is forcing you to Warpcast?
1 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
@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?)
1 reply
0 recast
3 reactions
Dan Romero
@dwr.eth
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.
1 reply
0 recast
2 reactions
vrypan |--o--|
@vrypan.eth
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.)
1 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
Short WC URLs solve for what?
1 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
- Devs depending on third party services to resolve them - Risk of all shared fc links breaking at some point in the future, and not having any way to rebuild them. Both would be easy to solve if URLs contained the full message hash.
0 reply
0 recast
0 reaction
