I (accidentally) removed two symbols from a curl header that have been deprecated and without functionality for over 17 years.

Result: of course there is still code out there using those that now reports build failures...

Keeping absolute backwards compatibility is real work.

At the gates of hell - The Lake of Hell national park

i got so angry after reading this paper on LLMs and African American English that i literally had to stand up and go walk around the block to cool off https://www.nature.com/articles/s41586-024-07856-5 it's a very compelling paper, with a super clever methodology, and (i'm paraphrasing/extrapolating) shows that "alignment" strategies like RLHF only work to ensure that it never seems like a white person is saying something overtly racist, rather than addressing the actual prejudice baked into the model

From Jason Gunthorpe, maintainer of 5 Linux kernel subsystems:

IMHO the current situation of Rust does not look like success. It is basically unusable except for unmerged toy projects and it is still not obvious when that will change.

Today I learned that my Apple AGX GPU driver, which is the kernel side to the world's first and only OpenGL and Vulkan certified conformant driver for Apple Silicon GPUs, and also the FOSS community's first fully reverse engineered driver to achieve OpenGL 4.6 conformance, and which is used by thousands of Asahi Linux users in production, and that literally has never had an oops bug in production systems not caused by shared C code (unlike basically every other Linux GPU driver), is "an unmerged toy project".

(He works for Nvidia, I guarantee he's heard of it, considering we beat nouveau and NVK to GL 4.6 conformance.)

I guess this is what Linux kernel maintainers think of us Rust developers, that we only write "toy projects"...

Speaking of recent events at LKML concerning #Rust and #kernel, and also what I've said in some threads, the key element for reaching tolerance is #documentation.

This does not mean that bad behavior is acceptable but great documentation is best means to be preventive of such events ever occurring. Right now Rust kernel documentation almost does not exist.

What is an appropriate granularity for documentation? It is the level where an experienced kernel maintainer who has *never* used Rust can still understand your kernel patch.

That is the ideal. Obviously not always reached but underlines how bad state Rust documentation is ATM. I blame for most of this #Google and #Microsoft, not the developers. They are two private companies who spend vasta amounts of money for Rust kernel work. And they should know what I said already.

This is a screenshot of the most beautiful karma post of 2024.

After having abused his ownership of X for two years, Brazil becomes the first country to simply shut down X.

The legally elected social democratic government of Brazil experienced a January 6 style coup attempt by anti-democratic, hard-right nationalist Bolsonaro in January 2023.

They have since fought a long legal battle to get Musk to shut down X accounts related to this coup.

Musk refused.

So they shut him down.

I have accountant for my company now. Had a meeting yesterday. I decided to go to a traditional accountant office and pay for personal accountant. I think this spending will come back!

I.e. not using one of those fancy Internet platforms. IMHO, great accountant is the same for a company as a great doctor is for a person.

it is crazy how acid you can get with u-he bazille without even getting even into using filters yet. phase distortion and fractalize rock

Good to know enjoyed this article, https://it-notes.dragas.net/2024/08/29/make-your-own-cdn-openbsd/

Yet another audio post. this is my basic "per-channel" use case for tape emulation. I care about the eq curve here mainly. for most sounds you want to soften the top and bottom.

It is like perfect placeholder EQ + saturation for a channel. Then by adjusting mixer gain I can go a long way before doing anything more sophisticated :-)

Essential tool with #Storj: https://cyberduck.io/

I guess everyone knows this who has used AWS but I experienced S3 storage first time ever last March :-)

#cyberduck

https://github.com/benjojo/dnsfs

To save some time upgrading all U-he plugins I did:

#!/usr/bin/env bash

set -e

wget -q --show-progress -r -np -nd -l1 -A Mac.zip https://uhe-dl.b-cdn.net/releases/ -P dl/
for file in dl/*.zip; do unzip -j -o "$file" -d staging "*.pkg"; done
for file in staging/*.pkg; do sudo installer -pkg "$file" -target /; done

Not a new one but interesting read (also part 2):

https://research.nccgroup.com/2023/02/06/rustproofing-linux-part-1-4-leaking-addresses/

This is great because MPE-parameters can be misused as automation parameters :-) Less automation curves better...

https://u-he.com/news/#mpe-update

https://www.politico.eu/article/exclusive-telegram-ceo-brother-nikolai-durov-wanted-france-authorities-pavel-durov/

https://www.youtube.com/watch?v=cq4AqVNErqM

Beware, there is an ongoing spambot attack in #GitHub issues in several projects were random people suggest "the fix" is to download a random file from mediafire.com. Like this:

IMHO, the most useful thing in its simplicity at least I've had for MSEG in Bitwig: drop-in replacement for LFO Tool.

I actually still use LFO Tool to "design" the side-chain curve and then just match it with Curves modulator and Tool device.

Actually this is what I do a lot: use VST first given e.g. nicer visual feedback and then replicate with stock devices. Best of both worlds as far as I'm concerned :-)

#Bitwig #BitwigStudio

I could imagine world without virtual memory ;-) Like back 80s memory model. You could have security by CPU enforcing the borders (and actually would address quite many modern attack vectors).

Not a serious proposal. Still would be totally doable. Like if you have 128 GB of RAM with my normal use I could pretty much do all my tasks easily in partitioned environment.