Mike Gerwitz

Activist for User Freedom

path: root/post
Commit message (Collapse)AuthorAgeFilesLines
* 2012-10-06-tradmarks-in-free-software.,d: GNUplot=>gnuplotMike Gerwitz2021-05-111-2/+2
| | | | | | | | | It's pronounced "new"plot, where "gnu" refers to the animal, pronounce "new", not GNU, pronounced "guh-new". I did not know this at the time. http://www.gnuplot.info/faq/faq.html#x1-70001.2
* LibrePlanet 2021: Adopting Free Software Ideals: Typo fixesMike Gerwitz2021-02-241-2/+2
| | | | ...clearly I didn't proofread.
* LibrePlanet 2021: Adopting Free Software IdealsMike Gerwitz2021-02-241-0/+42
| | | | Information about upcoming talk at LP2021.
* Writing As a Means to Another End: New postMike Gerwitz2020-06-301-0/+157
| | | | This is a deeply personal one.
* COVID-19: Update link to current pandemicMike Gerwitz2020-03-161-1/+1
* Social Responsibility Amid COVID-19 OutbreakMike Gerwitz2020-03-161-0/+163
* Fix Copyleft vs. Community linksMike Gerwitz2019-04-071-1/+1
* lp2019 post: Update abstractMike Gerwitz2019-03-051-17/+12
| | | | | | | It had to be shortened to 100 words. This also more accurately reflects what I will be talking about; it will be a slower pace than I had originally anticipated, and will focus a bit more on some core philosophical concepts. But it will still be interesting to both hackers and non-technical users.
* 2019-02-15-i-will-be-speaking-at-lp2019: Update with location (Stata Center)Mike Gerwitz2019-02-211-3/+2
| | | | Just announced, finally. I get nervous when I can't visualize my travels. :)
* post: GHCQ's Exceptional AccessMike Gerwitz2019-02-181-0/+973
| | | | | | | | | | | | | | Wow. I had wanted to spend less than an hour on a response, and instead I wound up writing my largest article since the NSA revelations and GHS. Hopefully others find this useful. I've been sitting on this for weeks because I didn't have the time to finish final proofreading and changes. I need to release this before I sit on it for another couple; I have to start working on my LP2019 talk soon. * post/2019-02-18-ghcq-exceptional-access-e2ee-decentralization-reproducible.md: New post. * src/papers.rec: Add post to top.
* post: I Will Be Speaking At LibrePlanet 2019Mike Gerwitz2019-02-151-0/+33
* post/2013-01-26-re-fsf-wastes-away-another-high-priority-project.md: Remove ↵Mike Gerwitz2019-01-171-1/+1
| | | | duplicate word typo
* post/2018-09-06-libreplanet-2019-will-be-march-23-24-in-boston-ma: Fix URLMike Gerwitz2019-01-171-1/+1
* Generate slug from post filenamesMike Gerwitz2019-01-1682-1/+4
| | | | | | | | | | | | | | | | | | | | Rather than having Pandoc generate the id, which has the potential to change over time and cause 404s, let's just generate the slug from the filename so that the ids will never change. This also solves the awkward question of what the filename should be, since it was previously something arbitrary. This mass rename was accomplished via this simple shell script: for p in *.meta; do slug=$( recsel -P slug "$p" | xargs basename ) mv -v "${p/.meta/.md}" "${p:0:10}-$slug.md" done with minor manual tweaks where I saw fit. Of course, now I have some pretty long filenames, which is undesirable. The next step is to compare it with the slugs currently on mikegerwitz.com and make them match. That's the next commit, and should be pretty simple.
* Translate Git Horror Story from AsciiDoc to MarkdownMike Gerwitz2018-12-221-0/+1316
| | | | | | | | | | | | | | This was a wholly manual effort since Pandoc does not have an AsciiDoc reader (only writer). Fortunately, Pandoc's Markdown features enabled me to keep the style essentially the same. I made no changes to the original text other than changes to markup, so this remains faithful to the original. Any changes to the text will be made in future commits so that the diff can be clearly observed. This could use more work (e.g. getting rid of inline links to make the Markdown file more readable), but otherwise this is in a good enough state for now.
* Convert posts to markdown filesMike Gerwitz2018-12-2291-0/+4875
This was considerable effort, and took a bit more time than I had hoped. While newer posts were written with Markdown, previous ones were writen with my own Markdown-like formatting, but they had enough differences that it was quite an effort to get things updated. I also checked the HTML output of each, though I didn't read every article in detail. Some of these were more substantial than others; National Uproar, for example. These conversions were markup translations: the actual text remains unchanged, except in one minor instance to add text for the sake of providing some text to hold a link to a quote. Any changes to post text will happen in future commits so that the diffs are clearly visible.