who

Indeed. It's linked in the third sentence of the article.

1

An argument could be made that the first group is about engineering software, while the second group is about navigating a certain kind of adversity.

I guess one could call the latter a kind of engineering, but not of software.

who @feddit.org 4w ago

Describing the saboteur as "The developer of Mumble" is misleading, because Mumble is developed by multiple contributors, and Beatrici isn't even the most prominent one.

The post's true headline is:

Statement regarding attempted distribution sabotage

who @feddit.org 1mo ago

Systemd (along with the various add-on services that come with it on most major distros) meddles with and tends to break critical functionality quite often, except on boring systems where the needs being served happen to be handled well by systemd's happy path(s).

If the computers you maintain fit Lennart Poettering's idea of how to do things, then you might never notice a problem. On the other hand, if you're responsible for systems with unusual or complex configurations, or have need of the flexibility that makes unix so very useful in the first place, then you might very well discover that systemd is a pushy, invasive, poorly considered, buggy, and in some ways just pain broken collection of software, maintained with a level of arrogance and carelessness not often matched in the unix community, and you might rightly come to despise working with it.

Sadly, my experience has been the latter. In the years since the systemd suite was adopted by Debian distros, I have been burned more times by it and spent more weeks of my life troubleshooting it than I can count any more. Because of this, I have come to resent systemd. And I know I'm not alone in this.

So, dear readers, when you see people complaining about systemd, please try not to be like the zealots out there who routinely cry "luddite" and demand proof when they encounter folks who dislike it. Try instead to remember that one size does not fit all, that some of systemd's detractors are very skilled and reasonable people who happen to run systems that are necessarily different from your own, and have encountered problems that you have not. It has been over a decade. Some of us are tired of it, and tired of talking about it.

1

who @feddit.org 1mo ago

You might want to read this:

https://www.eff.org/deeplinks/2026/06/kids-act-would-require-age-checks-get-online

The bills explicitly requiring age checks were already rejected, so the powerful people who want to impose this invasive nonsense on everyone else are trying to do it implicitly, with this bill.

who @feddit.org 2mo ago

https://web.archive.org/web/20260608193011/https://www.404media.co/this-company-will-add-phone-airpod-and-smartwatch-trackers-to-license-plate-readers/

who @feddit.org 2mo ago

I expected that astute readers would notice the opportunity on their own. :)

Perhaps the defenestration could be an escalating affair: Use a ground floor window the first time. Add a floor for each subsequent offence. Add a floor for each co-conspirator supporting the mass surveillance attempt.

2

who @feddit.org 2mo ago

I propose that any government official seeking (more) mass surveillance be immediately told "no", thrown out of office, and prosecuted.

who @feddit.org 2mo ago

Yeah, but before you get excited, know that planet is rife with dihydrogen oxide.

who @feddit.org 2mo ago

Weird. I don't know how that happened. I wonder if I hit a glitch in Lemmy's web UI.

2

who @feddit.org 2mo ago

2

who @feddit.org 2mo ago

He described new C "guards" and scoped locks inspired by Rust

In other words, the improved safety will sometimes come from Rust code, and sometimes from C code. The important point being that safer practices are becoming more common now that Rust has called attention to them.

who @feddit.org 2mo ago

The go env -w command can make most go environment variable settings persistent for the current user. Alternatively, you could set the environment variable in your shell's login script.

Be sure to read go's docs for individual environment variables, because go doesn't respect all methods of setting them in every case. (For example, it ignores certain approaches to disabling its telemetry. How convenient for Google.)

2

who @feddit.org 2mo ago

This is my first guess, and a facet of my single biggest criticism of Go: the module system they added has an enabled-by-default policy of phoning home to Google servers, which turned an otherwise decent toolchain into spyware.

The GOPRIVATE environment variable may be what you need to avoid that error.

https://go.dev/ref/mod#private-module-privacy

https://go.dev/ref/mod#environment-variables

who @feddit.org 3mo ago

The cifs driver is complex. I haven't spent time tuning it in quite a while, but I once got rid of a performance problem by mounting with the nouser_xattr option, which can be included in a mount.cifs command or an /etc/fstab entry. That, or something else documented in the mount.cifs man page, might be worth a try.

Good luck!

FWIW, this is more likely Linux-specific than Debian-specific.

who @feddit.org 3mo ago

https://web.archive.org/web/20260518192910/https://www.404media.co/the-fbi-wants-to-buy-nationwide-access-to-license-plate-readers/