#UnpopularOpinion / #HotTake: I think it's the right call for @gnome to "Stop being a mad scientist" and simply offload a lot of [quite security-critical] stuff onto #SystemD.

• After all both are being bankrolled mostly by the big 3 #Linux distros and neither #RedHat nor #Suse nor #Canonical are willing to spend money on essentially redundant work if they can avoid it...

Tho @BrodieOnLinux is wrong re: "Linux is #Unix" because technically #macOS (if we take in any #POSIX-esque system into account)!

• That being said, it does necessitate extra work by #BSD|s to run #Gnome.

There are many like it but this one is mine. Amazing quality and info! "Disarming Code" by Jonathan Levin

https://newdebuggingbook.com/

Today: Correcting StackOverflow posts that claim #macOS cannot use multiple editing commands within the sed `{ }` grouping command. While indeed

```
sed -e '/meow/ { s/foo/bar; s/baz/bang/; }
```

isn't allowed in macOS (which is totally fine by #POSIX 2001 btw), the following does work:

```
sed -e '/meow/ { s/foo/bar
s/baz/bang/
}
```

As specified by POSIX 2001. POSIX 2008 specifies delimiting with `;` though.

Just released: #swad 0.12

swad is the "Simple Web Authentication Daemon". It basically offers adding form + #cookie #authentication to your reverse proxy (designed for and tested with #nginx "auth_request"). I created it mainly to defend against #malicious_bots, so among other credential checker modules for "real" logins, it offers a proof-of-work mechanism for guest logins doing the same #crypto #challenge known from #Anubis.

swad is written in pure #C with minimal dependencies (#zlib, #OpenSSL or compatible, and optionally #PAM), and designed to work on any #POSIX system. It compiles to a small binary (200 - 300 kiB depending on compiler and target platform).

This release brings (among a few bugfixes) improvements to make swad fit for "heavy load" scenarios: There's a new option to balance the load across multiple service worker threads, so all cores can be fully utilized if necessary, and it now keeps lots of transient objects in pools for reuse, which helps to avoid memory fragmentation and ultimately results in lower overall memory consumption.

Read more about it, download the .tar.xz, build and install it .... here:

https://github.com/Zirias/swad

One thing I didn't know about the beautiful FediMeteo service is, that it is running on a fantastically low budget ENV that looks like it runs from a Server Park that has more than 60.000 of those servers purring along.

This is all that I shall default from the podcast you're smart and you're curious just like me so you will find the podcast yourself I will not put any links and then you will download it listen to it learn and enjoy

These are the screenshots regarding the two toots on

https://polymaths.social/@dendrobatus_azureus/statuses/01JXWNX73GE30935ANP4ZKAVC9

and

https://polymaths.social/@dendrobatus_azureus/statuses/01JXWNXSB086TGQHGWJ09DBG7P

https://nvd.nist.gov/vuln/detail/CVE-2025-5689

https://github.com/ubuntu/authd/security/advisories/GHSA-g8qw-mgjx-rwjr

Serious vulnerability has been detected in systemD authD which gives root access, from a distance

#InfoSec #Root #authD #systemD #Linux #POSIX #GNU #GPL

https://nvd.nist.gov/vuln/detail/CVE-2025-5689

@rl_dane

Thank you for this wonderful tip

So it's

:match Conceal /^.*$/
:set conceallevel=3

:highlight Conceal NONE

When you're finished, just do

:match

Executing this fix has been put on a red cue because the machine in question died a terrible early death

#freeBSD #ghostBSD #man #VT #console #Font #size #OpenSource #POSIX

https://forums.freebsd.org/threads/how-to-change-vt-console-font-size.91145/#post-630220

I'm sure you followed the Piped Pipe rule and updated your beloved client. I'm certain that you didn't defeat the update message of your beloved of client.

In case you have, please reinstate it because the new Piped Pipe is even more fun.

In case you do full manual update just go to the GitHub page and get it

This is a screen capture of KDE Connect on one of my Androids.

As you can clearly see my LAN has quite an amount of devices. All of these devices are being used by me.
They have specific purposes which makes my Android experience along with my Computing experience versatile and efficient.

I did not know how important KDE connect was for me. When I learned about it, I knew that it doesn't just enrich what I can do

KDE Connect is not a gimmick where I can control a Media Player, without any network connectivity by itself, from any of my KDE Connect devices. Many different functions can be handled smoothly without any problems, with the highest Speed that my wLAN can deliver from the point of my view of the LAN routers I have in my network.

Right now I'm using a wLAN router that is portable. This enables me to have the most efficient data transfer Speed between the devices I have on me without any snooping from any Big Company.

The curious case of shell commands, or how "this bug is required by POSIX"

https://notes.volution.ro/v1/2021/01/notes/502e747f/

Is the "$(blah)" syntax actually valid #posix #shell? I always use it because I think it's clearer than backticks for command substitution, but the #vim syntax highlighter complains about it unless I make the shebang '#!/bin/bash'. With '#!/bin/sh' it's highlighted like a syntax error. But it's supported by more shells than just #bash, so I don't really want to use the Bash shebang.

The POSIX spec seems to suggest that it's legal: https://pubs.opengroup.org/onlinepubs/000095399/utilities/xcu_chap02.html#tag_02_06_03. So why does vim and #neovim disagree?

@RecurringBloatware @cleverboi @rdfhrn @davidgerard #bash has some limitations and makes some things unelegant.

• Which isn't inherently the fault of the authors, given #POSIX-compatibility makes it hard to innovate and #fish yeets that for more elegance and flexibility.

Like dialogues and selections as well as parameter interactvility...

When was the last time you have played with KDE Connect?

You've never heard of that? Let me enlighten you. KDE Connect is a suite of very handy Network tools, to get the maximum out of the transfer and the control of data & programs between your KDE computer and your Androids.

It is in fact so versatile that even if your KDE computers are not connected, you can still do a lot of things between your Androids which are running the network software suite.

There are so many things you can do you should just download it yourself and put it on your Androids

A few highlights are transferring files between your devices in a transparent manner where no company like Google can snoop anything

Controlling media players from 1 device through all the others.

Getting notifications between different devices and even getting output, graphical output from different devices on others.

Controlling your Android with a mouse from a KDE Connect computer

The list goes on

Note:
If you're running a Linux distro with a running firewall, you have to make sure that your firewall has all the ports open for KDE connect. There are examples of the ports needed, in the docs.
I also have them {for {g}ufw}

In case you're still stuck with a Closed Source tool set for your 3D workflow one tool that you can use which is Open Source is freeCAD

https://www.freecad.org/downloads.php