No, I just keep an eye on this and similar projects in order to recommend them when people ask.
The linked resources, are free, yes.
They have a site with paid courses, but that site doesn't cover creating your own network stack/protocol yet. I'm guessing the resources I linked were them savings stuff so they could eventually make their own course.
My favorite pro is league of legends support.
https://github.com/codecrafters-io/build-your-own-x#build-your-own-network-stack
This site, a similar site dies have resources for that as a course. It's very difficult, though.
Yes
https://wiki.archlinux.org/title/Wireless_bonding
EDIT: oh wait, you configured them both with the same static ip address. Can you use a tool like iftop to check that both interfaces are actually being used? You can also use tcpdump -i interfacename or similar tools.
It's very possible that this setup doesn't break, but isn't true bonding, where both connections can be used at once for more bandwidth. Although, maybe this is an easy, reliable way to get a failover type system, where when the ethernet is disconnected it automatically uses the wifi. Or maybe it's been using only the wifi this whole time.
When on God's green earth would someone want to delete the partition table and not immediately create a new partition?
counterpoint: https://wiki.archlinux.org/title/Btrfs#Partitionless_Btrfs_disk
Btrfs can occupy an entire data storage device, replacing the MBR or GPT partitioning schemes,
I really like this take on it: https://forgejo.org/docs/latest/user/actions/github-actions/#familiarity-instead-of-compatibility
For all of these reasons, Forgejo Actions strives for familiarity instead of compatibility. We want users of GitHub actions to feel familiar using Forgejo Actions, even if there are some small changes here and there. Workflows should work with some minimal changes.
I think the same thing applies to Linux DE's. Linux is not and never will be a 1 for 1 to windows workflows. If we chase perfect compatibility, we will be perpetually behind on a wild goose chase.
But, doing things like what KDE does, where most of the common keyboard shortcuts are the same, and things like virtual desktops allow for similar workflows with very little adaptation, is very reasonable.
The chess com engine analysis sucks. It's too focused on glazing you and not enough on being honest. It certainly feels better than the lichess engine, but it doesn't actually share more information.
For example, it used to be that a "brilliant move" was any move that you spotted but that the engine didn't. But now, it's been changed so that any sacrifice is a "brilliant move".
Further, the LLM based analysis is also pretty bad. It only seems to explain moves, but like most LLM's, it actually hallucinates and recommends nonsensical stuff, or incorrectly makes other claims about the position. If you search on r/chess you can find plenty of examples of this:
- https://www.reddit.com/r/Chesscom/comments/1p7n8js/can_something_new_explain_why_chesscom_ai_thinks/
- https://www.reddit.com/r/chessbeginners/comments/1ko6snm/is_chesscom_ai_useless/
- https://www.reddit.com/r/Chesscom/comments/1o2j3rg/is_the_ai_text_in_the_game_analysis_just_plainly/
etc etc.
As an alternative, if you really want that type of UI, you can also use Lichess' server based engine analysis (you get 40 free per day unlike chess com's paid stuff):

But it doesn't tell you why a move is bad. If you really want to learn why a move is bad, the local analysis lets you play your moves against stockfish and experiment and see why they are lacking.
Just learn to use the Lichess local analysis. It's designed to actually facilitate improvement instead of glazing users and getting them to keep paying.
Switch to lichess.org (open source, has all of chess com's paid features available for free, plus no ads or trackers).
Start with the chess basics set: https://lichess.org/learn
Then the basic tactics set: https://lichess.org/practice
And then do puzzles: https://lichess.org/training (chess com makes you pay for more than a few per day). Do a lot of them.
Then, you can also analyze your games on lichess using it's analysis engines (which chess com makes you pay for). Uh I can't find a good guide how to do this right now, check back later.
Docker compose's don't really need to be maintained though. As long as the app doesn't need new components old docker composes should work.
EDIT: Oops, it does look like spacebarchat's docker images have last been updated over 2 years ago:
https://hub.docker.com/r/spacebarchat/server
EDIT2: Although this is outdated, I think their github repo has an action to autobuild docker images on pushes. Still investigating.
EDIT3: Okay, they don't seem to be actually ran.
But using nix to build a docker image is pretty cool.
EDIT4: Oh shit, the docker image build workflows were added just 2 hours ago. Of course they haven't been ran!
Docker support soon, probably.
EDIT5: the workflow ran, but it looks like it's private for now.


https://lutris.net/games/league-of-legends/