palordrolap

I’d like to believe that this means that these three pieces of software actually work and that someone in high office has decided that that is unacceptable.

Paranoid authoritarians really do not like ordinary people having access to secure communications and personal privacy. That might be an avenue they can use to organise and elect someone who isn’t a paranoid authoritarian, and that won’t do.

On the other hand, these pieces of software might already be compromised and this is all an elaborate double-bluff.

In which case it’s time for a few well placed communications over purportedly secure channels that would be guaranteed to generate an authoritarian response. Which they’ll then have to pretend they didn’t read until it’s too late.

I’m talking organising - horrors - peaceful protests. They really don’t like those. They have to use their brains, or someone else’s, in order to find a good excuse to stick the boot in.

I can’t imagine I’m the first to ever say this: Those who say they do not poop are full of it.

That’s the thing. Your memory only works one way. You’re incapable of perceiving time running in the opposite direction.

Every time you’ve pooped both in the past and the future*, it’s both going in and coming out, entirely dependent on the frame of reference.

*Yes, I did just refer to the future in the past tense. Because if time’s running backwards to how we perceive it, that’s actually the past.

The only way to win this game is not to poop. And good luck with that.

This may be a fleeting fancy, but at time of writing: «Merde»

Hello. As a former consumer of cheese, yes.

If it helps, think of it as a very unique form of cocoa-free chocolate, or better, a solid form of yoghurt.

(I developed a dairy intolerance a decade ago. I miss cheese.)

Neat. Don’t give them the ability to self-replicate and we’re golden.

Pipewire is newer and emulates PulseAudio so that it can be used as a drop-in replacement. There’s literally a command called pipewire-pulse related to this.

It makes me wonder if they really have both installed or are mistaking Pipewire’s emulation for an active PulseAudio installation, and so it’s just Pipewire that’s acting up.

I’d say reboot, but being in space might be one of those times where that’s a non-starter. In which case, they’re going to have to get their hands dirty unpicking system hooks and trying to reattach them all again as and when Pipewire’s working again, assuming it doesn’t do that automatically.

I never had a problem with either Pipewire or real PulseAudio back when that was current. I had motherboard sound physically pop, requiring the purchase of a separate sound card, but never a driver issue, so I can’t even imagine what might be going on.

At a guess, the counter goes up by fractions of a day internally, but it’s reset by subtracting the integer part, rounded.

The original version wouldn’t have had the rounding but they “fixed” that after the first time they did a reset and it went to 1 not 0.

As to why they wouldn’t just set it to zero, well here we have the joke under a microscope and it’s struggling to stay alive. Put the scalpel down.

NPC.

Oh. I have do the quiz?

It gave me “Multiclass”.

There’s a joke about inheritance in there somewhere. And the fact that no-one will want whatever I leave behind.

Can I choose NPC now?

Easy: House cat.

One of the well-looked-after, non-abused ones, naturally.

I already know about the monkey’s paw curses for that.

You have the constant recurrent belief that your owners are not pampering you at all times on purpose. And that they’re basically stupid big kittens who meow all the time and are terrible hunters. And that they control the rain but won’t turn it off for you. And also I don’t like this brand of food any more.

And hairballs.

I suppose it’s time I had another nap.

… but I think I can live with all that.

I never had screen tearing with NVIDIA under Mint, but for AMD I found that something needs to be added to the Xorg configuration to turn screen tearing off.

I suspect the default is so as not to limit the graphics in any way, but I can’t imagine the majority of users want it that way around, so I’m a little confused by that choice.

This website has instructions on how to fix it for Ubuntu, but I can confirm it works in LMDE too, so I assume it works across the Debian family if not elsewhere: https://davejansen.com/quick-how-to-fix-screen-tearing-in-ubuntu-with-amd-gpus/

Considering there’s rarely anyone around for me to say anything to, I’d probably let fly a few choice words and then start trying to work out where the next one was going to land and try to be under it.

That’s assuming you mean nuclear mushroom cloud anyway.

Other, sufficiently large ordnance also generates mushroom clouds and we’ve recovered from a handful of those before.

So any research would be trying to find out whether it was nuclear or not.

I’ve seen Threads. And a whole heap of post-apocalypse stories. I do not want to live in those worlds.

Prediction: The 3D TV will return in the next five years, with AI to turn 2D TV shows into 3D.

Heck, if I invited people over and told them I was going to cook them a meal, their heads might explode. The “what” would be entirely incidental.

But it would probably be a Sunday dinner. Beef, pork or lamb.

And I’d probably have to borrow someone else’s house for it or set up a tent in the back yard because there’s barely room to swing a cat in here.

I’m going to assume you’re not kidding, in which case, no, I mean the first letter of the command name it was called by.

There are already commands that do this. For example, on my machine, ex is the head of a symlink chain that leads to the vim text editor’s executable and if I run ex, vim will know that it was started with the name ex and will start in ex mode. ex was an editor that worked in a different way but was vim’s ancestor, so backwards compatibility is built right in for those strange people who love ex, (or have some kind of automation reliance on it being present).

Usually, the main command has a command line option that achieves the same effect as the special name. Here, vim -e is the less clever way to start vim in ex mode.

For yes, symlinking the name no to it and then calling that should arguably cause it to print n repeatedly, but it doesn’t, for historical reasons, hence my suggestion to go back in time and make it act differently.

(None of this touches on the fact that the GNU philosophy wants nothing to do with clever tricks like this. They prefer to compile separate executables for each and every use case. For example, most Linuxes have dir and vdir as variants of the ls command. Their functionality could have been implemented through this symlink trick, but instead there are three near-identical executables taking up space instead.)

Part hubris, part greed. They believe their own hype and either think that other people will believe it too or that they can force it on the unbelievers, thus leading to great profit.

Where is the profit? Enforced cloud accounts and storage mean users’ information is permanently held ransom, and users shall pay monthly to retain access to it.

They can also pick through users’ files and sell that information to data brokers and advertisers, if not also various government intelligence agencies.

Actually that last one is more about the continued ability to go on bleeding users dry, but it amounts to the same thing.

In before something like “The option does exist, but single article access is the same price as the minimum subscription. Thanks for contacting customer support.”

The two commands are not equivalent. sed 11q prints 11 lines whereas head’s default is 10.

Personally I would prefer head -11 in this situation as it more clearly indicates, for the sake of the meme, that something is being removed from the head.

There’s also that head seems to be ever-so-slightly quicker, perhaps proving what we already knew about thinking being quicker than speech.

TL;DR That’s what she sed?

The BeOS command line command set were all borrowed from or based upon Unix and/or Linux (IIRC many were straight from GNU), which is the basis for my comparison.

The kernel and graphics were all from-scratch and radically different from Linux, sure, but the same could be said of Linux when compared to the original Unix, or any of the BSDs.

That looks vaguely like a letter C to the left of the cap, assuming the wheat ear is rotated to be vertical, but I can’t make out anything else quite so clearly.

I also suspect that the oval shape that contained the branding was all a shade of orange or red, not unlike that small area towards the middle.

Reds are among the first colours to bleach, and it may be that something protected that one small area, like maybe the sort of sticky price labels that were once common, so that would explain why there’s not much of it left.