A place for developers to talk about building on Farcaster.

/dev

A long time ago, I wrote about Lens vs Farcaster https://paragraph.xyz/@teleyinex.eth/farcaster-vs-lens-protocol. 

The time has come to write about the Farcaster vs AT protocol https://paragraph.xyz/@teleyinex.eth/farcaster-vs-at-protocol

The blog post analyzes how both protocols are built from the technical point of view. I hope you like it.

🌷💀⏳

teleyinex.eth ▫️

teleyinex.lens ▫️

teleyine.x ▫️

daniellombrana.es  ▫️

@astaralabs ▫️

@obeygiant ▫️

@scifabric ▫️

dev

Would enjoy a deeper dive! Some corrections: I believe Bluesky also uses CRDTs as part of its Automerge protocol, and CIDs are also data hashes just like Farcaster. They have more in common than the article implies. :)

A doodler and computerer. I like permissive/permissionless open source, smart contracts, p2p systems, room-scale VR, and NixOS.

shazow.net

Currently: WhatsABI

I couldn't find more info on their docs. Maybe they have it in a different place. Thanks for the corrections.

Let me know if you want links for anything specific! CIDs are a construct of IPFS.

Can to share links for the auto merge protocol?

Hahahaha, no worries. I couldn't find information regarding how they handle conflicts, and it is super interesting to learn about them.

CRDTs are useful.  I have been reading about them for local first solutions.

Actually I think I mixed up the automerge thing with another protocol, my bad!