The assistant is in 2005

against the laziest vibe coder, probably

the name is menemommonomorable

it’s fine, python releases don’t use semantic versioning

it’ll take a while to reach 3.141 or 3.1415

you can actually call it from command line in this release:

$ 𝜋thon --version

Python 3.14.0

https://github.com/python/cpython/pull/125035

Yeah, if they fail twice in a row when I know I completed them correctly, I don’t bother a third time.

It exists too, it seems to be a support line from British Columbia, CA

https://www.crisislines.bc.ca/services

fwiw, I used Kopia for around a year, but eventually the backup got corrupted with a BLOB not found error and there was no way to fix it.

similar to this issue, except that nothing would fix or improve the situation https://github.com/kopia/kopia/issues/1087

and because it seemed to be an issue with the repo (not just with a snapshot), the remote copy was also borked. I couldn’t even list the snapshots.

I’ve since migrated to Rustic (though Restic might be more reliable today).

This seems to be the a similar issue too, but I was nowhere near the scale of this user. There are other similar reports that may or may not be linked to the same root cause, so it’s hard to say how rare this problem is.

and the more we vibe code, the more it thinks

Don’t forget the keyboard shortcuts. Office products would change shortcuts according to the language, so it would be more mnemonic. Ctrl-F for find and Ctrl-B for bold would be reassigned to whatever initials that language had. Fun! /s

I had completely forgotten about .avi

I’m using f-droid on 16 without issues (so far)

That’s coming next year AFAIK, and I don’t think staying on 15 will prevent it

deleted by creator

I work on a few repos that have branches that are rarely merged to the default one and it’s quite annoying

doesn’t matter: ma TAB

I prefer master exactly for that reason

Bc I said so

Fix your title

Isn’t that creating hardlinks between source and dest? Hard links only work on the same drive. And I’m not sure how that gives you “time travel”, as in, browsing snapshots or file states at the different times you ran rsync.

Edit: ah the hard link is between dest and the link-dest argument, makes more sense.

I wouldn’t bundle fs and backup compression in the same bucket, because they have vastly different reqs. Backup compression doesn’t need to be optimized for fast decompression.