Important changes regarding create/edit permissions
Sadly, due to spam, I have implemented a mechanism where specific users are Contributors, and these users have the ability to create and edit pages. A user profile (email confirmed or not) can no longer edit.
How to become a contributor? Email me...
If you browse ARMwiki as a non-logged in user, no cookies will be set. If, however, you create an account or log in, several cookies will be set in order that you may be identified to the server (for editing content, etc).
Please scroll down in order to read more about this.
ARMwiki is always looking for user contributions. If you have anything to add, please do. To help spark your creative juices, please browse the list of pages that have not yet been written that are cited by existing pages. When writing pages, please follow the style guide.
Please note: You must be a signed-in user who has contacted me for Contributor level access in order to create or edit content.
Copyright infringment? Request for Content Removal
There is no mechanism for you, the user, to explicitly "consent" to having cookies stored. However, if you have come here as an anonymous user, no cookies will have been placed on your machine. It is only when you create an account or login that the cookie is required. Therefore, it will be assumed that logging into ARMwiki is giving consent to having ARMwiki manipulate and store its own cookies on your computer.
Four cookies are stored, all beginning with irreleva_mysql followed by a bunch of numbers. This is a reference to the underlying database upon which ARMwiki is based. The cookies are Token, UserID, UserName, and session. Their function should be clear from the names. Check what cookies are being stored on your computer (this is a how-to, not some sort of script).
Feel free to wipe off the cookies at any time, or to configure your browser to retain cookies from this site on a session-by-session basis. It will not hurt anything, all you'll need to do is log in again.
ARMwiki does not contain embedded advertising, therefore there are no issues with third-party cookies.
You may read the full (and rather boringly verbose) directive at: