Varun Srinivasan
@v
What should Farcaster build in 2025?
28 replies
2 recasts
76 reactions
KMac
@kmacb.eth
name spaces
1 reply
0 recast
2 reactions
jd đș
@jdl
say more sailor
1 reply
0 recast
0 reaction
KMac
@kmacb.eth
partitioning an apps data from other apps data at the hub/snapchain
1 reply
0 recast
1 reaction
jd đș
@jdl
and what does this unlock for us? give it to us like weâre eight years old
1 reply
0 recast
0 reaction
KMac
@kmacb.eth
Hmm 8 not 5✠will try Youâre using your crayons & coloring on a piece of paper. Youâre drawing a house with your family by a tree on a sunny day a friends everywhere. Now someone you donât know from halfway around the world starts drawing too. On YOUR paper! They add planes dropping bombs & make the exploration sooo big it covers the entire piece of paper & rekts your picture. Names spaces prevent that by giving you each your own piece of paper to color on.
1 reply
0 recast
1 reaction
jd đș
@jdl
excellent starting point sugar. say more: whatâs possible by placing this at protocol layer that canât be done elsewhere in the stack
1 reply
0 recast
0 reaction
KMac
@kmacb.eth
today this concept is not supported really at any layer in the stack. It's like two kids in a playground. App-A is the older sibling and gets to decide the rules of the game, even though App-B might want to play something totally different. App-B doesnât get to choose how it plays, because it has to follow App-A's rules. Itâs like being told how to play all the time, even if you donât like it. How long before you go play a different game that's more fun to you? Now, think about how cool it would be if every app could have its own set of rules for how things should go. Like, App-A could play one game, and App-B could play a different game, with its own rules that make more sense for what it's doing. If we let every app have its own "playground rules" (or "context"), it would make apps way more flexible and fun.
0 reply
0 recast
0 reaction
