PrivacyWiki:Namespaces

Nothing to hide, but nothing to show you either.
Revision as of 18:28, 9 September 2020 by 21x (talk | contribs) (Created page with "{{SITENAME}} is broken into a number of mw:namespaces which delineate purpose of each article, and how it should be written. This page is here to elaborate how each namesp...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

PrivacyWiki is broken into a number of mw:namespaces which delineate purpose of each article, and how it should be written. This page is here to elaborate how each namespace should be used.

Main namespace

Main namespace is where most of the wiki's content should reside. Articles in main namespace should focus on practical advice regarding software, services, technologies and concept which the reader uses every day. The focus here is on the practicality and actionability. This means that the reader can take the subject product/service and based on the article's advice be able to implement changes to it which strengthen reader's privacy.

Articles in main namespace should not be about abstract concepts or arguments. While advocating for privacy is purpose of this wiki, we do not want to bog the reader down in philosophical arguments which offer no immediate value to the reader.
That does not mean that the mainspace articles cannot offer explanations or mention more abstract topics, but those explanations have to be directly in service of the actionable advice they're attached to.

For example, if the advice is for the user to change to a more private DNS provider, you may have to offer a brief explanation of what DNS is. However, this explanation should only be as long and as detailed as it is necessary to convey the basic idea of DNS (phone directory of the internet). If the reader wishes to know more, they can follow the links to the specific Concept namespace article or to Wikipedia itself.

Concept namespace

Concept namespace is for concepts and ideas that are adjacent to privacy, but do not lend themselves to actionable advice. Articles in the Concept namespace should be considered optional or supplementary reading to contextualise the decisions and advice we offer in this wiki. The reader should not have to read the Concept namespace articles to benefit from the actionable advice in the namespace, but doing so should be beneficial to their understanding of the underlying issues.

Not every concept or idea should have a Concept article. Generally speaking, terms which could be unfamiliar to a reader should be linked to the appropriate Wikipedia article. A Concept article should be created only where the equivalent Wikipedia article does not cover the privacy adjacent issues well or at all, and a separate elaboration would be helpful.

The Concept articles also should not reinvent the wheel in comparison to Wikipedia. We are not looking to write a general article on the topic, or focus on non-privacy related aspects. Stay on topic.
For example, using Concept:Free software has a number of different benefits, such as education, freedom from abusive copyright laws or accessibility of software to everyone regardless of their ability to pay. However, our article in the Concept namespace should focus on the privacy benefits of the Free software, and leave the coverage of remainder of the benefits to Wikipedia or Free Software Foundation. Thus, while we won't shy away from mentioning those benefits, where possible and tone appropriate, we will do so mainly by linking to those resources.