shazow
@shazow.eth
I love the premise of /frames and I don't want to poopoo but I can't remember the last time I interacted with a frame and didn't get an error/timeout. :( Relying on rando third party stateful servers is probably a mistake, wish more decentralized frames were viable.
1 reply
0 recast
2 reactions
horsefacts
@horsefacts.eth
I agree it's a bummer. But the whole internet relies on rando third party stateful servers, too. I think (hope) it's a sign of immaturity more than anything.
1 reply
0 recast
0 reaction
shazow
@shazow.eth
Yea but the whole internet is not intended to be ephemeral with misaligned timeline expectations. There's fairly strong permanence expectation (at least multi-year timescale). I feel like most frames are built with the creator's commitment of operating for just a few days, then they move on, but casts stick around.
1 reply
0 recast
2 reactions
shazow
@shazow.eth
Maybe a hot take: At least 1+ year domain registrations anchor commitment to a year of operation. I don't know if this is a good approach (I rather see server-agnostic frames) but could create somekind of registration anchor (maybe a bond with uptime refunds?).
2 replies
0 recast
2 reactions
shazow
@shazow.eth
Btw when I say server-agnostic frames, I mean some way to distribute the code separately from where it gets rendered, so that if the centralized host goes down then other hosts can continue to provide it (like farcaster clients), but state would need to be onchain then rather than serverside.
1 reply
0 recast
3 reactions
horsefacts
@horsefacts.eth
🤯 That would be cool.
1 reply
0 recast
0 reaction