Zach Into 2020


  • 2 people per meal
  • Every 3 days responsible for meal
  • Breakfast on own
  • 10:30 AM start time
  • Team that didn’t cook cleans


Knowledge and education is an issue.


  • All dishes cleaned or in dishwasher
  • All pots and pans cleaned or in dishwasher
  • All food put away
  • Stove wiped
  • Sink and drain are cleared out
  • Main counter cleared
  • Main counter wiped
  • Floor cleared
  • All meal related items off dining table
  • Dining table wiped if needed
  • Dishwasher started
  • Trash and recycling taken out if full

Better documentation for systemd

Idea: Better documentation for systemd. is incredibly confusing.

I can’t even figure out what section After and Wants goes in.

I want examples. I want to see how to make scheduled jobs. I want to see how to make one service depend on another service. I want to see where to put files for custom services that I define Examples, examples, examples.


Stuck in the middle. On China’s side or not? What is the opposition?

The US? Europe? Current opposition is not working. What can opposition do that China can’t? What can China do that opposition can’t?

Really scary stuff. Need to think more about Hack Club in terms of setting up systems to build out the org that I want to exist rather than just trying to do it all myself.

What is the next 20 years going to look like? When we look back on this time in 100 years, what are the history books going to say? What are the arcs of our time?

AI? Is it for real?

Start with Middle East, but probably overemphasized when comparing to the historical perspective.

From 1910, before everything changed in the 20th century.

  • Portugal 1494 to 1580 (end of Italian Wars to Spanish-Portuguese Union). Based on Portugal’s dominance in navigation.
  • Spain 1516 to 1659 (Ascension of Charles I of Spain to Treaty of the Pyrenees). Based on the Spanish dominance of the European battlefields and the global exploration and colonization of the New World.
  • The Netherlands 1580 to 1688 (1579 Treaty of Utrecht marks the foundation of the Dutch Republic to the Glorious Revolution, William of Orange’s arrival in England). Based on Dutch control of credit and money.
  • Britain 1688 to 1792 (Glorious Revolution to Napoleonic Wars). Based on British textiles and command of the high seas.
  • Britain 1815 to 1914 (Congress of Vienna to World War I). Based on British industrial supremacy and railroads.


How I got LTE working on my X1 Carbon (7th Gen) ThinkPad on Arch Linux

Note: does not work automatically through suspends. After resuming from a suspend, I need to run the following and wait a bit for the modem to show up again (as root):

setpci -s "0000:00:1c.0" "CAP_EXP+10.w=0052"
printf "%s" "\_SB_.PCI0.RP01.PXSX._RST" > /proc/acpi/call

I have struggled to get LTE working in Arch Linux on my new X1 Carbon (7th Gen) on Arch Linux. Thanks to @pradyungn on the Hack Club Slack for helping me out with this.

This is what ultimately worked for me:

$ uname -r

Install kernel module to convert modem to USB mode permanently on Linux:

  1. Clone
  2. make && sudo make install && sudo modprobe xmm7360_usb
  3. After modem boots into USB mode, unlock modem and set to MBIM mode (whatever that is, _this step is taken from xmm7360_usb‘s README)
$ sudo screen /dev/ttyACM0

…then type in, one line at a time, the following:


If you have previously messed around with ModemManager trying to get LTE working, make sure that ModemManager.service is not running because it will mess with your ability to run the above commands.

Now set it up with your system. You must be using NetworkManager to manage your computer’s networking for the following steps to work. I switched from using netctl to NetworkManager to get this to work (I couldn’t figure out the configuration files for netctl).

  1. Install modemmanager and modem-manager-gui
  2. Run sudo systemctl enable --now ModemManager
  3. Launch Modem Manager GUI. You should see something like the following:

    If you do, green light. Good signs so far.

  4. Run nm-connection-editor, create a new Mobile Broadband network, and follow the steps for your SIM card
  5. Run nmtui > Activate a connection > Activate the LTE connection you just set it.

It should all be working now! At least it did for me by this point.

Notes: I also tried manually following the steps in and couldn’t figure it out, likely an issue on my end. I also tried out and similarly struggled to get it working.

Working For NearlyFreeSpeech.NET


Due to the incredible amount of our members’ private information and content we handle, and the number and nature of people who want it, trust is a real issue. Consequently, NearlyFreeSpeech.NET operates under the Keyser Söze school of management. (Albeit with a lot less bloodshed and arson, most days.) We strictly compartmentalize projects and ruthlessly limit access to our production databases and systems.

