Update

wiki_style.md

@@ -21,6 +21,7 @@ If you contribute, add yourself to [wiki authors](wiki_authors.md)! You can also
 - **Filenames of articles shall use a lowercase snake_case**.
 - **Article/file names are to be preferably singular nouns**. I.e. "animal" rather than "animals", "portability" rather than "portable" etc. But there may be exceptions, e.g. articles that are lists may use plural ("human" is about human as species, "people" is a list of existing humans), non-nous MAY be used if nouns would be too long/awkward (e.g. "weird" instead of "weirdness"). Use your brain.
 - **This isn't [Wikipedia](wikipedia.md)**, memes, opinions and uncensored truths are allowed (and welcome). **References/citations are not needed**, we aren't a religion that relies on someone else's reputation to validate truth, we just spread information and leave it to others to either trust, test its usefulness and/or verify. Furthermore we don't limit ourselves to truths that can be or have been "proven" by whatever is currently called "approved science^TM", many valuable truths are just proven by experience etc. LRS advocates society in which deception doesn't happen and in which therefore there is no need for citations serving as a proof -- we practice this here. However references are still allowed and many times useful, e.g. as a further reading.
+- Unlike with [Wikipedia](wikipedia.md) our criterion of inclusion isn't notability, i.e. things that people talk about, but value, i.e. **things that are worth talking about**. On the other hand if something is notable but of little value, such as details of [OOP](oop.md) or famous feminists, we won't write too much about it, it's just useless noise that harms the good things by obscuring them.
 - The style of this wiki is inspired by the classic hacker culture works such as the [WikiWikiWeb](wikiwikiweb.md) and [Jargon File](jargon_file.md).
 - **Writing style should be relaxed and in many parts informal**. Formality is used where it is useful (e.g. definitions), most of other text can benefit from being written as a tech conversation among friends.
 - **Depth/complexity/level of articles**: Articles shouldn't try to go to unnecessary depth, but also shouldn't be shallow. This is written mainly for programmers of [less retarded society](less_retarded_society.md), the complexity should follow from that. Again, start simple and go more into depth later on in the article, very complex things should rather be explained intuitively, no need for complex proofs etc.