> For the complete documentation index, see [llms.txt](https://whitepaper.neighbourhoods.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.neighbourhoods.network/white-paper-2.0/introduction/our-vision/for-the-distributed-web.md).

# For the Distributed Web

The current distributed web generally does away with the central server architecture of the world of corporate mega-platforms without improving upon or even offering up an alternative to its system of account-based logins. Instead of providing groups the means to design and articulate the metrics and structures that make them unique, dWeb apps have focused more on governance of the pools of funds around which they are formed.

Given the scalability problems of blockchains upon which most of these projects are built, and their only marginal efficiency improvements through ‘layer two’ solutions (e.g. lightning networks, directed acyclic graphs (DAGs)), the Web 3.0 space risks mirroring individual-level solutions focused on siloed ledgers. Even when users own their data ($BAT, $DEC) it translates into being paid for it by advertisers and others seeking behavioral insight at the level of the individual consumer. 

With Holochain’s unique efficiency and scalability, we have the opportunity to re-imagine large, social spaces through the lens of interoperable design of culture. Records that are important for determining credibility and reputation become data *which is interpersonal rather than personal,* since it can be ported, translated, and made intelligible across social spaces. Owning data can only bring trivial monetary value to individuals, but it can bring immeasurable collective intelligence to groups.

![](https://lh5.googleusercontent.com/411oGYxZRNt9JqKC38rEGYyxB3lyT8pMNjGea1tT7010Qz8Y1HTVB2ok1MNjNiN3gSCEnS8iuKzAgKPCs-2f5u59Kpk1grWj4BKvo-JAYOOPcUc8vh5vvN9GQgSAjXcEuEnGFlYv)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://whitepaper.neighbourhoods.network/white-paper-2.0/introduction/our-vision/for-the-distributed-web.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.