# Social Graph In Web2, a social graph is a network graph that says "I know you". It reflects the people that users know through various means: family members, work colleagues, friends from meetings, high school classmates, club members, friends of friends, and so on. Social graphs are mainly generated by mainstream social networks such as Facebook or LinkedIn, where users send invitations to people they know to build and maintain their social relationships. In Web3, all crypto natives are using on-chain addresses to participate in the network, which will result in us not having a precise grasp of the real network of relationships of the people behind each address. So e have designed an on-chain recommendation system to help Web3 users expand their personal Web3 social graphs. ## The way of Expanding Social Graph on Web3 A social graph is a step-by-step process, and Relation is designed to help users do this simply and precisely. The crypto natives can still refine their network through "people they may know". ### Recommended by interest Recommending people with similar preferences based on the on-chain behavior of the crypto native population, such as NFT trading counterparty, DeFi trading records, Games with a common authorization, and other ways to integrate data for a recommendation. ### Recommended by Web2 social media Recommending friends on Twitter, TG, Discord, and Steam's follow list for you. ### Proactive friend-following Crypto Natives can follow their friends by actively searching for their address, nickname, and DID through Relation One. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://relationlabs.gitbook.io/user-guide/walk-into-relation/social-graph.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.