Digital ads do not promote things I'm interested in buying. I do not see ads very often at all - I haven't had a TV for 20+ years, I don't go to cinemas, so I don't even see those kinds of ads. Occasional ads on YT pop up, and I'll skip them; if they are unskippable or too frequent, I'll abandon the vid. I'm not on any commercial "social media", so I don't see ads on them either. I've just never liked social media - Lemmy and Mastodon are all I use these days.

Occasionally, very, very occasionally, I'll see a meatspace ad that I pay attention to: there's a local alternative music collective that wheatpaste ads around in a nearby town. I actually WANT to know about these events, and I will actually go to them, and I actually sought them out in the first place. I also see ads at my local community centre, for local events. Same kind of thing.

So how is this resistance futile?

Solidarity. You're so right. It's a wild ride, but I'm charting my symptoms, and they ARE improving - I hope the same is true for you. U had to make some big changes, cutting out energy drains, and then cut more and more. Self care is the most important thing in burnout, but learning what you need to do to provide yourself care is the hardest.

I'm in Autistic burnout... the slightest stress - just about any official letter, appointment with benefit agency or sometimes just something nasty on the news - can lead me straight into dissociation or shutdown. Occasionally, just having to concentrate hard can also wipe me out in a similar way. It usually takes at least a few days for me to recover.

I'm nearly 60, and this is new to me - I mean, I've had bouts before, but never as debilitating as this. I used to be able to cope with these things, even if they darkened my day.

Yep.

Flockin' hell.

He's bang on. LLMs have no understanding of anything: they are literally just statistical models.

You never know ... maybe THIS year!

The way windoze 11 is going - people really hating it - you never know, but I'm not holding my breath. Linux is still very niche, and people are wary of "strange" "new" things, especially FREE ones - where's the catch? I've seen it surge and blossom over the years, but it's still got a really tiny install base (as long as you don't count Android and embedded tech, where the OS and kernel are largely irrelevant to the user). But I don't see people moving over to Linux in droves any time soon, really: I've seen too much.

For context, I've been using it since [dredges up old memories] slackware was new, so about 1994, when a work colleague and I installed it (off about 20 floppies) onto an old 386sx PC with probably 4MB of RAM. Been using it ever since - and from Red Hat 4 onwards (about 1999) it's been my only OS on my own computers. I've always preferred it, and I've seen it grow in so many ways - I'd still use it if it was illegal. I haven't tried EVERY distro, but I have tried most. These days I mostly stick with Debian or Debian-based distro's (I'm currently on Mint LMDE).

Had to do some work with SuSE post Novell acquisition for a customer. IIRC the package manager is a bit odd, but I haven't looked at it in what nearly 15 years, so I can't really remember much about it. What I CAN remember involved running packet traces using Wireshark - it was mostly network problems, I think, so nothing to do with SuSE. It was certainly very popular in Europe, though I have no idea what they're doing these days!

The court has decided not to tell the jury that the trial for the accusation of burglary will result in terrorism sentences if they are found guilty; the defendants have been told they are not allowed to state their motivation of preventing the production of weapons that were to be used in the ongoing genocide in Gaza, and the press was gagged from reporting on it.

In other words, it was going to look to the jury like it was purely a burglary, but the defendants were going to be sentenced for a different, much more serious crime, and no-one was allowed to talk about it. This is because in the previous trials, most of the defendants were acquitted by the jury, because the defendants used the crime of conscience defence.

I'd suggest you start with a simple static web server if you're looking for a good beginner project. Use something like Nginx, and just set it up on your local network at first, then work out how to harden it, and open it up to the real internet. There's a lot less to learn for this usage case, and it's less likely to get you into trouble.

I say that, because, after reading through the thread, it seems you are hoping to find an (educational) use for an old computer. I did Linux and Unix admin professionally for 15 years, for some famous brands. I would NOT recommend setting up a mail server as a first project - it's complex in ways you will never expect, and will require learning skills and knowledge that are very specific and you literally can't "start small and build up" because a lot of the things you don't know yet will get you into big trouble. Essentially, it's not too hard to set up the server software, and your hardware is certainly capable of running this task, but making it safe and secure IS hard these days - especially with all the encryption and anti-spam setups you have to learn how to do.

In 2011, I worked in West Bromwich, greater Birmingham, UK, on Birmingham Road, where it joined High Street. The news had been reporting on riots starting in Tottenham, London, and it was said that they were spreading. One lunch time during this time, I went out to get lunch from a great Indian sweet shop called Dhillons that did an amazing Samosa Chaat, which was about 5 minutes walk down the road from our office. As I got closer, I could see a crowd and police further down the road, not far from the sweet shop, and coming towards me. Then I saw smoke, and turned around, and went back to the office, without my samosa chaat. Loads of busies with full blues and two's on (police cars with sirens and lights on) started whizzing past, towards the trouble, and this continued all afternoon. When I left, the air was cloyed with smoke, and the street towards the sweet shop was cordoned off. The next day we learnt that the sweet shop got smashed up, and their van was torched, one of many that got hit. Nearly got caught up in a riot!