To give a contrived example of how this works, if we needed member files backed up, we would not hire a system administrator to backup member files. We might hire someone to develop and maintain an automated system for backing up files. That system would be developed in isolation. Then, after code review and testing, we would deploy that system to back up member files. The person responsible for the system would thus never gain access to member files, even though that task can’t be completed without that access. The end result is a lot like we bought an off-the-shelf system that does exactly what we need from a vendor with really good support. (Which is also an option we pursue, on those rare occasions when it exists.)

This means that we do not have any traditional employees. Almost all of the day-to-day operational work is (where possible) done directly by the owners or by select highly-qualified vendors. When additional work is needed, we work with equally qualified independent contractors. In order to do this, a high level of information isolation is used. Although we joke that this means a person could be doing work for us and not even know it, in practice it means that they may be doing the work under an agreement with an intermediary, and they will typically be working on testbed systems with no real data on them.

Where work opportunities exist, we do not post them on our site. We prefer to identify and recruit specific individuals, often based on their relevant open source work or other demonstrated expertise. Sometimes we also make small, isolated projects available in venues where good candidates are likely to be found in an effort to flush them out. So, if you have exactly the mix of expertise, incredible skills, steadfast discretion, and willingness to work for fair but not lavish compensation we need for a specific project, you don’t need to apply. Mr. Kobayashi may be in touch.

About NearlyFreeSpeech.NET


NearlyFreeSpeech.NET is about three things: fairness, innovation, and free speech.


Our baseline pricing is designed to recover the basic costs associated with “keeping the lights on.” What that means is that if every member of our service set up only sites and services that subsequently got no activity, our goal would be for them to pay exactly enough to cover the costs we incur. In other words, at such a basic level, we would pay our bills, everybody involved would make a reasonable wage, and there wouldn’t be any money left over at all. Everybody pays their way, and nothing more.

Then, when sites get bigger and become more successful, that’s when we start to profit. That’s the essence of our intention that “our success depends entirely on your success!” However, beyond the occasional pizza, we tend to reinvest what profits we make, be it spending money on innovation, newer equipment sooner, or similar improvements. (No matter what we do or how far we come, our list of ways to make the service better always seems to gain items faster than we can cross them off.) We also like to keep a little money around so that when the really critical legal issues come up, we can fight to protect our members’ privacy and service, rather than letting anybody who can hire a lawyer financially DDOS our members into submission.


Like most web hosts, we use and depend on a whole lot of open source software. Unlike most web hosts, we don’t depend on a proprietary control panel written by somebody else that dictates what sorts of services we can and can’t offer. We use a clustered hosting network that turns downtimes that would last hours or days if your site was dependent on a specific web server into minutes, or no outage at all. On our network, moving sites that are misbehaving where they can’t hurt others is the rule, not the exception. Those are some of the benefits of innovation.

The flip side of this is that our interface and featureset were entirely developed by people who march to the beat of their own drummer. It does things that others can’t, and doesn’t do things others can. While the result of that is something that’s not for everyone, a lot of our members are kindred spirits, and they like the idea that supporting us as we chart our own course helps us support them as they chart theirs.

Free Speech

Since we started back in 2002, one of the things that’s repeatedly been made clear to us is that governments aren’t the biggest threat to free speech. They certainly bear watching and perpetual wariness, but they’re just not the source of the everyday threats to our members’ ability to express themselves.

The most common threats come from corporations and the pressure they can bring. Not a week goes by that we don’t hear from some cheap lawyer about how mad some company is that some website said something that they don’t like and what horrible things they’re going to do to us if we don’t hop to and do their bidding.

We know where the line is. We know what our legal protections are, and how far they go. We know how to tell intimidation from legitimate complaints (which, sadly, do come up from time to time). As a result, we’ve been successfully telling the corporate blowhards who think intimidation gets results where to stuff it since 2002, and at this point, we’re awfully good at it.

(Please don’t take this as an invitation to violate our Terms & Conditions of Service. That’s a betrayal of the trust we place in each and every member to play by the rules, and when that trust is violated, we come down a lot harder than any corporate thug. In fact, we would go so far as to say that in such a case, we would strike down upon you with great vengeance and furious anger.)

(If you want to dig back into the past, you can visit this page from 2005.)