[ COMMANDMENTS ]

I have the unfortunate tendency of being bound by principles in my approach.

These are the ones that served as the ground work for this project.

I

Must be completely functional

I wasn't interested in making a product for aesthetic or speculative purposes. I knew that I wanted whatever I had made to be a real, working piece of software that does what is intended to do.

II

Create an alternative to the internet

The root issue I wanted to tackle was my qualms with the internet as a system. This is explored further in the "REFUSAL" page but in short, I wanted to make a tool that could distribute information

III

Give people the means to share information

Ultimately, the goal of TARSYS was to bring the means of communicating back into the hands of the people. With that in mind, it had to be a flexible application in the sense that people could use it however they saw fit.

IV

Cannot use the internet in its operation

Given that the grounding idea of TARSYS was to circumvent the systems of the internet, it didn't make sense to use the internet in its operation. How can you defeat a system by still using it?

V

Manifests as distributable software

With TARSYS being a means of undermining and subverting pre-existing methods of communication, there is a very high likeihood that there would be agents that would wish for it's downfall. Thus, existing as distributable software gives it staying power, as people can repeatedly share the software and not stamp it out.

Hierarchy 2 Streamline Icon: https://streamlinehq.com