it's 2024, when i sign up for an onchain social app, i expect to autofollow anyone who i already follow on farcaster

social

|￣￣￣￣￣￣￣￣￣￣￣|
|       Stop conflating       |
|   creators and friends   |
|＿＿＿＿＿＿＿＿＿＿＿|
         (\__/)  ||
         (•ㅅ•) ||
         / 　 づ

What if the fc graph topology doesn’t make sense for the app?

@zinger has a good take here that the fc graph is for friends not followers - I’m not sure if it makes sense to import it in other social contexts

/new-york by day 🗽 /latenightcrew by night :) Fan of eating tacos and bringing people together, often at the same time 🌮 oh and /untzuntz 😈

optimist • building the front page of onchain culture at /forage • ENS: richiebonilla.eth

What if the fc graph topology doesn’t make sense for the app?

@zinger has a good take here that the fc graph is for friends not followers - I’m not sure if it makes sense to import it in other social contexts 

https://warpcast.com/zinger/0x23ca9a39

Linking relationships (i.e. follow) at the protocol level has a type. This could be used to support different types of relationships.

What docs is this screenshot from?

I could only find this: https://docs.farcaster.xyz/reference/hubble/datatypes/messages#_5-1-linkbody

This is fascinating though - what is the default type that Warpcast uses, and are there any other types in use currently?

The open web is dead, long live the open web. ⌐◨-◨

Building /warpcast and /farcaster

— gabrielayuso.com

https://github.com/farcasterxyz/protocol/blob/main/docs%2FSPECIFICATION.md

@sanjay might be able to answer your other questions about usage