# Script TV + Web3

While Web 1.0 and Web 2.0 furnished many possibilities for the global population, there were still many issues involved, such as data privacy, safety, centralization, and more. The problem is that we lost sovereignty of our data when large unified companies like Facebook began to own user data. Nowadays, the information we share on social media is used without our consent and sold to marketers to more efficiently target us as consumers or influence our political leanings.

## **ScriptTV: Bridging Video Streaming With Web 3.0**

Thanks to blockchain technology and the inception of Script.tv, we are now beginning to return to a more decentralized internet. It is the only viable solution that will allow us to regain control of our data, preserve rights for online privacy, and ensure the free flow of information.

Script.tv has the potential to revolutionize video streaming for television stations and broadcasts while providing the necessary infrastructure for web 3.0, allowing anyone to host video content and live streams in a decentralized manner.

Due to the immutability of the blockchain, Script.tv creators will have the creative liberty to post any content without the fear of being censored or de-platformed. Furthermore, Script.tv will offer a more affordable and robust storage system than cloud services. There won’t be any server downtime or security leaks/hacks related to central points of failure.

Another essential element of web 3.0 protocols like Script is establishing a fairer distribution of profits for content creators and rewarding users for helping maintain the platform’s functioning.


---

# 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://documentation.script.tv/about-script-network/script-tv-+-web3.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.