Content
@
0 reply
20 recasts
20 reactions
Samuel ツ
@samuellhuber.eth
Very misleading to be a FIP. The Farcaster protocol as laid out in its specification is NOT recieving a direct message system with this update. The Warpcast Direct messaging system will be further opened beyond existing APIs To me that’s great for programmability but NOT a protocol feature! A feature built on top of the protocol sure but not protocol level Though as Frames also are a client level, non protocol feature I get why it may be an FIP Though I already see posts from people saying DCs will be at protocol level because of the FIP label. TLDR: very very excited about DCs opening up, though as always I prefer more precise language 😂 Why DCs matter? Darn it just look at telegram bot markets, they are HUGE! Great for devs, great for AI/programmable workflows!
9 replies
16 recasts
65 reactions
Samuel ツ
@samuellhuber.eth
Cc @meb DC agents coming to Gladio then?
1 reply
0 recast
6 reactions
Samuel ツ
@samuellhuber.eth
Yes DCs won’t be on your Hub. Frames also aren’t on your hub. That’s why I understand the FIP. Though people likely will misunderstand. Will it be at hubs eventually for DCs. Yes. I believe that to eventually happen.
0 reply
0 recast
3 reactions
Matthew Fox 🌐
@matthewfox
Sorry brother you did this to yourself
1 reply
2 recasts
9 reactions
Varun Srinivasan
@v
Why shouldn’t it be an FIP? Fnames aren’t on hubs, and neither are fids or keys. Yet they’re all changed as part of the fip process.
1 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
I've seen this argument a few times, but I don't agree. Farcaster is not just the hubs, it's everything that defines how things work or are expected to work on Farcaster. FIPs should document anything that standardizes building on Farcaster. Similar to how ERCs do not change how the Ethereum blockchain works, but they are extremely important.
1 reply
0 recast
0 reaction
Rafi
@rafi
@statuette direct casts API could time well with AI agent workshop 👀
1 reply
0 recast
1 reaction
Rafi
@rafi
I also get confused with use of farcaster.xyz for API and use of 'protocol' word while referring to API
0 reply
0 recast
0 reaction
0xbhaisaab
@0xbhaisaab
@pratzyy.eth
0 reply
0 recast
0 reaction
resplendent
@resplendent.eth
Excellent !!
0 reply
0 recast
0 reaction
L3MBDA
@l3mbda
your call for more precise language is spot on
0 reply
0 recast
0 reaction
valse
@0xvalse
Totally agree! DCs are a game-changer for programmability, but not a protocol feature. Labeling matters to avoid confusion. That said, opening DCs is huge—just look at Telegram bot markets. Excited to see how devs leverage this for AI and automation!
0 reply
0 recast
0 reaction
