palordrolap

This is true. But then I’m not using the latest version while I still have an active session, and that can lead to weird behaviour or errors after the fact.

Case in point, I once received an Xorg update that I allowed to install, but didn’t restart the computer properly until much, much later.

By then I’d forgotten about the update, so when I restarted and started having graphics problems, I was mystified.

I’ve also forgotten how that all panned out, but in the same situation I’d roll back to a previous Timeshift snapshot and work the system forward again until I find the culprit or things are stable, so I assume that’s what I did back then.

Tangential advice: Many people use YouTube (and formerly Twitch until they nixed it) as a place to store videos. As in the only copy of a video is hosted there.

If your videos are precious to you (or you think they’re going to be), make arrangements for them to be at least stored elsewhere, if not hosted. That’s not going to be cheap what with hardware prices going through the roof, personally or third-party, but it is necessary because no host is both trustworthy and permanent.

Actually not even self-storage is as trustworthy and permanent as we’d like, but it’s still better than any alternative for data retention.

Also, donate to your chosen Fediverse host(s) if you can.

For me, it’s about reducing the amount of time the “update available” icon shows up in the system tray, because its very presence bothers me. Maybe there’s something cool and new. Maybe it fixes a severe security problem. If it’s for programs I’m not using right now, then the update can be applied right now. Otherwise it’s going to have to wait until I’m done. And bother me.

Yes, I could turn updates off and never see it, but that seems like a bad plan in the long run.

An old computer trick / prank / “fun” thing to do was piping random things to /dev/audio, or finding whatever program was available that could take any old file and not complain while translating it to audio by some means or another.

On my distro there are at least three of these programs installed by default: aplay, paplay and pw-play.

Some or all of these will complain if the file or stream they’re given isn’t a recognisable audio file, in which case, there’s a --raw or similar flag where it’ll just shrug and blast whatever through the sound system. If you’re creative, you can set different sample rates and hear it at different speeds.

VLC is just a really fancy way of doing the same thing.

For even more “fun”, try opening a file in Audacity / Tenacity, which will default to raw mode if it can’t tell what a file is, and you get to see the waveform and so on. Just take care not to modify and save over an important file with that.

Yeah, my university had those, but they also had an interface to it accessible from the more modern systems.

I also did a work experience placement with a company that had amber-screen terminals when I was still at school (and the year still started with a 1), so I’m no spring chicken either. They were very early in the process of supplanting them with PCs, which is not something they explicitly told me, but looking back, the evidence was all there.

The “fun” part with those specific terminals was that the admin password for the terminal hardware itself - because they had a rudimentary sort of BIOS on them - was a “fail at the first wrong character” system. With enough tries you could figure it out.

There wasn’t much you could do from there, at least not that I remember, but one of the terminals I used did end up beeping at a slightly different frequency to all the others.

A terminal in the computer sense was originally a screen and keyboard attached to a terminating node on a network. The network didn’t pass through, so it terminated there. This meant the literal, physical hardware. Think old school green- or amber-screen systems attached to a mainframe in the basement somewhere.

A console was a terminal that was serving some kind of purpose and showing some kind of interface for humans to interact with. Without the interface software, a terminal is not a console. Without the hardware, you wouldn’t have either.

It’s easy to see how these things became blurred.

And now it’s worse because we’ve extended the meanings a bit. The program in our fancy GUIs called “Terminal” and which we often just call “a terminal” is actually a terminal emulator.

And to a lesser extent, so is the thing you can access on many distros by pressing Ctrl+Alt+F1. This sometimes gets called “the console” because it’s even more like those old terminal interfaces. Full screen. Text only. Largely monochrome. No GUI.

And deeper still, a terminal, console, or terminal emulator doesn’t have to mean “a shell” which is another thing entirely. Shells just happen to be one kind of interface that can run there, and is often the default option in a GUI terminal emulator.

