ABC Browser Circus

this is a random, very small text. no one would care to read it, but you <3

parasite (project B)

— an organism that lives in or on an organism of another species (its host) and benefits by deriving nutrients at the other's expense.

The browser is a fantastic creature; like a flower longing for rays of the sun, it feeds on files from the web; html, css, and js are essential nutrients and once obtained, the incoming bits are processed, and turned into colorful pixels. The browser blooms and the human marvels.

This parasite attaches to the browser. From under its skin, it watches as the browser (its host) interacts with the servers of the world, receives files through the network and renders content. It watches too, as we (the human species) engage with the interface; it listens as we click, scroll, copy, and paste.

What are the parasite’s objectives? Which information does it seek and how does it interfere in its host’s activities? What are the resulting symptoms — how is the browser’s behavior altered? Does the parasite do harm or do good? Or does it merely coexist?

Build a Browser Extension (the parasite), and unleash it.


You may work on this project as a team (of two).


Don't hesitate to ask me any 'Is it technically possible for a Chrome extenion to...' question. The asnwer will mostly be yes, and I will point you to the right resources.


some inspiration: