1<!doctype html> 2<html><head> 3<title>Trivial Technologies — Trivial Technology</title> 4<meta charset="UTF-8"> 5<meta name="generator" content="romanzolotarev.com/ssg"> 6<meta name="stylesheet" content="perfectmotherfuckingwebsite.com"> 7<meta name="viewport" content="width=device-width, initial-scale=1"> 8<link rel="stylesheet" href="style.css"> 9</head><body> 10<nav> 11 <a href="index.html">Index</a> 12 <a href="manifesto.html">Manifesto</a> 13 <a href="landing.html">Landing</a> 14 <a href="guidelines.html">Guidelines</a> 15</nav> 16<h1>Trivial Technologies</h1> 17 18<p>Trivial Technology (TT) is a new way of doing FOSS, whose goal is to maximally empower the individual, by providing a stepping stone for whatever they may wish to build.</p> 19 20<p>TT is Trivial. A beginner should be able to completely understand it in 2 days. A professional should grasp it in a rainy afternoon. It is not meant to be a plug-and-play black box that one does not open lest they contract some ancient curse.</p> 21 22<p>TT is malleable. There are visible hooks for adding features and open points where one can extend functionality. It is not a feature pinata where one has to dance around implementation details.</p> 23 24<p>TT is open. As much as possible, TT is offered with no strings attached and we mean it. It's licenced under the most permissive licences we can find (0BSD, Unlicence, CC0) and even that we see as a compromise. Nobody will frown at you for forking TT, there's nobody to ask for permission, there's no original author that has to be forever mentioned.</p> 25 26<p>TT is your own. To find out more about how this came to be and what are the larger principles behind this movement, be sure to read our manifesto.</p> 27 <footer><p> 28 This mirror maintained by <a href="mailto:[email protected]">[email protected]</a>. 29 Original Trivial Techology repo maintained at <a href='https://github.com/TrivialTechnologies/TT'>github.com/TrivialTechnologies/TT</a>. 30 </p></footer> 31 </body> 32</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.