The YASA axial flux motors benefit from much shorter windings and direct oil cooling which gives an unparalleled performance proposition.
A 200kW peak-power radial motor, run continuously, might typically give 50% of peak power between 80 and 100kW, as a result of thermal limitations. In contrast, a 200kW YASA motor runs continuously at 150kW thanks to the improved high-thermal-contact cooling that oil offers.
Since you're already using Tasker, you could use it to launch Tailscale on the phone at boot - I've got mine set to do this so my phone reconnects to tailscale after a reboot.
Now I have another mobile with more control, so restart is not a problem anymore, and as I can SSH in to it using Termux. This basically handles all of my needs.
Now I just need to get enough momentum to set up the process of waking up my desktop as needed and set up radical caldav server in the mobile.
That's a coincidence, that the author only picked recipes that are made without cycles. Other Factorio recipes (e.g. nuclear fuel processing) are cyclic.
I thought you could go between heavy and light oil cyclically, but I think the recipes I'm thinking of are from UltraCube. The others are a subset of nuclear (Kovarex and reprocessing), so I think you're right.
You automate all the recurring things (this is built into Gnucash), enter the non-recurring things (takes a minute or two a day if that day even had any transactions) and reconcile against the bank's statement/app/website monthly to make sure its representation stays accurate.
Once you've entered a transaction once, its autocomplete handles those going forwards so entering a new transaction is as quick as typing the first couple of letters of the shop name, pressing tab a few times, then entering the amount.
> You automate all the recurring things (this is built into Gnucash
Is it? When I last looked at GnuCash (which, admittedly, was like 7 years ago) you could not setup automatic categorization of transactions. You couldn't say, while going through imported transactions, "Every transaction where the payee is utility company should come from the Utilities account". The idea was that GnuCash was using some kind of Bayesian scheme to learn how to categorize your transactions automatically, but you had to input your transactions manually 3 or 4 times before it started working. Which, for me, seemed like a huge waste of time since 90% of my transactions could be automatically categorized by simple keyword matching against the payee or description.
I'm not talking about importing transactions, that's not a feature I use because it'd take longer than entering manually if you did it daily. I'm talking about the scheduled transaction editor, where you enter e.g. your rent manually once then schedule the same transaction to happen monthly. This should still work if you also import the non-recurring ones.
That's the heading, the title is still "small staff" for me. The heading is what shows at the top of the page, you'll see the page title in the browser tab's name among other places.
It's a school - write or find a comprehensive set of instructions (for the happy path), give each student a chromebook and a blank USB, and have them do it. You get usable laptops and the students learn an important life skill - not necessarily that they memorise the instructions for next time, but that they learn what's possible.
School Chromebooks are centrally managed via MDM software [1]. Getting students to jailbreak and install Linux is a non-starter. Schools lock these devices down right to the hilt. There’s no way parents would put up with their kids having an unrestricted laptop provided by the school.
I used to manage laptops (both student Chromebooks and teacher Windows laptops) at a school, and I wouldn't even trust the teachers to be able to do this, much less students and parents.
