Editorial pass & migration to mkdocs.

There's a lot in grimoire.ca that I either no longer stand behind or feel pretty weird about having out there.

6 files changed, 0 insertions, 283 deletions

diff --git a/wiki/people/co-op-social-media.md b/wiki/people/co-op-social-media.md
deleted file mode 100644
index afbb119..0000000
--- a/wiki/people/co-op-social-media.md
+++ /dev/null
@@ -1,51 +0,0 @@
-# Notes towards a Co-Op Social Network
-
-## Premises
-
-* Money, and paid labor generally, are a prerequisite to a polished, usable technical system that is accessible to more than just the technical core of its contributors.
-
-    * A social network is a technical system.
-
-* Existing social network systems have _users_ - people who socialize through the network - and _customers_ - people who provide revenue in return for obtaining something of value. Those two groups have incompatible desires, and the ones with the money win.
-
-    * _Users_ want a way to connect, communicate, plan, and organize with people they know.
-
-    * _Customers_ want to maximize the return on their dollars.
-
-    * Social network customers tend to be advertisers, whose goals are maximizing the visibility of their messages and maximizing the information extracted about the relationships and demographics of the users being advertised to.
-
-        * Secondary customers: law enforcement.
-
-* Revenue from customers and investor dollars are the only sources of money for a privately-owned, incorporated social network.
-
-* The conflicting incentives between social networks' stated goals, which would benefit the users, and social networks' actual goals, which benefit the customers, is at the root of major, high-visibility dysfunctions in social networks:
-
-    * The rise in news-like advertising on Facebook (it's what metrics provided by Facebook show Facebook users will respond to, after all)
-
-    * Limited or consciously-ineffective tools for managing conflict. (If you block someone, you can't see ads they might propagate or share!)
-
-    * Emphasis on metrics-gathering and privacy-puncturing tools even for users (automatic location posting, closed services, infinite data retention as the default).
-
-    * Features widely requested by users generally disregarded in favour of "pet" features, features requested by customers, and doing nothing.
-
-    * The "Nobody at Twitter uses Twitter" problem
-
-* Social media users are poorly-served by existing social networks, as a result of these mismatched incentives.
-
-* Accepted wisdom is that nobody will pay to use a social network, and that social networks which need money therefore must find money somewhere else.
-
-* We can do better.
-
-## Proposal
-
-* Organize a social media venture as a cooperative, so that the company's own incentives line up with things that benefit the users.
-
-    * What kind of co-op? Member-owned? Employee-owned? The incentives are different.
-
-* Fund the cooperative through a combination of membership dues, user fees, public and private _grants_, and other non-transactional income sources.
-
-* Direct the construction, modification, and maintenance of the network with direct involvement of the network's users.
-
-    * How?
-
-* Prioritize the welfare of users and the sustainability of the enterprise, rather than maximizing revenue or assets.
diff --git a/wiki/people/community-norms.md b/wiki/people/community-norms.md
deleted file mode 100644
index 9062f23..0000000
--- a/wiki/people/community-norms.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# Community Norms & Problematic Media
-
-From a Slack discussion about [this rpg.stackexchange thread](http://meta.rpg.stackexchange.com/questions/6399/rpgs-by-and-for-white-nationalists):
-
-> Roleplaying games are vehicles for stories. If you ignore the social context and strip them down to pure mechanics, you might as well play ​_any_​ game - but (a) mechanics are not, themselves, morally or socially neutral, and (b) the thing Varg actually shipped is, quite consciously, laden with intent, and disregarding that wilfully enables him.
->
-> Critical analysis and remixing is a great way to defang racist literature.
->
-> I think maybe the point is “it’s not the game, it’s the players:” you’re (implicitly) arguing for a conscious, intentional restriction on the spectrum of tolerated opinions and beliefs. That’s fine, that’s ​_the nature of social spaces_​, but the idea of consciously excluding someone on that basis is, at least on paper, anathema to (for lack of a better term) nerd culture.
->
-> (It actually happens anyways, “on paper” and “lol these are humans” never line up. I'm talking about what we tell ourselves, and therefore how we justify our actions.)
->
-> The conversation about whether to ban discussion of ​_the game_​ is misguided, because it doesn’t address any of that. A bunch of folks who all agree with the prevailing opinion (that racist vehicles are a bad idea and the people who voluntarily participate in them are, at best, highly suspect) should, I think, be perfectly able to have a sensible, critical discussion of the game without violating community norms.
->
-> What you’re actually asking for, and what may be the only way to manage this, is a ​_ban on having personal beliefs that align with the author's_​.
->
-> I’m +1 on that, and someone in the thread explains why perfectly: nominal inclusiveness causes marginalized people to exclude themselves for their own protection, since nominal inclusiveness prevents various social safety mechanisms that might otherwise protect marginal people from functioning.
->
-> Basically, I think [geek social fallacies #1 and #2](http://www.plausiblydeniable.com/opinion/gsf.html) are driving that thread.
->
-> In a context where it’s unacceptable to say “if you are racist, we want you to leave,” banning discussion of racist material is a workable stopgap, but it’s considerably more expensive (more stressful, harder to enforce, harder to explain to new community members) than fixing the problem you actually care about.
->
-> I’m quite happy to ban people for having vile opinions. The “it’s just my opinion, man” stance that so, so many idiot bros (even me, sometimes) fall back on is not, basically, a good reason to tolerate people.
diff --git a/wiki/people/public-compensation.md b/wiki/people/public-compensation.md
deleted file mode 100644
index dcae172..0000000
--- a/wiki/people/public-compensation.md
+++ /dev/null
@@ -1,101 +0,0 @@
-# Notes Towards A Public Compensation Database
-
-There's a large body of evidence that silence about compensation is not in the interest of those being paid.
-Let's do something about that: let's build a system for analyzing and reporting over salary info.
-
-## Design Goals
-
-1. Respect the safety and consent of the participants.
-
-2. Promote a long-term, public conversation about compensation and salary, both in tech and in other fields.
-
-## Concerns
-
-* Compensation data is historically contentious.
-    For a cautionary tale, see [@EricaJoy's Storify](https://storify.com/_danilo/ericajoy-s-salary-transparency-experiment-at-googl) about salary transparency at Google.
-    Protecting participants from reprisal requires both effective transparency about how data will be collected and used and a deep, pervasive respect for consent.
-
-* Naive implementations of anonymity will encourage abusive submissions: defamatory posts, fictional people, attempts to skew the data in a variety of ways.
-    If this tool succeeds, abuses will discredit it and may damage the larger conversation.
-    Abuses may also prevent the tool from succeeding.
-
-* _Actual laws_ around salary discussion are not uniform.
-    Tools should not make it easy for people to harm themselves by mistake.
-
-* Voluntary disclosure is an inherently unequal process.
-
-## Design
-
-The tool stores _observations_ of compensation as of a given date, consisting of one or more of the following compensation types:
-
-* Salary
-* Hourly wage
-* Bonus packages
-* Equity (at approximate or negotiated value, eg. stock options or grants)
-* “Other Compensation” of Yearly, Quarterly, Monthly, or One-Time periodicity
-
-From these, the tool will derive a “total compensation” for the observation, used as a basis for reporting.
-
-Each observation can carry _zero or more_ structured labels:
-
-* Employer
-    * Employer's city, district, and country
-* Employee's name
-    * Employee's city, district, and country
-* Job Title
-* Years In Role (senority)
-* Years In Field (experience)
-* Sex
-* Gender
-* Ethnicity
-* Age
-* Family Status
-* Disabilities
-
-All labels are _strictly_ voluntary and will be signposted clearly in the submission process.
-Every label consists of freeform text or numeric fields.
-Text fields will suggest autocompletions using values from existing verified observations, to encourage submitters to enter data consistently.
-
-There are two core workflows:
-
-* Submitting an observation
-* Reporting on observed compensation
-
-The submission workflow opens a UI which requests a date (defaulting to the date of submission) and a compensation package.
-The UI also contains expandable sections to allow the user to choose which labels to add to the submission.
-Finally, the UI contains an email address field used to validate the submission.
-The validation process will be described later in this document, and serves to both deter abuse and to enable post-facto moderation of a user's submissions.
-
-The report workflow will allow users to select a set of labels and see the distribution of total compensation within those labels, and how it breaks down.
-For example, a user may report on compensation for jobs in Toronto, ON, Canada with three years' experience and see the distribution of compensation, and then break that down further by gender and ethnicity.
-
-The report workflow will also users to enter a tentative observation and review how that compares to other compensation packages for similar jobs.
-For example, a user may enter a tentative observation for Research In Motion, for Software Team Lead jobs, with a compensation of CAD 80,000/yr, and see the percentile their compensation falls in, and the distribution of compensation observations for the same job.
-
-## Verification
-
-To allow moderation of observations, users must include an email address when submitting observations.
-This email address _must not be stored_, since storing it would allow submissions to be traced to specific people.
-Instead, the tool digests the email address with a preconfigured salt, and associates the digest with the unverified observation.
-The tool then emails the given address with a verification message, and discards the address.
-
-The verification message contains the following:
-
-* Prose outlining the verification process.
-* A brief summary of the observation, containing the date of the observation and the total compensation observed.
-* A link to the unverified observation, where the user can verify or destroy the observation.
-
-The verification system serves three purposes:
-
-1. It discourages people from submitting spurious observations by increasing the time investment needed to get an observation into the data set.
-2. It complicates automated attempts to skew the data.
-3. It allows observations from the same person to be correlated with one another without necessarily identifying the submitter.
-
-The correlation provided by the verification system also allows observations to be moderated retroactively: observations shown to be abusive can be used to prevent the author from submitting further observations, and to remove all of that author's submissions (at least, under that address) to be removed from the data set.
-
-Correlations may also allow amending or superceding observations safely. Needs fleshing out.
-
-## Similar Efforts
-
-* Piper Miriam's [Am I Underpaid](https://github.com/pipermerriam/am-i-underpaid), which attempts to address the question of compensation equality in a local way.
-* As mentioned above, [@EricaJoy's Storify](https://storify.com/_danilo/ericajoy-s-salary-transparency-experiment-at-googl) covers doing this with Google Docs.
diff --git a/wiki/people/rape-culture-and-men.md b/wiki/people/rape-culture-and-men.md
deleted file mode 100644
index ca97504..0000000
--- a/wiki/people/rape-culture-and-men.md
+++ /dev/null
@@ -1,39 +0,0 @@
-# This Is Rape Culture
-
-In the last couple of years, I've been interacting with folks who take a more
-active hand in gender and social issues, and it's changed the way I see the
-word “rape.” It didn't entirely make sense to me how so many people could be
-self-identified victims of rape culture while so few people are, even in a
-euphemistic way, identifiable as rapists, so I dug a bit at my assumptions.
-
-Growing up immersed in what I now recognize as the early stages of modern
-“news” culture, rape was always reported as a violent act. Something so black
-and white that if you committed rape, you would know yourself to be a rapist.
-Media descriptions of rape and of rapists focussed on acts of overt violence:
-“she was in the wrong neighbourhood and got raped at knifepoint,” “held down
-and raped,” and so on.
-
-Reading more recent postings on the idea of “rape culture,” however, paints a
-very different picture of the same word. “Raped at a party,” “too drunk to
-consent,” and other depictions of rape as an act of exploitation (or,
-appallingly, convenience or indifference) rather than violence.
-
-Let me be perfectly clear here: without _active consent_, any sexual contact
-is rape or is on the road to it. In that sense, violence, exploitation,
-intoxication and other forms of coercion are interchangeable and equally vile.
-
-However, when the public idea of rape is limited to rapes with overt violence,
-it's really easy to excuse non-violent coerced sex as “not really rape.” After
-all, you didn't hit her, did you? She never said _no_ and _meant it_, right?
-
-I don't know what I'm going to do with this insight, yet, but I think it's an
-important piece towards educating the next generation to be more awesome and
-less dangerous to each other and un-learning any bad habits and beliefs I
-already have.
-
-Relevant reading:
-
-* [“My friend group has a case of Creepy Dude,” by Captain
-  Awkward](http://captainawkward.com/2012/08/07/322-323-my-friend-group-has-a-case-of-the-creepy-dude-how-do-we-clear-that-up/)
-  (which also reminded me that it's possible to be a creep to your girlfriend)
-* [“Meet the Predators,” from the fantastic Yes Means Yes](http://yesmeansyesblog.wordpress.com/2009/11/12/meet-the-predators/), cited in the Captain Awkward article but worth a read on its own well-researched merits.
diff --git a/wiki/people/rincewind.md b/wiki/people/rincewind.md
deleted file mode 100644
index 7dbc202..0000000
--- a/wiki/people/rincewind.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# On Rincewind
-
-[Rincewind](http://wiki.lspace.org/mediawiki/index.php/Rincewind), we are
-told, is a wizard. On the Disc, wizarding is a profession; Pratchett based
-them on the English academic system, with colleges and bursars and tenure. A
-wizard is a man of some academic distinction, or a student of such a man;
-career wizards are uniformly well-fed, of sound body (if not necessarily of
-sound mind) reasonably dressed, opinionated, crankish, and - importantly -
-capable of magic.
-
-Rincewind is a wizard: he is not well fed, having spent his life being thrust
-from one adventure to the next; his body is more attuned for running away
-from things than it is for meandering the halls or sitting by a fire; his
-opinions largely revolve around “is this new thing going to eat me,” rather
-than more abstract matters; importantly, he is completely incapable of magic,
-in spite of years of study.
-
-Rincewind is a wizard, and the interesting thing about that is that the
-reader is expected (and I certainly did) take both his and the narrator's
-insistence on it at face value. Why shouldn't we?
-
------
-
-I had a conversation with [@aeletich](https://twitter.com/aeleitch) a while
-back, while she was teaching herself to program. I don't recall exactly what
-prompted it, but at one point I told her to stop worrying about all the
-better programmers out there: from everyone else's point of view, she was
-already a wizard. There might be better wizards, and worse wizards, but she'd
-already passed any sort of bright line delimiting “not a programmer” from
-“programmer.”
-
-I think self-identification is important, and overlooked.
diff --git a/wiki/people/why-twitter.md b/wiki/people/why-twitter.md
deleted file mode 100644
index ef20b14..0000000
--- a/wiki/people/why-twitter.md
+++ /dev/null
@@ -1,37 +0,0 @@
-# Why Twitter? Survey
-
-I [asked](http://twitter.com/derspiny/status/835317524480811008)
-
-> Twitter frens! Why do you use Twitter?
-
-I got some answers:
-
-> everyone I think is cool is good at it
-- [@angusiguess](http://twitter.com/angusiguess/status/835318098156716032)
-
-> mostly to rant pointlessly about computers. also to annoy @jdiller and to follow @SwiftOnSecurity
->
-> also for creative and hilarious seasonal username changes.
-- (a locked account)
-
-> i'm pretty shy and prefer the intimacy of plausible deniability and public speaking to actually leaving my house.
-- [@aeleitch](http://twitter.com/aeleitch/status/835322188643336192)
-
-> it's _the_only_ popular social network with good API access and a commitment to users retaining IP ownership of what they post.
-- [@gnomon](http://twitter.com/gnomon/status/835335715043098624)
-
-> natural selection of interesting URLs
-- [@letoams](http://twitter.com/letoams/status/835343447640981508)
-
-> It's where I learn about tech, politics and other issues; more than any other place. It's also where I interact with said things.
->
-> I also have a lot of people I'm close to here, but in a way that doesn't fit into Facebook.
-- [@jkakar](http://twitter.com/jkakar/status/835345823219118080)
-
-> bitching. Side eye. Drunk posts.
->
-> oh. Also cats.
-- (another locked account)
-
-> interesting content slot machine
-- [@blagh](http://twitter.com/blagh/status/835374149740728320)