Content
@
https://warpcast.com/~/channel/fc-updates
0 reply
0 recast
0 reaction
Varun Srinivasan
@v
FIP: Direct Casts A proposal to make Warpcast's Direct Casts an open standard that any Farcaster client can use. https://github.com/farcasterxyz/protocol/discussions/226
6 replies
17 recasts
151 reactions
KMacš ā©
@kmacb.eth
This is a bad idea to take on right now. Would shelf this entire idea in favor of other priorities. Full stop. But wait thereās more. Who is āFarcasterā that is operating the server? gc & smh all at the same time. Protocols are rules not organizations. Conflating these leads one to think like a business instead of a headless public good. More gatekeepingā½ really Keep it as wc direct and group casts. Open that if you want but keep it out of Farcaster protocol if itās not on a node, permissionless & independently verifiable. An idea- Work on creating more flexible app specific context-containers that are ai ready.
1 reply
0 recast
12 reactions
Andrei O.
@andrei0x309
Gatekeeping is maximal because if you didn't check there's a whitelist like we are used to, so it's much worse than a centralized server, as per usual devs will need to request permission from the team not even in an automated way. I mean I am just astonished by the lack of foresight, imagine if you want to get permission to read/send DMs on Twitter, Threads, etc is easier. You can literally make an app in 5 minutes that has those permissions, how blind you must be to understand that writing such poor proposals is a complete disaster from an optics perspective.
1 reply
0 recast
1 reaction
KMacš ā©
@kmacb.eth
Devs gonna dev š¤·š»āāļø
1 reply
0 recast
1 reaction
KMacš ā©
@kmacb.eth
More seriously, this is likely the direct result of corporate control of a public good. This āworking codeā āgeneral consensusā BDFL thing is now probably the last thing Iām concerned about in Farcasterland. The rest theyāve delivered on promises. Keep the dc/gc āprotocol as MerkleMās if you want but stop bloating Farcaster.
1 reply
1 recast
1 reaction
Andrei O.
@andrei0x309
Correct, that is how it looks from the outside, building in the open was always only after, many people complained. There's no interest in building in the open, if you do a `find whitelist` command over all proprietary code that the Farcaster team drives I am sure you'll get like 50+ hits... Not trying to be cynical but for me, it seems like the main interest is to appear to be open while trying to retain as much control as possible without suffering too much backlash, that's why there is so much promotion of "openness", if you're open you don't need to promote that, because is just a fact.
1 reply
0 recast
1 reaction