From a console, the default program is generally some flavour of login prompt. And then the system automagically loads whatever is configured as that user’s shell once they log in.

I made sl on my computer a bit more literal. It takes the output of ls -l and reverses every line, including any wrapping within the column width, and pads it to the right of the terminal. One day I might get around to fixing it so that it forces, parses and correctly reverses the ANSI colour codes too.

In /usr/bin, I get lots of lines that “start” with spaces and “end” with things like toor toor 1 x-rx-rxwr-

US English dialects mainly, though there may be pockets in other Anglophone places.

The basic functionality of sponge can be emulated with an AWK or Perl script, so most people who needed it in the past almost certainly rolled their own.

I get what they’re going for with the arrow coming from the process to STDIN, but I still feel like it should point the other way.

And shout-out to the sponge and tee command-line tools for those situations where the memory buffer won’t cut it.

“I like to rebuild my kit sports car every time I want to take it out for a drive. Anyone who does otherwise is a pleb.”

Where are their communications? Who visits a government website without needing to?

To me it makes sense that they should cover as much ground as possible and have accounts on all major platforms as well as making announcements on TV and radio.

And in order to do so they should have their own accounts on there in order that their message gets across directly without having to go through a third party that has an account on there.

Now, when that site starts espousing “free speech” of the sort that only they like, then it might be a good idea to not use that particular platform any more, because that brings in the third party interference that wasn’t there in the first place, even if the site was technically third party.

But hey whatever, now let’s make, say, the BBC the mouthpiece of the government - it’s not like the Tories didn’t try really hard to do that when they were in power - and have everyone report on that. Far better.

Government creates announcement feed. No-one knows about it because they can only advertise it on their own announcement feed.

What now?

@[email protected] @[email protected]

It may not be a public place per se, but it is a place where a very large cohort of the general public go.

Perhaps my analogy should have been “This is bit like saying that governments shouldn’t make announcements on television and radio stations not under government control.”

The same logic applies there. Of course they should. A large cohort of the general public watch television and listen to the radio (less so these days in the age of the Internet, but people do still watch and listen there.).

This is a bit like saying that governments shouldn’t post notices in public places.

Surely you’re not saying they shouldn’t have had a Twitter presence?

Or is this more of a “they should have left when Elon took over” kind of thing? In which case, they probably thought that the majority of people who follow(ed) them on there wouldn’t have left immediately - not least because there weren’t any good alternatives* at the time - so it would have made sense to maintain a presence, which I think is what’s actually going on.

* Yes, Mastodon existed, but you’ve got to think about the average person here. There’s a reason the first people on there were academics and tech folks.

Lucky you had a motherboard with a CMOS battery. Without that*, you needed to enter the time and date every time the computer booted / rebooted.

* Or a capacitor instead.

LMDE’s system is the same as regular Mint. I’ve been on LMDE for a few years but was on regular before that.

YSK/PSA: If you’re on Mint, Mint’s apt is not Debian’s apt and while they work similarly for common use cases, they diverge pretty quickly beyond that. Both are installed by default but Mint’s takes precedence.*

Case in point: I was looking for which package - specifically one that was not yet installed - contains a certain command line tool and Mint’s apt search does not find it. Debian’s does. **

On the other hand, Mint’s apt has way more subcommands than the default one, which have been useful on occasion.

* Mint’s is at /usr/local/bin/apt and Debian’s is at /usr/bin/apt; The default user $PATH puts /usr/local/bin before /usr/bin.

** FWIW, the tool is/was sponge and it’s in the moreutils package.

Let me save you a few characters: %Y-%m-%d can be shortened to %F

For visualisation’s sake I also like to put a space before the %F so that the year and the file size are separated a little more, but that’s more of a taste thing than anything else.

(Caveat: %F’s year is explicitly four digits in some libraries, whereas %Y is always the full year. If you’re planning for your code to last 8000 years you might want to consider that.)