Content
@
0 reply
20 recasts
20 reactions
Kartik
@slokh
I think we need to go back to allow fid + user registration without paying for storage. IMO the identity piece is the most interesting part about FC and that should be as accessible as possible. Most FC-adjacent apps won't actually need the rest of the stuff (casts, reactions, etc) Simplifies it for app backends as well: 1. They can immediately onboard users to FC as their identity system (just pay for gas) 2. Use the protocol without broadcasting messages 3. If the user wants to reach the rest of the network, user/app can pay storage and immediately broadcast those messages The part to figure out is the reason it went away in the first place - spam registrations. This is solvable though.
13 replies
7 recasts
58 reactions
Dan Romero
@dwr.eth
How is a FID useful without data on Hubs?
4 replies
1 recast
7 reactions
Kartik
@slokh
SIWF, apps want to use FC for the identity. It's more complex to maintain app-specific identity + FC identity if you want to onboard users and not pay the storage costs. FC should want increased adoption of the FC identity and eventually translate those into paying customers (storage). Top of my head examples: - create/rsvp on events.xyz - rate/review on nook.social - interact with frames / cast actions, especially as they mature
1 reply
0 recast
9 reactions
boscolo.eth
@boscolo.eth
Why not open it up, allow the experiments to be conducted, and let other smart people give you the answer to this question with code?
1 reply
0 recast
1 reaction
christopher
@christopher
we’re going to find out when people churn their free storage from this winter but still open their apps
0 reply
0 recast
2 reactions
Joseph.🎩🎭
@josewhizzy
SIWF, apps want to use FC for identity, but maintaining multiple identities is complex. FC should promote its identity system to drive adoption, reduce storage costs, and convert users into paying customers through use cases like events, reviews, and frame interactions.
0 reply
0 recast
1 reaction
