From b04386905990aa35e7d710e6492f86ca09848f06 Mon Sep 17 00:00:00 2001 From: Kathleen Fitzpatrick <3170201+kfitz@users.noreply.github.com> Date: Wed, 18 Nov 2026 16:16:28 -0500 Subject: [PATCH] add free and sustainable --- blog/index.html | 5 + feed/feed.xml | 51 +- feed/masto.xml | 11 +- free-sustainable/index.html | 709 +++++++++++++++++++++++ in-the-wake/index.html | 36 +- index.html | 14 +- pagefind/fragment/en_2ba845e.pf_fragment | Bin 0 -> 531 bytes pagefind/fragment/en_3e9e2ac.pf_fragment | Bin 0 -> 4472 bytes pagefind/fragment/en_713b061.pf_fragment | Bin 0 -> 23836 bytes pagefind/fragment/en_822d96e.pf_fragment | Bin 0 -> 2352 bytes pagefind/fragment/en_cfae82d.pf_fragment | Bin 0 -> 395 bytes pagefind/fragment/en_e9ed7b2.pf_fragment | Bin 0 -> 241 bytes pagefind/fragment/en_fae8818.pf_fragment | Bin 0 -> 604 bytes pagefind/index/en_11d88b7.pf_index | Bin 0 -> 28119 bytes pagefind/index/en_15ede15.pf_index | Bin 0 -> 29424 bytes pagefind/index/en_167becf.pf_index | Bin 0 -> 28195 bytes pagefind/index/en_18217a9.pf_index | Bin 0 -> 28456 bytes pagefind/index/en_1bbc1a1.pf_index | Bin 0 -> 27375 bytes pagefind/index/en_24286a7.pf_index | Bin 0 -> 25353 bytes pagefind/index/en_2a9daca.pf_index | Bin 0 -> 28891 bytes pagefind/index/en_2c1aa68.pf_index | Bin 0 -> 27380 bytes pagefind/index/en_2c66221.pf_index | Bin 0 -> 31176 bytes pagefind/index/en_2ff2896.pf_index | Bin 0 -> 29838 bytes pagefind/index/en_3184af2.pf_index | Bin 0 -> 30915 bytes pagefind/index/en_39fd250.pf_index | Bin 0 -> 27325 bytes pagefind/index/en_3a76a6f.pf_index | Bin 0 -> 23705 bytes pagefind/index/en_3e62cbf.pf_index | Bin 0 -> 33368 bytes pagefind/index/en_407ee54.pf_index | Bin 0 -> 31854 bytes pagefind/index/en_475dbe8.pf_index | Bin 0 -> 29651 bytes pagefind/index/en_49e82e3.pf_index | Bin 0 -> 30885 bytes pagefind/index/en_4d7fa72.pf_index | Bin 0 -> 30311 bytes pagefind/index/en_4dc6d84.pf_index | Bin 0 -> 30393 bytes pagefind/index/en_4f775eb.pf_index | Bin 0 -> 26652 bytes pagefind/index/en_4f883f5.pf_index | Bin 0 -> 51530 bytes pagefind/index/en_5170df1.pf_index | Bin 0 -> 21664 bytes pagefind/index/en_552c29e.pf_index | Bin 0 -> 28874 bytes pagefind/index/en_564b1f2.pf_index | Bin 0 -> 30732 bytes pagefind/index/en_5bed12b.pf_index | Bin 0 -> 24508 bytes pagefind/index/en_64bd333.pf_index | Bin 0 -> 29026 bytes pagefind/index/en_6a36cd4.pf_index | Bin 0 -> 28656 bytes pagefind/index/en_6b28293.pf_index | Bin 0 -> 35616 bytes pagefind/index/en_70f896c.pf_index | Bin 0 -> 27682 bytes pagefind/index/en_759c9e1.pf_index | Bin 0 -> 28904 bytes pagefind/index/en_7627cf2.pf_index | Bin 0 -> 53947 bytes pagefind/index/en_7ff5fe2.pf_index | Bin 0 -> 26009 bytes pagefind/index/en_8611476.pf_index | Bin 0 -> 24879 bytes pagefind/index/en_898f0a6.pf_index | Bin 0 -> 30637 bytes pagefind/index/en_946a88c.pf_index | Bin 0 -> 21850 bytes pagefind/index/en_98dc1f5.pf_index | Bin 0 -> 26203 bytes pagefind/index/en_9d3d91d.pf_index | Bin 0 -> 27966 bytes pagefind/index/en_a0b8636.pf_index | Bin 0 -> 28071 bytes pagefind/index/en_a0f2f91.pf_index | Bin 0 -> 20438 bytes pagefind/index/en_a567d85.pf_index | Bin 0 -> 32572 bytes pagefind/index/en_a589baf.pf_index | Bin 0 -> 27844 bytes pagefind/index/en_a5b58af.pf_index | Bin 0 -> 27921 bytes pagefind/index/en_a71f10a.pf_index | Bin 0 -> 29983 bytes pagefind/index/en_a89d7c7.pf_index | Bin 0 -> 22749 bytes pagefind/index/en_a9c4ba1.pf_index | Bin 0 -> 30425 bytes pagefind/index/en_aef2e21.pf_index | Bin 0 -> 22004 bytes pagefind/index/en_b582be9.pf_index | Bin 0 -> 44421 bytes pagefind/index/en_bc46f98.pf_index | Bin 0 -> 29140 bytes pagefind/index/en_bd34143.pf_index | Bin 0 -> 30007 bytes pagefind/index/en_c666d03.pf_index | Bin 0 -> 33080 bytes pagefind/index/en_c78517f.pf_index | Bin 0 -> 37721 bytes pagefind/index/en_ca2bb2e.pf_index | Bin 0 -> 28608 bytes pagefind/index/en_cab8d29.pf_index | Bin 0 -> 27545 bytes pagefind/index/en_d01322f.pf_index | Bin 0 -> 31547 bytes pagefind/index/en_d1f3135.pf_index | Bin 0 -> 28049 bytes pagefind/index/en_d822973.pf_index | Bin 0 -> 29341 bytes pagefind/index/en_d8f9745.pf_index | Bin 0 -> 25356 bytes pagefind/index/en_ddc424d.pf_index | Bin 0 -> 26638 bytes pagefind/index/en_e04c4f5.pf_index | Bin 0 -> 26286 bytes pagefind/index/en_e37a968.pf_index | Bin 0 -> 22164 bytes pagefind/index/en_fc3bc41.pf_index | Bin 0 -> 28959 bytes pagefind/index/en_fd2e7d3.pf_index | Bin 0 -> 31256 bytes pagefind/index/en_feac744.pf_index | Bin 0 -> 29041 bytes pagefind/index/en_fffb358.pf_index | Bin 0 -> 29015 bytes pagefind/pagefind-component-ui.css | 10 +- pagefind/pagefind-component-ui.js | 18 +- pagefind/pagefind-entry.json | 2 +- pagefind/pagefind-highlight.js | 6 +- pagefind/pagefind-ui.js | 4 +- pagefind/pagefind-worker.js | 4 +- pagefind/pagefind.en_18e3c28af9.pf_meta | Bin 0 -> 14807 bytes pagefind/pagefind.js | 4 +- pagefind/wasm.en.pagefind | Bin 72740 -> 59738 bytes pagefind/wasm.unknown.pagefind | Bin 68199 -> 55400 bytes sitemap.xml | 7 +- tags/commons/index.html | 7 +- tags/index.html | 3 + tags/sustainability/index.html | 564 ++++++++++++++++++ 91 files changed, 1392 insertions(+), 63 deletions(-) create mode 100644 free-sustainable/index.html create mode 100644 pagefind/fragment/en_2ba845e.pf_fragment create mode 100644 pagefind/fragment/en_3e9e2ac.pf_fragment create mode 100644 pagefind/fragment/en_713b061.pf_fragment create mode 100644 pagefind/fragment/en_822d96e.pf_fragment create mode 100644 pagefind/fragment/en_cfae82d.pf_fragment create mode 100644 pagefind/fragment/en_e9ed7b2.pf_fragment create mode 100644 pagefind/fragment/en_fae8818.pf_fragment create mode 100644 pagefind/index/en_11d88b7.pf_index create mode 100644 pagefind/index/en_15ede15.pf_index create mode 100644 pagefind/index/en_167becf.pf_index create mode 100644 pagefind/index/en_18217a9.pf_index create mode 100644 pagefind/index/en_1bbc1a1.pf_index create mode 100644 pagefind/index/en_24286a7.pf_index create mode 100644 pagefind/index/en_2a9daca.pf_index create mode 100644 pagefind/index/en_2c1aa68.pf_index create mode 100644 pagefind/index/en_2c66221.pf_index create mode 100644 pagefind/index/en_2ff2896.pf_index create mode 100644 pagefind/index/en_3184af2.pf_index create mode 100644 pagefind/index/en_39fd250.pf_index create mode 100644 pagefind/index/en_3a76a6f.pf_index create mode 100644 pagefind/index/en_3e62cbf.pf_index create mode 100644 pagefind/index/en_407ee54.pf_index create mode 100644 pagefind/index/en_475dbe8.pf_index create mode 100644 pagefind/index/en_49e82e3.pf_index create mode 100644 pagefind/index/en_4d7fa72.pf_index create mode 100644 pagefind/index/en_4dc6d84.pf_index create mode 100644 pagefind/index/en_4f775eb.pf_index create mode 100644 pagefind/index/en_4f883f5.pf_index create mode 100644 pagefind/index/en_5170df1.pf_index create mode 100644 pagefind/index/en_552c29e.pf_index create mode 100644 pagefind/index/en_564b1f2.pf_index create mode 100644 pagefind/index/en_5bed12b.pf_index create mode 100644 pagefind/index/en_64bd333.pf_index create mode 100644 pagefind/index/en_6a36cd4.pf_index create mode 100644 pagefind/index/en_6b28293.pf_index create mode 100644 pagefind/index/en_70f896c.pf_index create mode 100644 pagefind/index/en_759c9e1.pf_index create mode 100644 pagefind/index/en_7627cf2.pf_index create mode 100644 pagefind/index/en_7ff5fe2.pf_index create mode 100644 pagefind/index/en_8611476.pf_index create mode 100644 pagefind/index/en_898f0a6.pf_index create mode 100644 pagefind/index/en_946a88c.pf_index create mode 100644 pagefind/index/en_98dc1f5.pf_index create mode 100644 pagefind/index/en_9d3d91d.pf_index create mode 100644 pagefind/index/en_a0b8636.pf_index create mode 100644 pagefind/index/en_a0f2f91.pf_index create mode 100644 pagefind/index/en_a567d85.pf_index create mode 100644 pagefind/index/en_a589baf.pf_index create mode 100644 pagefind/index/en_a5b58af.pf_index create mode 100644 pagefind/index/en_a71f10a.pf_index create mode 100644 pagefind/index/en_a89d7c7.pf_index create mode 100644 pagefind/index/en_a9c4ba1.pf_index create mode 100644 pagefind/index/en_aef2e21.pf_index create mode 100644 pagefind/index/en_b582be9.pf_index create mode 100644 pagefind/index/en_bc46f98.pf_index create mode 100644 pagefind/index/en_bd34143.pf_index create mode 100644 pagefind/index/en_c666d03.pf_index create mode 100644 pagefind/index/en_c78517f.pf_index create mode 100644 pagefind/index/en_ca2bb2e.pf_index create mode 100644 pagefind/index/en_cab8d29.pf_index create mode 100644 pagefind/index/en_d01322f.pf_index create mode 100644 pagefind/index/en_d1f3135.pf_index create mode 100644 pagefind/index/en_d822973.pf_index create mode 100644 pagefind/index/en_d8f9745.pf_index create mode 100644 pagefind/index/en_ddc424d.pf_index create mode 100644 pagefind/index/en_e04c4f5.pf_index create mode 100644 pagefind/index/en_e37a968.pf_index create mode 100644 pagefind/index/en_fc3bc41.pf_index create mode 100644 pagefind/index/en_fd2e7d3.pf_index create mode 100644 pagefind/index/en_feac744.pf_index create mode 100644 pagefind/index/en_fffb358.pf_index create mode 100644 pagefind/pagefind.en_18e3c28af9.pf_meta create mode 100644 tags/sustainability/index.html diff --git a/blog/index.html b/blog/index.html index d1e5b969b..0ce3c96c0 100644 --- a/blog/index.html +++ b/blog/index.html @@ -543,6 +543,11 @@ pre[class*="language-diff-"] {
2026
    +
  1. + Free and Sustainable
    + +
  2. +
  3. In the Wake
    diff --git a/feed/feed.xml b/feed/feed.xml index 1fa00de0e..b80cfa040 100644 --- a/feed/feed.xml +++ b/feed/feed.xml @@ -5,11 +5,27 @@ The long-running and erratically updated blog of Kathleen Fitzpatrick. - 2026-10-09T18:45:24Z + 2026-11-18T20:56:25Z https://kfitz.info/ Kathleen Fitzpatrick + + Free and Sustainable + + 2026-11-18T20:56:25Z + https://kfitz.info/free-sustainable/ + <p><em>Crossposted from the <a href="https://about.hcommons.org/2026/11/18/free-and-sustainable/">Knowledge Commons team blog</a>.</em></p> +<p>My colleague Martin Eve was <a href="https://bsky.app/profile/did:plc:hnpt7ns2lecdujegbi6qkqqm/post/3n2dpljhmae2b">speculating on Bluesky</a> the other day that while he has enjoyed Tailscale's robust free plan, he should probably think about signing up a for a paid offering to ensure that this ridiculously useful service is able to stay sustainable. Someone responded with a link to Tailscale's own post, from 2022, exploring <a href="https://tailscale.com/blog/free-plan">how the free plan is able to remain free</a>. It's a fantastic look behind the curtain at their financial modeling and business design. The long and the short of it is that they can remain free to end users for their individual use because many of those happy end users are then able to persuade their companies to subscribe to paid accounts. This mode of &quot;bottom-up marketing&quot; allows them to keep their customer acquisition costs very low and focus their investments on product development and service scaling.</p> +<p>I read this post with great interest not just because I too have a free Tailscale account and have been a little worried about how long I'd be able to get away with that, but also because the model of free-to-individuals, supported-by-organizations is exactly what we're building for Knowledge Commons. We are committed to keeping that free tier free -- we are, after all, an open-source, open-access, values-first nonprofit organization -- but like Tailscale, we need a paid tier to make the platform sustainable.</p> +<p>Martin pointed out to me in discussion that one key difference is that Tailscale has by default a somewhat affluent user base -- users with multiple devices and the desire to connect them into a secure network. And those interests tend to indicate that the average Tailscale user is likely to be working in a technical capacity, and if they're happy with the service they're likely to recommend it to their co-workers, and at some point suggest to their bosses that their work environment might benefit from it, and somewhere in that chain it's not at all unlikely that they'll have the ear of someone with the company buying power to sign up for a paid tier of service.</p> +<p>Knowledge Commons is different in nearly all of these respects. While many of our users have extensive technical knowledge, the tech community isn’t our target audience. Scholars and practitioners work in a far broader range of organizational contexts, and we want all of them to feel a sense of belonging within an open, collective community, where independent scholars are just as welcome as tenured professors, and where users need not be working in a specifically technical position in order to make active use of our services.</p> +<p>However, we still need to find ways to make connections between our individual users and the folks who have the capacity to support us. At the individual level, of course, we have the <a href="https://about.hcommons.org/kc-champions/">KC Champions program</a>, which encourages users who might benefit from some extra services to join us and, in so doing, help keep the platform’s free tier thriving. But we also need institutional and organizational memberships in order to enable the platform to achieve real sustainability, and figuring out how to connect to the right people at those institutions can be hard – especially when a cold email from our team can feel like yet another message from yet another vendor trying to sell yet another commercial product to institutions with already stressed budgets.</p> +<p>This is where we need your help. The most important thing that our individual users can do for us is talk to others about Knowledge Commons. We’ve got some <a href="https://about.hcommons.org/become-a-commons-ambassador/">resources available</a> that might help you get started. Tell your colleagues why and how you use the platform and encourage them to use it as well. Tell your instructional technology or library services contacts about us and why you think it would be great for your institution to think about adopting nonprofit, community-governed alternatives to the kinds of corporate platforms that so many are currently using. And then let us know you’ve done so! If you can share your contact’s information with us (by emailing <a href="mailto:network@hcommons.org">network@hcommons.org</a>), we can follow up to offer a demo or a campus visit as well as any other information that’s helpful to your institution’s deciders.</p> +<p>The point is this: the Knowledge Commons team is ready to support your institution, but we need your help with starting the conversation. Together, we can help keep our free tier robust while still reaching sustainability.</p> +<p>So how can we help you help us with that process? If you have thoughts to share about how we can collectively get the word out about Knowledge Commons, please share them in the comments!</p> + + In the Wake @@ -243,39 +259,6 @@ </li> </ol> </section> - - - - Networking Continued - - 2025-08-09T20:38:09Z - https://kfitz.info/networking-continued/ - <p>As you may recall, I've been experimenting with setting up a home server, and several months ago had gotten stuck on an issue related to <a href="https://kfitz.info/networking/">the structure of my network</a>. <a href="https://kfitz.info/networking/?ht-comment-id=26755687">Taylor hopped in</a> and really helped me understand how everything <em>ought</em> to work.</p> -<p>But it's not working. And I'm again flummoxed.</p> -<p>Here's the setup:</p> -<ol> -<li>I have my ISP's modem/router/gateway monstrosity (the BGW320) running in IP Passthrough mode, with the WAN IP address being passed to my gateway Eero.</li> -<li>I have my Eeros set to Automatic DHCP mode; the gateway Eero is successfully getting the WAN IP address and is handing out private IP addresses in the 192.168.4.X range.</li> -<li>I have a registered domain name (let's say <code>example.net</code>), and I have an A record at my DNS service pointing to my WAN IP address. I have also created a subdomain A record (<code>service</code>) pointing to the same IP address. DNS Checker gives me all green checks for both.</li> -<li>I have a mini server, running Proxmox.</li> -<li>I have installed Nginx Proxy Manager in a container on the Proxmox (an LXC), which is running and reachable at the static address 192.168.4.11.</li> -<li>I have installed the service I'm trying to expose in another LXC, which is running and reachable at the static address 192.168.4.12.</li> -<li>I have set up port forwarding on my Eero network for ports 80 and 443 to <s>198</s>192.168.4.11.</li> -<li>I have created a proxy host in NPM, for which all the dots are green: -<ul> -<li>Domain Name: <a href="http://service.example.net">service.example.net</a></li> -<li>Scheme: http</li> -<li>Forward Hostname/IP: 192.168.4.12</li> -<li>Forward Port: <code>port</code></li> -<li>Block Common Exploits and Websockets Support on</li> -<li>Access List: Publicly Accessible</li> -</ul> -</li> -</ol> -<p>But <code>http://service.example.net:port</code> refuses to connect, as does <code>http://example.net</code>, either from my local network or through my VPN. And <code>traceroute</code> to either <code>example.net</code> or <code>service.example.net</code> stalls out.</p> -<p>I've checked the Proxmox firewall and inbound 80 and 443 are both set to accept. I've checked to see whether my ISP's montrosity's firewall could be blocking those ports but... who's to say. The NAT/Gaming (sigh) panel of the admin interface isn't showing the gateway Eero as a device that could need anything in particular sent its way, so my assumption is that IP Passthrough passes inbound requests through for the Eero to sort out, too.</p> -<p>I've searched around, and the nearest thing I've found to what I'm trying to do and how I'm trying to do it is in <a href="https://www.reddit.com/r/Proxmox/comments/u857x5/nginx_proxy_manager_setup_troubles/">this Reddit thread</a>, but the problem in that case is back at the beginning with the A record, which is definitely not my issue, unless I spelled my domain name wrong at the DNS. (I didn't.) And that person was able to get to the NPM congratulations page; my connections get refused entirely.</p> -<p>If anybody sees anything that I should adjust, or take a look at adjusting, I'd be grateful to hear. I'm already <em>this</em> close to dumping my ISP anyhow due to some ongoing service issues, and getting rid of their annoying modem/router/gateway would be a bonus, but I'm not entirely certain that it's the problem, and I'd love to find a way through without taking that step.</p> \ No newline at end of file diff --git a/feed/masto.xml b/feed/masto.xml index 7cb72db5f..d8ec40df9 100644 --- a/feed/masto.xml +++ b/feed/masto.xml @@ -540,13 +540,22 @@ pre[class*="language-diff-"] { The long-running and erratically updated blog of Kathleen Fitzpatrick. - 2026-10-09T18:45:24Z + 2026-11-18T20:56:25Z https://kfitz.info/ Kathleen Fitzpatrick kfitz@kfitz.info + + Free and Sustainable + + 2026-11-18T20:56:25Z + https://kfitz.info/free-sustainable/ + Crossposted from the Knowledge Commons team blog.
    +My colleague Martin Eve was
    +
    + In the Wake diff --git a/free-sustainable/index.html b/free-sustainable/index.html new file mode 100644 index 000000000..0321c9d7a --- /dev/null +++ b/free-sustainable/index.html @@ -0,0 +1,709 @@ + + + + + + Free and Sustainable + + + + + + + + + + + + + + Skip to main content + +
    + kfitz + +
    + + +
    + + +

    Free and Sustainable

    + + + +

    Crossposted from the Knowledge Commons team blog.

    +

    My colleague Martin Eve was speculating on Bluesky the other day that while he has enjoyed Tailscale's robust free plan, he should probably think about signing up a for a paid offering to ensure that this ridiculously useful service is able to stay sustainable. Someone responded with a link to Tailscale's own post, from 2022, exploring how the free plan is able to remain free. It's a fantastic look behind the curtain at their financial modeling and business design. The long and the short of it is that they can remain free to end users for their individual use because many of those happy end users are then able to persuade their companies to subscribe to paid accounts. This mode of "bottom-up marketing" allows them to keep their customer acquisition costs very low and focus their investments on product development and service scaling.

    +

    I read this post with great interest not just because I too have a free Tailscale account and have been a little worried about how long I'd be able to get away with that, but also because the model of free-to-individuals, supported-by-organizations is exactly what we're building for Knowledge Commons. We are committed to keeping that free tier free -- we are, after all, an open-source, open-access, values-first nonprofit organization -- but like Tailscale, we need a paid tier to make the platform sustainable.

    +

    Martin pointed out to me in discussion that one key difference is that Tailscale has by default a somewhat affluent user base -- users with multiple devices and the desire to connect them into a secure network. And those interests tend to indicate that the average Tailscale user is likely to be working in a technical capacity, and if they're happy with the service they're likely to recommend it to their co-workers, and at some point suggest to their bosses that their work environment might benefit from it, and somewhere in that chain it's not at all unlikely that they'll have the ear of someone with the company buying power to sign up for a paid tier of service.

    +

    Knowledge Commons is different in nearly all of these respects. While many of our users have extensive technical knowledge, the tech community isn’t our target audience. Scholars and practitioners work in a far broader range of organizational contexts, and we want all of them to feel a sense of belonging within an open, collective community, where independent scholars are just as welcome as tenured professors, and where users need not be working in a specifically technical position in order to make active use of our services.

    +

    However, we still need to find ways to make connections between our individual users and the folks who have the capacity to support us. At the individual level, of course, we have the KC Champions program, which encourages users who might benefit from some extra services to join us and, in so doing, help keep the platform’s free tier thriving. But we also need institutional and organizational memberships in order to enable the platform to achieve real sustainability, and figuring out how to connect to the right people at those institutions can be hard – especially when a cold email from our team can feel like yet another message from yet another vendor trying to sell yet another commercial product to institutions with already stressed budgets.

    +

    This is where we need your help. The most important thing that our individual users can do for us is talk to others about Knowledge Commons. We’ve got some resources available that might help you get started. Tell your colleagues why and how you use the platform and encourage them to use it as well. Tell your instructional technology or library services contacts about us and why you think it would be great for your institution to think about adopting nonprofit, community-governed alternatives to the kinds of corporate platforms that so many are currently using. And then let us know you’ve done so! If you can share your contact’s information with us (by emailing network@hcommons.org), we can follow up to offer a demo or a campus visit as well as any other information that’s helpful to your institution’s deciders.

    +

    The point is this: the Knowledge Commons team is ready to support your institution, but we need your help with starting the conversation. Together, we can help keep our free tier robust while still reaching sustainability.

    +

    So how can we help you help us with that process? If you have thoughts to share about how we can collectively get the word out about Knowledge Commons, please share them in the comments!

    + + + + + +
    +

    Webmentions

    + + +

    No replies yet.

    + + + + + + + + + +
    + + +
    +
    + + + + + + diff --git a/in-the-wake/index.html b/in-the-wake/index.html index 9ded3d3ac..30dc8c68c 100644 --- a/in-the-wake/index.html +++ b/in-the-wake/index.html @@ -692,7 +692,7 @@ hr.new {

    What further questions do you have? Let us know in the comments; we'd very much like to keep a discussion of these issues going.

    And again, we thank you for your support, and we apologize for the inconvenience that this hack and the resulting process of remediation created. We continue to focus on doing better for all of our community members.

    -