Debian is a stable distro and therefore tends to have less up-to-date packages.

Ubuntu added telemetry and forced snaps

Voyager:

(?=) for positive lookahead and (?!) for negative lookahead. Stick a < in the middle for lookbehind.

(to make the joke more obvious)

The two most common sources of security vulnerabilities are buffer overflows, use-after-free, and off-by-one errors.

It’s equivalent to cp -r, but:

• the copy is read-only
• reuses unchanged files
• easier to share (btrfs sub send)

btrfs sub snap -r

There’s even .deb, .rpm, flakes, whatever pacman uses, … that are just package files that copy to /bin/ for you, like .apk/.ipas.

Probably a reference to Reddit’s “fourth comment” thing.

My main branch is called HEAD.

Unless you’re on Voyager, in which case the image is already displayed before you click!

Yes, with --privileged. It’s totally safe. Trust me.

symlinks (or whatever windows calls them)

Windows actually has two types of symlinks:

• Shortcuts: stored as regular files on disk; only function as a symlink from Explorer.
• Actual symlinks: stored as actual symlinks (or NTFS reparse points). Transparent for all apps, but can only be created using mklink.
• There’s also junction links apparently, but afaik they’re just bindmounts.

moving a symlink can sometimes move all the data too.

Probably, someone managed to create a real symlink in their OneDrive folder, and since OneDrive probably doesn’t check for symlinks it blindly copied all the files to the cloud.

Take all this with a grain of salt — I’m not a Microsoft developer, and it’s been a while since I last used Windows.

It’s joking about A, which in ASCII stands for America, being the only letter capitalized.

By the way, you can use g~ to get the effects of tildeop without needing to set it.

Not if you’re a Bash programmer ·υ·

(Source)

Thanks for the reminder that I can tag users!

It probably opened it in ${VISUAL:-${EDITOR:-vim}}; usually setting one of those variables in e.g. bashrc will avoid future vim.