Seems quite good - I've tried a LOT of MarkDown editors over the years, but until quite recently, I'd stuck with Zettlr for a long time. I've recently reinstalled my laptop, which made me look for alternatives to some software, and I've been playing round with MarkText for the last few days, which seems nice.

HelixNotes is definitely good - if I had to drop MarkText, I think I could get on well with it. I like that they have a debian repository, so I can keep it updated with the usual system update software. I downloaded the AppImage as a quick test, but it didn't work because it was compiled against an old version of glibc.

The only thing I don't like so far is the format toolbar is at the bottom of the editor screen, and I haven't found a way to move it.

This diagram is wrong on so many levels. Ozone is "charged Oxygen" (O1 rather than the usual O2) so it's saying you get Ozone out of the Hydrogen side. The bubbles are forming in a place where they can't get to the output vents, so the accumulating gases would slowly force the water level in the inner chamber down, and thus up through the vents. It's pretty shit. Is it AI slop?

Science fiction dystopias being fictional and set in the "far future".

I can assure you it's far from easy to get PIP, as I'm going through the process at the moment. It's degrading and stressful (which is the thing I've been told to avoid) and seems entirely arbitrary. The application process is opaque and assessment is not performed by medical professionals. If someone IS getting PIP, they have jumped through MASSIVE hoops to do so. If you think they're "cheating" then I challenge you to try to get it yourself. You really seem to have no idea.

I hate your reductive "if they'd just" rhetoric, whether directed at drug use or other "simple to solve" difficulties that are, in practice, far from simple to solve. You see an outward symptom as the root cause, and you also fallaciously assume that even if that IS the root cause, that it's easy to solve. And before you assume that I'm one of those people "doing drugs all the time", I'm not.

I started working in 1985, and I've worked right up to July last year, when I got ill. Prior to that, I seldom had time off sick - I had less than two weeks off in the past decade.

Just wait until LLMs are used to design most of them - they will be distinctively average.

Nah man. "kill" doesn't shut the system down quickly. This is the "instant death" way - the kernel reset gun - no shutdown scripts, no disk sync, just reset to BIOS boot sequence, instantly:

As root:

echo 1 > /proc/sys/kernel/sysrq

echo b > /proc/sysrq-trigger

If you change out the "b" in the second command for "o" it will just halt the kernel instead of rebooting. Still switched on, but the system is doing absolutely nothing.

I used to use this trick all the time to test high availability server clusters.

Not only can you take loans against your shares, but you can pay the interest on those loans with dividends from the shares, and because they're a loans, the cash-in-hand is not taxable, so you pay NO TAX on it. You have no "income" on paper, but you can pay people and companies with shares instead of money, shares that you can literally conjure into existence by typing numbers into a spreadsheet. Those money and shares are really useful for greasing the palms of politicians, government officials, and hangers-on so that you can get your way. You can even use this money and influence to cause riots and stoke division in society.

I usually do that too, but this time round I've really not had the spoons. Had the "Red Letter" yesterday - "we're sending in the heavies". I still CBA - send 'em. We don't have a telly and we don't watch any telly via the web - we HATE TV. I don't even watch any U-tubers regularly. Been this way for >20 years.

You mean in the context of high availability?

tl;dr: It's to test if the cluster fail-over configuration is working properly.

So this was before things like Kubernetes or Terraform were a thing, so had to be done by the operating system itself. The simplest HA cluster is made of two nodes, one in "active node", the other "passive". The active node does all the work, and the passive node just keeps its data synchronised with the active node. I used to use DRBD for this, which is a system for copying writes to the active node over a network link to the passive node. That only gives you a "second, up-to-date copy" which is not that useful on its own - you also need a way to automatically switch over to using the passive node if the active one "dies", and for that I used to use "heartbeat", which simply passes packets back and forth between the two cluster members - ping-pong style - and if the passive node notices that the active node hasn't sent its scheduled packet for, say, 10 seconds, it cuts it off the current active node (kills it), and promotes itself to the active role, thus preserving the service. Killing the "other node" is necessary to stop data corruption or user requests going to a node that can't actually service them, and is called STONITH - Shoot The Other Node In The Head. STONITH can involve an electronically controlled switch, which literally cuts off power to the "other" node, or can isolate it on the network, by shutting down its network ports on the switch, or in a VM setup, sending a notification to the hypervisor to kill the VM.

The reason you need to be able to kill the kernel on the active node, is that when you manually shut down the active node, it automatically informs the passive node that it's going down, known as an "orderly fail-over", and you're not actually testing if the heartbeat fail-over works, you're just testing an orderly fail-over. Killing the active node's kernel tests that the passive node is properly configured to take over during a catastrophic failure of the active node. You can watch the heartbeat status go from "up" to "down", and then see the passive node decide to take over, promote itself and bring up its services, and begin processing requests.

To make sure it's all working, you need to test orderly fail-overs first, from both nodes, then test disorderly fail-overs both ways, by using the kernel gun on the active node.

Things moved on from Heartbeat-based HA clusters to multimode clusters managed by Corosync and other software, enabling other strategies to be employed. This was eventually supplanted by "orchestration" systems like Kubernetes, and proprietary Virtual Cloud systems that move this functionality to the platform rather than the operating system.