# Time to Wake Up

> [Mushon Zer-Aviv](https://github.com/costoffreedom/costoffreedom-book/tree/2206d40f4fbd41d7489de1da00d444b3d56f0f0a/book/appendix/attributions.html#mushon-zer-aviv)

Freedom of information, much like freedom of markets, doesn’t “naturally” lead to the kind of freedom we hope for in society. In fact, in the past decade since the rise of the free culture movement, we’ve seen many costs such as time, attention and education shifting to the side of content creators while financial profit is centralized by the data-hoarding Internet giants that enjoy the reputation of information liberators. Google, for example, is considered a great patron for free culture, whereas in practice it cannibalizes the free culture that it monetizes, offsetting the costs of culture from those consuming it, and profiting from those creating it, and that’s us.

The technological principle that powers digital freedom of information, and that we celebrate through free culture and the creative explosion of the web, is the same technological principle that powers digital surveillance. We have to stop seeing these technological principles as “ready-made for culture” whether that be as a pre-made model for cultural exchange, or as a pre-made model for the end of privacy. This techno-determinism is a double-edged sword; it’s time to wake up and realize that the new possibilities and challenges posed by digital networks should inform the way we decide to live our lives, not dictate it.


---

# 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://book.costoffreedom.cc/index-2/time-to-wake-up.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.