Content
@
0 reply
20 recasts
20 reactions
Vladyslav Dalechyn
@dalechyn.eth
It's hard for people who are not at least one inch deep into the Farcaster protocol to even tell the difference between Warpcast and Farcaster. Warpcast isn't the only client, it's just the first one. Anyone is open to build another client™ make smoother UX, richer DX and win Warpcast. In a non-decentralized environment you wouldn't be able to do it.
15 replies
11 recasts
76 reactions
Vladyslav Dalechyn
@dalechyn.eth
Making changes to social graph is a risky and very complex change to be done – forking should be much more endorsed to let people not just iterate on the app client looks/ideas – but also on the protocol level. I'd say it's the Step 2 for App Clients – you firstly iterate by building a "private" subset of a social graph, and only when you feel like the change is really positive and that it finds it use, you contribute to "L1". A good example of this is /uno's stories.
2 replies
1 recast
5 reactions
Steve
@stevedylandev.eth
Only qualifier I might add is that the protocol is ultimately still controlled by Merkle. Yes it’s permissionless, but FIPs and other decisions are still ultimately decided by the Merkle team. Examples include FIP-171, channels, and hub architecture. They do ask for feedback, but nothing can force their hand even if a majority disagrees. Not saying that’s a bad thing, it’s a VC funded startup that has to succeed, but just something people should be fully aware of before they start building.
2 replies
0 recast
3 reactions
Vladyslav Dalechyn
@dalechyn.eth
I'm not deep into hubs, but considering that they communicate with each other, there should be a way to fork a hub, connect it to other hubs but yet keep the "L2" cloud of hubs to support FIP-171 in example. Can that be possible to avoid such dillema? I'd say pushing a FIP isn't easy – just as pushing EIP to modify Ethereum isn't.
1 reply
0 recast
2 reactions
Steve
@stevedylandev.eth
I could be be wrong here, but I don't think it works like that unfortunately. You can fork the hub architecture and start your own network, but I don't think it would be compatible with farcaster mainnet. Hubs work with a gossip system using libp2p vs a blockchain mechanism, so the concept of L1 vs L2 doesn't work the same. However I know @vrypan.eth has been working on the concept of Farcaster L2s and could probably comment better than I could.
1 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
Not working as in actual working, just sharing ideas 🤣 https://blog.vrypan.net/2024/06/26/farcaster-l2/
1 reply
0 recast
2 reactions
Vladyslav Dalechyn
@dalechyn.eth
you read my mind and layered my thoughts 100x smarter! great article
1 reply
0 recast
2 reactions
vrypan |--o--|
@vrypan.eth
🙏
0 reply
0 recast
0 reaction
