Found the best license:

GitHub

fork-off-public-license/FOPL_0.9.md at main · klardotsh/fork-off-public-license

a software license for the existentially exhausted - klardotsh/fork-off-public-license

# The "Fork Off" Public License v0.9 > _fork off_ (verb) - to take this freely available code, create a new > repository under a new name to hold it, and maintain it your forking self If you've received source code with this license attached, you are free to build, run, and/or redistribute it. You are not, however, free to complain at the author(s) or maintainer(s). Here are some examples of strategies to alleviate any pain and suffering this requirement may cause you: - If you think this code comes with literally any warranty whatsoever, fork off. If this code causes your house to burn down, your cat to poop on your keyboard, or billionaires to buy your website... sorry about that, but still fork off. - If you think this code should do more or less than it currently does - fork off. Relatedly, if you think you've found a bug in this code, no you didn't. It's a feature. Fork off. Even if you think this software is usable somehow: fork off! - If you don't like the author(s) or maintainer(s) of this project, or if the leadership style of this project is not agreeable to you - fork off. If you would rather the code be hosted on some other platform than you found it on: fork off! If you email the author(s) or maintainer(s) of this code, you may, at their sole discretion, be sent a complimentary copy of this license in response, with a reminder to _FORK OFF._

This cooking technique (heat-retention cooking) is used all the time in bbq, which is how I learned of it, but very interesting to see charts and estimates for everyday food. Especially with summer arriving and this making it possible to cook without heating up the house as much:

SmolNet Portal

SolarMonk and the Wonderverse I had a 6 hour drive yesterday, and all that boredom contributed to some creativity. Myself and a friend had been discussing the possibility of making a fully copyright-free-open-source-whatever literary universe. This gets around a lot of the problems people typically have with fan art or fan fics or any other attempts to make art inspired by something that's locked down by corporate interests. And then of course you have stuff like the Lord of the Rings and all of CS Lewis' stuff that is locked down by his family, and again, becomes something unusable due to corporate greed. We discussed various starting points that were already in the public domain: King Arthur, The Odyssey, E. Nesbit's stories. But all of them felt a little too confining. Then inspiration struck: Alice in Wonderland. It's so insane, it allows for anything to branch off from it. One particular literary universe that always frustrated me with how tightly it's overlords controlled it is Warhammer 40K. But that whole universe could easily be accessed via Wonderland: Alice wanders off into the woods, and the next thing she knows she's surrounded by giant iron warriors fighting bugs from space, and Games Workshop can take a long walk off a short pier. And on top of all that, there's already a lively community around Wonderland, with movies and tv shows and anime and fan fics stretching out the Wonderverse in all directions. Anyway, back to the 6 hour drive. I came up with a simple game, set in the Wonderverse, that could be played with pen and paper and a D6, though I also threw together a spreadsheet since I wanted to test it a bunch and see if it was varied enough to provide interesting results, and so far it is. I put together a repo with the rules and the spreadsheet here:

GitHub

GitHub - davidbaunach/solarmonk: SolarMonk Game set in the Wonderverse

SolarMonk Game set in the Wonderverse. Contribute to davidbaunach/solarmonk development by creating an account on GitHub.

But here it is if you don't want to click through: SolarMonk Alice and Cheshire Cat stumble upon a monastery of Benedictine monks as they walk through a forest clearing. They do not know the way to the garden, but they are fascinated by its description, and plan to build their own one day. After a pleasant meal, Alice and Cheshire Cat continue on their way, and the monks continue their life of prayer and sustainable living. How long will they survive? Begin with: 50 monks 50 food Each year: +2D6 food +D6 new monk(s) joining -D6 monk(s) dying of old age/accident Role D6 for each aspect of the year: Earth 1. Earthquake (-10 food, -1 monk) 2. Sinkhole (-1 food, -1 monk) 3. Calm (+1 food) 4. Sleepy (no change) 5. Tranquil (+1 food) 6. Fruitful (+5 food) Air 1. Thunderstorms (-5 food) 2. Blizzards (-1 monk) 3. Tornado (-5 food, -1 monk) 4. Wildfires (-5 food, -1 monk) 5. Pleasant Breezes (+5 food) 6. Balmy (+5 food, +1 monk) Water 1. Gentle rains (+5 food) 2. Heavy rains (-5 food) 3. Flooding (-15 food) 4. Drought (-10 food) 5. Healthy rains (+5 food, +1 monk) 6. Average rains (+1 food) Fire 1. Extreme heat (-5 food, -1 monk) 2. Cool temperatures (no change) 3. Comfortable (+1 food) 4. Temperate (+5 food) 5. Mild (no change) 6. Extreme humidity (-1 food, -1 monk) Ether 1. Miracles (+10 food, +10 monks) 2. War (-10 food, -5 monks) 3. Plague (-10 food, -10 monks) 4. Malaise (-3 food, -1 monk) 5. Neutral (no change) 6. Satisfaction (+3 food, +3 monks) 5 extra food may be given to the poor for +1 monk before next year begins The game ends when you want it to, or when food or monks reaches 0.

So I've been using Resilio to keep all my files (docs, art projects, music and video libraries and some random stuff) synced across all my devices. This presented a problem with the Steam Deck, in that it requires substantial workarounds to make Resilio work (mostly due to how Steam keeps stuff locked down). I solved this problem by avoiding it completely: started a virtual machine, ran Debian, and got Resilio working there no problem. 15ish hours later when all my files had synced, the final part of the problem needed solving: how to quickly move files to the host machine from the vm, and in the opposite direction on occasion. Again, there were many fiddly methods, which I quickly dismissed as being too much work. Instead, my first attempt was to install Keet on both, which made it easy to move files, but it was one at a time. What I finally settled on, was using Syncthing on both, and just having a folder I could dump stuff into. Can easily move things in both directions, and files move almost instantaneously since it's all essentially on-device. Redundancy is preserved, can access what I need on the device I need it on, and I've worked around the limitations of the Steam Deck without any messy processes that could potentially break after an update. Success!