Farcaster

One point of feedback we got on the Snapchain design doc is that we didn't fully explain why sync in the current model is a problem. 

@sanjay wrote up a good thread on our internal slack, which i'll try to summarize below.

One point of feedback we got on the Snapchain design doc is that we didn't fully explain why sync in the current model is a problem. 

@sanjay wrote up a good thread on our internal slack, which i'll try to summarize below. 

https://warpcast.notion.site/Snapchain-v2-Public-10e6a6c0c101807aadfacbcddda8ce4f?pvs=74

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

thanks for that additional detail. would love for you go deeper on a couple other pieces…

two: what sort of app would require this? if a client were built on top of the protocol, what sort of service would that client provide such that it would make this strategic decision

blockspace babe. cultural attaché from ‘06 twitter. adjacent possible fanatic. writing at https://paragraph.xyz/@jdl

🌐 UTC–5

𝓵𝓲𝓿𝓲𝓷𝓰 𝓽𝓱𝓮 𝓮𝓷𝓭𝓵𝓮𝓼𝓼 𝓼𝓾𝓶𝓶𝓮𝓻 • building @buoy 🛟 • pfista.com

Nomad Rural LLG, Western Province, Papua New Guinea

@pfista did this at the app level for buoy because he didn’t want to index some particularly noisy accounts

have you found buoy's utility increased by doing this beyond the obvious spam mitigation benefits

Yes some people were not creating buoys because they were getting too many spammy notifications. 

Now signal is much higher and more useful for people to get notified about keywords they want to track