# Background

* ### Censorship  <a href="#id-1-censorship" id="id-1-censorship"></a>

  \
  The centralized control of our social data results in a scenario where a handful of major companies possess absolute control over the propagation of social opinions, ideas, and content. This form of censorship manifests in various ways, including politically motivated suspensions by platforms, pressure from nation-states leading to censorship, or unexplained forms of suppression.

* ### **Unrealized Value for Creators**  <a href="#id-1-censorship" id="id-1-censorship"></a>

  \
  Social media content generates immense value globally, yet in the Web 2.0 landscape, content creators only retain a small fraction of that value.\
  \
  Actually, the value of Web3 extends beyond the social aspect; it applies to any other field as well, and DeFi is the prime example.

* ### Data is compartmentalized and redundant <a href="#id-1-censorship" id="id-1-censorship"></a>

  \
  Within the centralized framework of Web 2.0, our social data and graphs are confined within "walled gardens". Transitioning this data between systems is exceedingly challenging and often unfeasible. This circumstance results in elevated switching costs, introducing user friction and wasting time as users consistently establish connections each time they engage with a new application.

* ### Inhibited Innovation <a href="#id-1-censorship" id="id-1-censorship"></a>

  \
  Isolated data further curtails innovation. When a handful of entities possess access to our collective data, independent developers are hindered from exploring and utilizing this data to create beneficial products. For instance, if someone conceives a superior Instagram interface or an improved feed algorithm, they lack the capacity to harness the vast user-generated data to actualize their concept, even with user consent.&#x20;


---

# 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://onboard-social.gitbook.io/onboard-whitepaper/welcome-onboard/background.md?ask=<question>
```

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.