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
59 reactions
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
Samuel ツ
@samuellhuber.eth
The naming here is fucked up as well We use Ethereum Request for Comment (ERC) the same as EIP (Ethereum Improvement Proposal) Though yep both now semantically translate to standardization of Ethereum itself + the ecosystem Which it seems FIPs now are too
0 reply
0 recast
2 reactions
