Can’t agree. The internet is composed of ultra high speed, ultra cheap plumbing (financed by normies doing their normie things). We piggyback on it, selfhosting our capsules for next to no cost, freeloading on all the wonderful infrastructure. Don’t look at all that is bad about it, don’t participate and it won’t affect you.

I made a honest effort, but in the end went back to Git for my personal projects. The advantages Fossil has over Git (wiki, bug tracker) are trivial to emulate with versioned plaintext files, and everything about Git’s version control system just clicks with my head. Having years of experience breaking and unbreaking things helps too.

Tho one thing Fossil taught me is to merge by default, not rebase. Rebase when there’s good justification for it, and the rest of the time, have an alias for git log --oneline --graph --first-parent (or whatever that was). --first-parent collapses a horrible branchy-mergy history into a linear overview thereof, with details available when needed.

Go. It’s nobody knows how many thousands of years old, it’s easy as pie and difficult like crazy. The game can’t end in a draw. It’s easy to balance strong and weak players so they can compete with full effort. The equipment is trivial to make with common, cheap household items. Computers got competitive against humans just a couple of years ago (compare to chess where they beat humans in 1997 and ever since).

I watched my kids grow, my apples and pumpkins to ripen, my code to compile, my functional tests to pass. Life’s good.

Several people here have suggested the gearbox be in 1st gear, while starting. Dunno why.

I always shift to neutral, while starting, for safety (to avoid having the starter lurch), depress the clutch (as a 2nd layer of defense for the same) and still sometimes it happens that I forget both.

As for how to actually start moving: press clutch, put in 1st gear, release any brakes assuming you’re on level ground, slowly release clutch until you feel that the clutch starts engaging. Then hold it there for a moment, to allow the car to get a tiny bit of speed, until finally releasing it completely. If you release clutch too fast, it’ll overload the engine and it’ll stall. If too slowly, it wears the clutch, which is expensive to replace. Older gasoline-fueled cars with low torque at low RPM might need a bit of accelerator (say 2000RPM) to get moving without stalling.

OP didn’t want to delete anything, but to compress them all, exploiting the fact they’re similar to gain efficiency.

Indeed! Interesting! I made an experiment now with a non-compressible file (strings < /dev/urandom | head -n something) and it shows you’re right. 2nd commit, where I added a tiny line to that file, increased repo size by almost the size of the whole file.

Thanks for this bit.

Highly unlikely to succeed. The tiny differences are spread out all over the image.

You could store one “average” image, and deltas on it. Like Git stores your previous version + a bunch of branches on top.

Cool idea. If this doesn’t exist, and it probably doesn’t, it sounds like a worthy project to get one’s MSc or perhaps even PhD.

Wheee, I just got out of the Prison start recently. Trying to figure out what I want to do with my life, next.

I use it whenever possible, for its easy sandboxing. I’ve also been bui lding my own sandboxing solution based on Bubblewrap, for things not on Flathub. Maybe I should learn how to build flatpaks locally, instead…

I feel like I couldn’t live without my bathroom. I probably could, but it’dn’t be great.

I’m using NixOS in Azure - Azure allows creating a VM out of a disk image, and NixOS has tools to create preconfigured disk images. You inject your SSH keys and stuff straight into the image, then upload and create a VM. A bit fiddly, but I got it to work.

If you have a place to host Forgejo/Gitea, you have a place to store a Git server. Set it up like this:

$ git clone --bare myrepo myrepo.bare
$ scp -r myrepo.bare srv:
$ cd myrepo
$ git remote add origin srv:myrepo.bare
# or
$ git remote set-url origin srv:myrepo.bare

Now git push etc work similar to GitHub, but you’re using your server (named srv in SSH config, as shown in my previous post) as the remote storage.

Selfhosted Gitea is a way to get a wiki, bug tracker or whatnot - collaborate, for example, but it’s not necessary to have a Git server for your personal use.

I started running my own Gitea instance because I wanted a private place to host my Obsidian notes.

I don’t have the time to read the article now, but permit a question: what do you use Gitea for?

I’m holding my dotfiles on a SSH server, clone/push over SSH, and it’s enough to do Git. I don’t need a ticket system, or wiki or anything (I use plaintext notes).

$ cat ~/.ssh/config
Host srv
  Hostname srv.mywhatever.com

$ git clone srv:/path/to/repo
$ cd repo
$ git push

It’s not compulsory, so I get not to do it.

Sorry for the cliffhanger. That’s ILIFE. I didn’t have the opportunity to check, and I didn’t remember it by heart.

My robot vacuum doesn’t do WiFi, so unless it has an expensive GSM modem, it can’t send anything.

OTOH, it just sweeps floors, and lacks built-in voice assistant, freemium subscription with a paid option to also sweep the hallway, smart speaker mode, companion/pet mode, built-in games, or all the rest that the modern equivalent of a broom ought to be capable of…

Pancakes?? Yell when they’re ready, and we’ll run over like hares and devour them like lions!