Skip to content

Instantly share code, notes, and snippets.

@adrienne

adrienne/mullenweg-wpe.md

Last active November 2, 2024 23:00
Show Gist options
  • Save adrienne/aea9dd7ca19c8985157d9c42f7fc225d to your computer and use it in GitHub Desktop.
Save adrienne/aea9dd7ca19c8985157d9c42f7fc225d to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. adrienne revised this gist Sep 27, 2024. 1 changed file with 2 additions and 1 deletion.
    3 changes: 2 additions & 1 deletion mullenweg-wpe.md
    View file
    Original file line number Diff line number Diff line change
    @@ -22,4 +22,5 @@
    ## 27 September 2024

    * Mullenweg uses the .org blog to post [WP Engine Reprieve](https://wordpress.org/news/2024/09/wp-engine-reprieve/), stating that they are re-enabling WP Engine's access to the central repository, but *only through 30 September* (specifically "until October 1, UTC 00:00"), giving WP Engine all of two and a half business days to spin up working mirrors.
    * A WordPress Core contributor reports that [his access to the Make Wordpress team was disabled](https://x.com/KarlAustin/status/1839630750359888142) after he criticized Mullenweg's decision on the team's private Slack
    * A WordPress Core contributor reports that [his access to the Make Wordpress team was disabled](https://x.com/KarlAustin/status/1839630750359888142) after he criticized Mullenweg's decision on the team's private Slack
    * The Verge [posts an explainer article](https://www.theverge.com/2024/9/27/24256361/wordpress-wp-engine-drama-explained-matt-mullenweg)
  2. adrienne revised this gist Sep 27, 2024. 1 changed file with 4 additions and 1 deletion.
    5 changes: 4 additions & 1 deletion mullenweg-wpe.md
    View file
    Original file line number Diff line number Diff line change
    @@ -19,4 +19,7 @@

    # Updates

    * 27 September 2024: Mullenweg uses the .org blog to post [WP Engine Reprieve](https://wordpress.org/news/2024/09/wp-engine-reprieve/), stating that they are re-enabling WP Engine's access to the central repository, but *only through 30 September* (specifically "until October 1, UTC 00:00"), giving WP Engine all of two and a half business days to spin up working mirrors.
    ## 27 September 2024

    * Mullenweg uses the .org blog to post [WP Engine Reprieve](https://wordpress.org/news/2024/09/wp-engine-reprieve/), stating that they are re-enabling WP Engine's access to the central repository, but *only through 30 September* (specifically "until October 1, UTC 00:00"), giving WP Engine all of two and a half business days to spin up working mirrors.
    * A WordPress Core contributor reports that [his access to the Make Wordpress team was disabled](https://x.com/KarlAustin/status/1839630750359888142) after he criticized Mullenweg's decision on the team's private Slack
  3. adrienne revised this gist Sep 27, 2024. 1 changed file with 5 additions and 1 deletion.
    6 changes: 5 additions & 1 deletion mullenweg-wpe.md
    View file
    Original file line number Diff line number Diff line change
    @@ -15,4 +15,8 @@
    * Note, here, that WP Engine's C&D was sent to Automattic, which runs wordpress.**com**, and at no point has WP Engine made *any legal claims whatsoever* against wordpress.**org** or the WordPress Foundation.
    * Meanwhile, Pressable (another web hosting company _also wholly owned by Automattic_), [posts a special offer for WP Engine users](https://archive.is/Ybnmi), offering to buy out their contracts and migrate them for free. (The above is an archival link; at the time of writing, the offer is live and [linked here](https://pressable.com/wpe-contract-buyout/).)
    * Mullenweg has also spent the last several days [Posting Through It on Reddit](https://old.reddit.com/user/photomatt) (link goes to his user page, which should make all comments visible). (Note that many of these comments were posted significantly after his receipt of the C&D letter from WP Engine.)
    * Mullenweg is reportedly also [privately exhorting Automattic employees](https://x.com/ryancduff/status/1838961425647063047) to make supportive posts on their own blogs and social media. There may or may not be an implication that they will be retaliated against if they choose not to do so; reports vary.
    * Mullenweg is reportedly also [privately exhorting Automattic employees](https://x.com/ryancduff/status/1838961425647063047) to make supportive posts on their own blogs and social media. There may or may not be an implication that they will be retaliated against if they choose not to do so; reports vary.

    # Updates

    * 27 September 2024: Mullenweg uses the .org blog to post [WP Engine Reprieve](https://wordpress.org/news/2024/09/wp-engine-reprieve/), stating that they are re-enabling WP Engine's access to the central repository, but *only through 30 September* (specifically "until October 1, UTC 00:00"), giving WP Engine all of two and a half business days to spin up working mirrors.
  4. adrienne revised this gist Sep 27, 2024. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion mullenweg-wpe.md
    View file
    Original file line number Diff line number Diff line change
    @@ -10,7 +10,7 @@
    * Not alleged in the letter, but reported by attendees to WordCamp, is that Mullenweg engaged in a verbal altercation with WP Engine employees working the WP Engine booth at the show, which included Mullenweg threatening to physically dismantle their booth in the middle of the show. (I can't find my link to this right now, i'll look for it later.)
    * Automattic sends [a C&D letter of its own](https://automattic.com/2024/wp-engine-cease-and-desist.pdf) to WP Engine, demanding that they stop misusing the WordPress trademark. (Note that the WordPress *Foundation* is the trademark owner, and Automattic is the sole commercial licensee.) The exhibits are a separate document [here](https://automattic.com/2024/wp-engine-cease-and-desist-exhibits.pdf).
    * Prompted by Mullenweg's multiple blog posts, which get automatically propagated to every WordPress user with the "News Feed" widget on their admin dashboard (which is most WordPress users, as very few actually modify their dashboard), WP Engine disables the "News Feed" dashboard widget for all its customers. (Note that just as with disabling revisions, this is a simple config change, supported by WordPress; it does not involve modifying any code or otherwise "chopping up" WordPress installs.)
    * A day after Automattic sends the C&D, the wordpress.**org** domain (again, maintained by the WordPress *Foundation*), [blocks WP Engine](https://techcrunch.com/2024/09/25/wordpress-org-bans-wp-engine-blocks-it-from-accessing-its-resources/) (and thence all of their customers) from accessing the plugin/theme/update repository. This means that none of WP Engine's customers can install plugins or themes, update plugins or themes, *or update WordPress itself*, including vital security patches. Additionally, all WP Engine user accounts are reportedly banned from the wordpress.**org** site, meaning they cannot post to the forum or update the plugins which they maintain as an organization. (Need to find the link on this one too.)
    * A day after Automattic sends the C&D, the wordpress.**org** domain (again, maintained by the WordPress *Foundation*), [blocks WP Engine](https://techcrunch.com/2024/09/25/wordpress-org-bans-wp-engine-blocks-it-from-accessing-its-resources/) (and thence all of their customers) from accessing the plugin/theme/update repository. This means that none of WP Engine's customers can automatically install plugins or themes, update plugins or themes, *or update WordPress itself*, including vital security patches. Additionally, all WP Engine user accounts are reportedly banned from the wordpress.**org** site, meaning they cannot post to the forum or update the plugins which they maintain as an organization. (Need to find the link on this one too.)
    * [Mullenweg posts](https://wordpress.org/news/2024/09/wp-engine-banned/) about this decision, again to the wordpress.**org** blog, and includes the following statement: "**What I will tell you is that, pending their legal claims and litigation against WordPress.org, WP Engine no longer has free access to WordPress.org’s resources.**"
    * Note, here, that WP Engine's C&D was sent to Automattic, which runs wordpress.**com**, and at no point has WP Engine made *any legal claims whatsoever* against wordpress.**org** or the WordPress Foundation.
    * Meanwhile, Pressable (another web hosting company _also wholly owned by Automattic_), [posts a special offer for WP Engine users](https://archive.is/Ybnmi), offering to buy out their contracts and migrate them for free. (The above is an archival link; at the time of writing, the offer is live and [linked here](https://pressable.com/wpe-contract-buyout/).)
  5. adrienne revised this gist Sep 27, 2024. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion mullenweg-wpe.md
    View file
    Original file line number Diff line number Diff line change
    @@ -9,7 +9,7 @@
    * WP Engine's letter alleges, among other things, that Mullenweg demanded money from WP Engine ostensibly as a licensing fee for the WordPress trademark, but in actuality to refrain from disparaging and defaming them on stage and in blog posts.
    * Not alleged in the letter, but reported by attendees to WordCamp, is that Mullenweg engaged in a verbal altercation with WP Engine employees working the WP Engine booth at the show, which included Mullenweg threatening to physically dismantle their booth in the middle of the show. (I can't find my link to this right now, i'll look for it later.)
    * Automattic sends [a C&D letter of its own](https://automattic.com/2024/wp-engine-cease-and-desist.pdf) to WP Engine, demanding that they stop misusing the WordPress trademark. (Note that the WordPress *Foundation* is the trademark owner, and Automattic is the sole commercial licensee.) The exhibits are a separate document [here](https://automattic.com/2024/wp-engine-cease-and-desist-exhibits.pdf).
    * Prompted by Mullenweg's multiple blog posts, which get automatically propagated to every WordPress user with the "News Feed" widget on their admin dashboard (which is most WordPress users, as very few actually modify their dashboard), WP Engine disables the "News Feed" dashboard widget for all its customers. (Note that is a simple config change, supported by WordPress; it does not involve modifying any code or otherwise "chopping up" WordPress installs.)
    * Prompted by Mullenweg's multiple blog posts, which get automatically propagated to every WordPress user with the "News Feed" widget on their admin dashboard (which is most WordPress users, as very few actually modify their dashboard), WP Engine disables the "News Feed" dashboard widget for all its customers. (Note that just as with disabling revisions, this is a simple config change, supported by WordPress; it does not involve modifying any code or otherwise "chopping up" WordPress installs.)
    * A day after Automattic sends the C&D, the wordpress.**org** domain (again, maintained by the WordPress *Foundation*), [blocks WP Engine](https://techcrunch.com/2024/09/25/wordpress-org-bans-wp-engine-blocks-it-from-accessing-its-resources/) (and thence all of their customers) from accessing the plugin/theme/update repository. This means that none of WP Engine's customers can install plugins or themes, update plugins or themes, *or update WordPress itself*, including vital security patches. Additionally, all WP Engine user accounts are reportedly banned from the wordpress.**org** site, meaning they cannot post to the forum or update the plugins which they maintain as an organization. (Need to find the link on this one too.)
    * [Mullenweg posts](https://wordpress.org/news/2024/09/wp-engine-banned/) about this decision, again to the wordpress.**org** blog, and includes the following statement: "**What I will tell you is that, pending their legal claims and litigation against WordPress.org, WP Engine no longer has free access to WordPress.org’s resources.**"
    * Note, here, that WP Engine's C&D was sent to Automattic, which runs wordpress.**com**, and at no point has WP Engine made *any legal claims whatsoever* against wordpress.**org** or the WordPress Foundation.
  6. adrienne revised this gist Sep 27, 2024. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion mullenweg-wpe.md
    View file
    Original file line number Diff line number Diff line change
    @@ -8,7 +8,7 @@
    * [TechCrunch has solid reporting](https://techcrunch.com/2024/09/22/matt-mullenweg-calls-wp-engine-a-cancer-to-wordpress-and-urges-community-to-switch-providers/) on the [initial events](https://techcrunch.com/2024/09/23/wp-engine-sends-cease-and-desist-letter-to-automattic-over-mullenwegs-comments/): Mullenweg's initial blog post, his WordCamp keynote, his second blog post, and [WP Engine's C&D letter](https://wpengine.com/wp-content/uploads/2024/09/Cease-and-Desist-Letter-to-Automattic-and-Request-to-Preserve-Documents-Sent.pdf). The blog posts are posted to the wordpress.**org** blog, not to Automattic's blog.
    * WP Engine's letter alleges, among other things, that Mullenweg demanded money from WP Engine ostensibly as a licensing fee for the WordPress trademark, but in actuality to refrain from disparaging and defaming them on stage and in blog posts.
    * Not alleged in the letter, but reported by attendees to WordCamp, is that Mullenweg engaged in a verbal altercation with WP Engine employees working the WP Engine booth at the show, which included Mullenweg threatening to physically dismantle their booth in the middle of the show. (I can't find my link to this right now, i'll look for it later.)
    * Automattic sends [a C&D letter of its own](https://automattic.com/2024/wp-engine-cease-and-desist.pdf) to WP Engine, demanding that they stop misusing the WordPress trademark. (Note that the WordPress *Foundation* is the trademark owner, and Automattic is the sole commercial licensee.)
    * Automattic sends [a C&D letter of its own](https://automattic.com/2024/wp-engine-cease-and-desist.pdf) to WP Engine, demanding that they stop misusing the WordPress trademark. (Note that the WordPress *Foundation* is the trademark owner, and Automattic is the sole commercial licensee.) The exhibits are a separate document [here](https://automattic.com/2024/wp-engine-cease-and-desist-exhibits.pdf).
    * Prompted by Mullenweg's multiple blog posts, which get automatically propagated to every WordPress user with the "News Feed" widget on their admin dashboard (which is most WordPress users, as very few actually modify their dashboard), WP Engine disables the "News Feed" dashboard widget for all its customers. (Note that is a simple config change, supported by WordPress; it does not involve modifying any code or otherwise "chopping up" WordPress installs.)
    * A day after Automattic sends the C&D, the wordpress.**org** domain (again, maintained by the WordPress *Foundation*), [blocks WP Engine](https://techcrunch.com/2024/09/25/wordpress-org-bans-wp-engine-blocks-it-from-accessing-its-resources/) (and thence all of their customers) from accessing the plugin/theme/update repository. This means that none of WP Engine's customers can install plugins or themes, update plugins or themes, *or update WordPress itself*, including vital security patches. Additionally, all WP Engine user accounts are reportedly banned from the wordpress.**org** site, meaning they cannot post to the forum or update the plugins which they maintain as an organization. (Need to find the link on this one too.)
    * [Mullenweg posts](https://wordpress.org/news/2024/09/wp-engine-banned/) about this decision, again to the wordpress.**org** blog, and includes the following statement: "**What I will tell you is that, pending their legal claims and litigation against WordPress.org, WP Engine no longer has free access to WordPress.org’s resources.**"
  7. adrienne revised this gist Sep 26, 2024. 1 changed file with 2 additions and 1 deletion.
    3 changes: 2 additions & 1 deletion mullenweg-wpe.md
    View file
    Original file line number Diff line number Diff line change
    @@ -14,4 +14,5 @@
    * [Mullenweg posts](https://wordpress.org/news/2024/09/wp-engine-banned/) about this decision, again to the wordpress.**org** blog, and includes the following statement: "**What I will tell you is that, pending their legal claims and litigation against WordPress.org, WP Engine no longer has free access to WordPress.org’s resources.**"
    * Note, here, that WP Engine's C&D was sent to Automattic, which runs wordpress.**com**, and at no point has WP Engine made *any legal claims whatsoever* against wordpress.**org** or the WordPress Foundation.
    * Meanwhile, Pressable (another web hosting company _also wholly owned by Automattic_), [posts a special offer for WP Engine users](https://archive.is/Ybnmi), offering to buy out their contracts and migrate them for free. (The above is an archival link; at the time of writing, the offer is live and [linked here](https://pressable.com/wpe-contract-buyout/).)
    * Mullenweg has also spent the last several days [Posting Through It on Reddit](https://old.reddit.com/user/photomatt) (link goes to his user page, which should make all comments visible). (Note that many of these comments were posted significantly after his receipt of the C&D letter from WP Engine.)
    * Mullenweg has also spent the last several days [Posting Through It on Reddit](https://old.reddit.com/user/photomatt) (link goes to his user page, which should make all comments visible). (Note that many of these comments were posted significantly after his receipt of the C&D letter from WP Engine.)
    * Mullenweg is reportedly also [privately exhorting Automattic employees](https://x.com/ryancduff/status/1838961425647063047) to make supportive posts on their own blogs and social media. There may or may not be an implication that they will be retaliated against if they choose not to do so; reports vary.
  8. adrienne revised this gist Sep 26, 2024. 1 changed file with 1 addition and 0 deletions.
    1 change: 1 addition & 0 deletions mullenweg-wpe.md
    View file
    Original file line number Diff line number Diff line change
    @@ -9,6 +9,7 @@
    * WP Engine's letter alleges, among other things, that Mullenweg demanded money from WP Engine ostensibly as a licensing fee for the WordPress trademark, but in actuality to refrain from disparaging and defaming them on stage and in blog posts.
    * Not alleged in the letter, but reported by attendees to WordCamp, is that Mullenweg engaged in a verbal altercation with WP Engine employees working the WP Engine booth at the show, which included Mullenweg threatening to physically dismantle their booth in the middle of the show. (I can't find my link to this right now, i'll look for it later.)
    * Automattic sends [a C&D letter of its own](https://automattic.com/2024/wp-engine-cease-and-desist.pdf) to WP Engine, demanding that they stop misusing the WordPress trademark. (Note that the WordPress *Foundation* is the trademark owner, and Automattic is the sole commercial licensee.)
    * Prompted by Mullenweg's multiple blog posts, which get automatically propagated to every WordPress user with the "News Feed" widget on their admin dashboard (which is most WordPress users, as very few actually modify their dashboard), WP Engine disables the "News Feed" dashboard widget for all its customers. (Note that is a simple config change, supported by WordPress; it does not involve modifying any code or otherwise "chopping up" WordPress installs.)
    * A day after Automattic sends the C&D, the wordpress.**org** domain (again, maintained by the WordPress *Foundation*), [blocks WP Engine](https://techcrunch.com/2024/09/25/wordpress-org-bans-wp-engine-blocks-it-from-accessing-its-resources/) (and thence all of their customers) from accessing the plugin/theme/update repository. This means that none of WP Engine's customers can install plugins or themes, update plugins or themes, *or update WordPress itself*, including vital security patches. Additionally, all WP Engine user accounts are reportedly banned from the wordpress.**org** site, meaning they cannot post to the forum or update the plugins which they maintain as an organization. (Need to find the link on this one too.)
    * [Mullenweg posts](https://wordpress.org/news/2024/09/wp-engine-banned/) about this decision, again to the wordpress.**org** blog, and includes the following statement: "**What I will tell you is that, pending their legal claims and litigation against WordPress.org, WP Engine no longer has free access to WordPress.org’s resources.**"
    * Note, here, that WP Engine's C&D was sent to Automattic, which runs wordpress.**com**, and at no point has WP Engine made *any legal claims whatsoever* against wordpress.**org** or the WordPress Foundation.
  9. adrienne revised this gist Sep 26, 2024. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion mullenweg-wpe.md
    View file
    Original file line number Diff line number Diff line change
    @@ -13,4 +13,4 @@
    * [Mullenweg posts](https://wordpress.org/news/2024/09/wp-engine-banned/) about this decision, again to the wordpress.**org** blog, and includes the following statement: "**What I will tell you is that, pending their legal claims and litigation against WordPress.org, WP Engine no longer has free access to WordPress.org’s resources.**"
    * Note, here, that WP Engine's C&D was sent to Automattic, which runs wordpress.**com**, and at no point has WP Engine made *any legal claims whatsoever* against wordpress.**org** or the WordPress Foundation.
    * Meanwhile, Pressable (another web hosting company _also wholly owned by Automattic_), [posts a special offer for WP Engine users](https://archive.is/Ybnmi), offering to buy out their contracts and migrate them for free. (The above is an archival link; at the time of writing, the offer is live and [linked here](https://pressable.com/wpe-contract-buyout/).)
    * Mullenweg has also spent the last several days [Posting Through It on Reddit](https://old.reddit.com/user/photomatt) (link goes to his user page, which should make all comments visible).
    * Mullenweg has also spent the last several days [Posting Through It on Reddit](https://old.reddit.com/user/photomatt) (link goes to his user page, which should make all comments visible). (Note that many of these comments were posted significantly after his receipt of the C&D letter from WP Engine.)
  10. adrienne created this gist Sep 26, 2024.
    16 changes: 16 additions & 0 deletions mullenweg-wpe.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,16 @@
    # The Players
    * [The WordPress Foundation](https://wordpressfoundation.org) is the nonprofit which manages the WordPress code and ecosystem. It theoretically maintains the wordpress.**org** website (the domain, however, is [owned by Matt Mullenweg](https://wp-content.co/bay-lights/) rather than by the Foundation), which acts as the central repository for all updates, themes, and plugins, as well as managing the WordPress documentation and maintaining a large discussion forum for WordPress devs and users. The Foundation is administered by [a board of three people, one of whom is Matt Mullenweg](https://www.pluginvulnerabilities.com/2024/09/24/who-is-on-the-wordpress-foundation-board/).
    * [Automattic](https://automattic.com) is the for-profit arm of WordPress, which maintains the wordpress.**com** web host as well as offering a number of other free and paid addons to WordPress. Matt Mullenweg is the CEO and a member of the Board of Directors, and controls a majority of voting shares in the organization.
    * [WP Engine](https://wpengine.com) is a company which offers managed hosting for WordPress sites. They are a major player in the WP hosting space. It is important to note that the phrase "managed hosting" specifically implies a high level of control by the hosting company over the software and infrastructure; managed hosting services are geared toward less-technical clients and clients who want to offload server administration stuff. People who are purchasing managed hosting, as opposed to unmanaged hosting, are *specifically buying* the higher level of control by the hosting provider, because it means fewer hassles for them.

    # The Story So Far

    * [TechCrunch has solid reporting](https://techcrunch.com/2024/09/22/matt-mullenweg-calls-wp-engine-a-cancer-to-wordpress-and-urges-community-to-switch-providers/) on the [initial events](https://techcrunch.com/2024/09/23/wp-engine-sends-cease-and-desist-letter-to-automattic-over-mullenwegs-comments/): Mullenweg's initial blog post, his WordCamp keynote, his second blog post, and [WP Engine's C&D letter](https://wpengine.com/wp-content/uploads/2024/09/Cease-and-Desist-Letter-to-Automattic-and-Request-to-Preserve-Documents-Sent.pdf). The blog posts are posted to the wordpress.**org** blog, not to Automattic's blog.
    * WP Engine's letter alleges, among other things, that Mullenweg demanded money from WP Engine ostensibly as a licensing fee for the WordPress trademark, but in actuality to refrain from disparaging and defaming them on stage and in blog posts.
    * Not alleged in the letter, but reported by attendees to WordCamp, is that Mullenweg engaged in a verbal altercation with WP Engine employees working the WP Engine booth at the show, which included Mullenweg threatening to physically dismantle their booth in the middle of the show. (I can't find my link to this right now, i'll look for it later.)
    * Automattic sends [a C&D letter of its own](https://automattic.com/2024/wp-engine-cease-and-desist.pdf) to WP Engine, demanding that they stop misusing the WordPress trademark. (Note that the WordPress *Foundation* is the trademark owner, and Automattic is the sole commercial licensee.)
    * A day after Automattic sends the C&D, the wordpress.**org** domain (again, maintained by the WordPress *Foundation*), [blocks WP Engine](https://techcrunch.com/2024/09/25/wordpress-org-bans-wp-engine-blocks-it-from-accessing-its-resources/) (and thence all of their customers) from accessing the plugin/theme/update repository. This means that none of WP Engine's customers can install plugins or themes, update plugins or themes, *or update WordPress itself*, including vital security patches. Additionally, all WP Engine user accounts are reportedly banned from the wordpress.**org** site, meaning they cannot post to the forum or update the plugins which they maintain as an organization. (Need to find the link on this one too.)
    * [Mullenweg posts](https://wordpress.org/news/2024/09/wp-engine-banned/) about this decision, again to the wordpress.**org** blog, and includes the following statement: "**What I will tell you is that, pending their legal claims and litigation against WordPress.org, WP Engine no longer has free access to WordPress.org’s resources.**"
    * Note, here, that WP Engine's C&D was sent to Automattic, which runs wordpress.**com**, and at no point has WP Engine made *any legal claims whatsoever* against wordpress.**org** or the WordPress Foundation.
    * Meanwhile, Pressable (another web hosting company _also wholly owned by Automattic_), [posts a special offer for WP Engine users](https://archive.is/Ybnmi), offering to buy out their contracts and migrate them for free. (The above is an archival link; at the time of writing, the offer is live and [linked here](https://pressable.com/wpe-contract-buyout/).)
    * Mullenweg has also spent the last several days [Posting Through It on Reddit](https://old.reddit.com/user/photomatt) (link goes to his user page, which should make all comments visible).