Skip to content
forked from gungorkocak/tyyp

An application level networking protocol to enable government controlled internets

Notifications You must be signed in to change notification settings

kommradHomer/tyyp

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

23 Commits
 
 

Repository files navigation

tyyp://

A demonstrator shows love and support for TYYP during one of the recent protests in Istanbul Analytics TYYP in the making...

TYYP is an application level networking protocol for government controlled information systems, named after the notable 21st century villain Recep Tayyip Erdogan. TYYP was not started or is being coordinated by an open standards consorcium, because openness and freedom are oxymorons of the dictatorial values we commonly share and some of our design goals.

Features and design goals

  • Acts as a proxy between users and HTTP/HTTPs resources.
  • Removes the bad side effects of HTTPs.
  • Removes anonymity permanently. You can match any request with a subscriber. Good news is that your subscribers don't need to remember passwords anymore, your ISPs can automatically log your users into any website.
  • Provides full functional parity with HTTP/HTTPs on the client level. It's perfectly backwards compatible, browsers don't need to support TYYP. Your users can keep continue to use fully open sourced browsers -- which is also a good selling point.
  • All requests are logged and persisted at least for 2 years, you don't need to be in a hurry investigate the dirty laundry of your subscribers.
  • Makes it possible to censor or block a certain path under a domain. It is such a huge improvement over blocking the entire host or the entire IP block. DNS block is so 2000s...
  • Retrieve detailed metrics about the browsing trends in the large scale. You can monetize this information by selling it to marketing agencies.
  • Easy to market to the clueless public as a product of safe browsing.
  • Allows you to jail anyone by faking the records.
  • Reminds you of Tayyip and the limitlessness of the evil.

Get started

To enable this technology, follow the steps:

  • Create and sustain a dictatorial government or get in high power to make influence on legislative institutions. The separation of powers should not be in the business anymore to make sure jurisdiction can't get against of the deployment and execution of this technology. Read recent history of the Middle East for influence and success stories in this area.
  • Pass certain acts to force ISPs to discontinue support for HTTP/HTTPS. Deactivate provider licenses if they disagree. Make them forward all HTTP/HTTPS requests to TYYP.
  • Use child porn or safe browsing needs as excuses. Know the point of failures of your society. If you're in Middle East, the first example may not work.

Network flow

 +----------+           +---------------+          +-----------+
 |  Host A  |---------> |   Router A    |- TYYP -> |  Tier 1   | Proxification
 +----------+           +---------------+          | Internet  | HTTP/S multiplexing
    (src)                                          | Backbone  | Logging, etc.
                                                   +-----+-----+
    (dst)                                            HTTP/HTTPS
 +----------+           +---------------+                |
 |  Host B  | <---------|   Router B    | <--------------+
 +----------+           +---------------+      Central pipe to the Internet.
  1. Host A makes a TYYP request, request headers and body are parsed by the ISP and logged before any action is taken.
  2. ISP resolves the IP address of the destination host. It's often asked whether there aren't any design flaws since we address no DNS issues. The DNS is not required for this system to work, but we allow clients to make DNS requests not the break the existing software, such as legacy browsers.
  3. ISP decides whether the end destination is allowed to be visited or not. If it's a yes, we authenticate the user automatically (if required) and make an identical HTTP(S) request to Host B.
  4. Host B responses.
  5. ISP receives the packet, parses it, logs the headers and the body, and puts an entry to the user's scorecard according to the destination resource's content rating.
  6. The response is returned to the source as a TYYP response.

Status codes

  • 200: HALAL
  • 303: TURN YOUR HEAD ELSEWHERE
  • 400: MAKRUH
  • 403: HARAM
  • 418: I'm the tayyip
  • 500: YOUR FAULT
  • 502: ARAF

License

Copyright (c) Recep Tayyip Erdogan

The supreme ruler, Recep Tayyip Erdogan ("RTE") hereby grants, ex gratia, to any person accepting his magnanimous sovereign, the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of this software and its associated documentation files (the "Software"), under the following conditions:

Marginal groups, including but not limited to anti-government protestors ("Capulcu"), and any corporation, government body or similar party ("Mihrak") with an evil intent such as undermining Turkey's economical greatness or overthrowing its advanced democracy are strictly prohibited from using the Software for their nefarious purposes. Possession, reproduction, transmission and all other applications of the Software by Capulcu or Mihrak are punishable under law.

The license is valid from time immemorial until after the end of time, unless RTE explicitly states that it is meaningful in terms of timing and disavows his grace upon the license, after which will be considered as an exclusive license for rich-text editors, run-time engines or anything else with the same initials, effective immediately.

Full text is available on the homepage of the RTE License.

About

An application level networking protocol to enable government controlled internets

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published