Skip to main content


in reply to GreeNRG

if carnists could read, they'd realize what community they're in
This entry was edited (3 months ago)

in reply to Leaflet

Been a very exciting release.

The nix-darwin upgrades come along right as i migrated my Mac to Nix, but even outside of that, all the package and module merges are always welcome. All my machines run Nix now, so the less work I have to do manually, the better

in reply to dinckel

What made the release exciting for you?

I just roll along on NixOS-unstable, so for me changes just trickle in over time.

in reply to Laser

For nix-darwin specifically, the cleaned up build process, and SDK packaging is nice. It hasn't eliminated all the issues, but a lot of those are less of a fault of Nix, and more an issue with macOS design. Hoping they can be addressed somehow, but for now, the issues with workarounds are tracked.

And just in general, Python has kind of been a pain in the ass to understand, so any improvement is exciting, as i'm still learning how things work here.

A bunch of packages I want got officially merged or updated during this release cycle too, and as much as I appreciate thirdparty flakes, I don't want to rely on them too much

in reply to dinckel

I use QGIS, which needs to stay in sync with a number of Python packages and plugins. I have thought of using Nix for that, but am not sure if everything I need is packaged for Nix.

I’m using Conda now, a Python package member which seems more popular for this niche need.

in reply to Leaflet

On the last day actually, haha

For anyone interested, this was due to a curl regression AFAIK. 24.11 was supposed to release a week ago but a lot of stuff had to be rebuilt.





Fedify 1.3.0 released


This entry was edited (3 months ago)
in reply to Cris

This is the same tool @Ghost.org is (was?) using to bring federation to publishers using the Ghost platform.


Fedify 1.3.0 released


This entry was edited (3 months ago)



in reply to Intergalactic

Why? (I admit I don't know a ton about him except he's an industry plant and that he had to go to the hospital once because he ODed on hot cheetos)


in reply to Leaflet

the Wayland color management protocol might finally be close to merging after four years in discussion.


But also

Going all the way back to January 2020


So really it's been almost 5 years.

Let's hope we can finally get it and move on to any other remaining protocols.

This entry was edited (3 months ago)
in reply to theshatterstone54

HDR is new ground on Linux, so it’s understandable it’s taking a while. It requires involvement from all over the graphics stack: graphics drivers, mesa, Wayland protocol, protocol needs to be implemented in compositor, apps need to implement the protocol.

in reply to db0

You can say anything you want
And you can do anything you wanna do
If you have Ghost
You have everything

in reply to learnbyexample

A user types at a terminal (a physical teletype). This terminal is connected through a pair of wires to a UART (Universal Asynchronous Receiver and Transmitter) on the computer.


Once I had the opportunity to sit at such a machine.

A real typewriter with real paper. And no display! Only paper.

I type my "command line" and it appears on my paper. Ok, where else...

The computer responds by letting it's response appear - what do you think? - on my paper, too. Not by magic, but by my machine typing it.

I am typing to my paper. Then the computer is typing to my paper. And so on.

Hardly ever have I had such a creepy feeling while doing computer work 😵‍💫





Replace Is Number Saves 440GB a week


in reply to ☆ Yσɠƚԋσʂ ☆

Basically it was a two liner dependency and how npm works it doesn’t cache and always downloads all dependencies fresh. This lead to 440GB/Month of traffic in a lage project.

Instead of removing a dependency we should just accept that the entire JS ecosystem is a total ****show and start over

in reply to istdaslol

Not just that, but the standard library and core language semantics like equality are also a total shit show.


Israeli strike kills 5, including three World Central Kitchen workers


Israeli forces targeted a World Central Kitchen (WCK) vehicle in Khan Younis, southern Gaza, killing at least five people, including three WCK workers.

The three WCK workers were identified as Azeem Jalal Abu Daqqa, Ahed Azmi Qudeih, and Mohammed Adel Al-Namla.

This attack is not an isolated incident, with a previous strike in April resulting in the deaths of seven workers.

in reply to geneva_convenience

Even if those workers were not being deliberately killed because of their affiliation with a known humanitarian agency. It shows what is happening to many, with the purposeful eradication of food distribution


This entry was edited (3 months ago)


think of the children


This entry was edited (3 months ago)
in reply to Tux

Did someone actually find a backdoor in Recall, or is this just the usual "M$ is evil" posting?

(Either way, fuck ~~Recall~~ Security Exploit Centrap)



Russia uses custom Linux - awake nerd


reshared this

in reply to Ahri Boy 🏳️‍⚧️

Im just waiting for some capitalist to call Linux inc out for supporting the russians
in reply to Luffy

They've sanctioned the Russian driver maintainers, it's probably enough
in reply to Ahri Boy 🏳️‍⚧️

Lots of weird typos in that article, and it reads more like a fluff piece than anything but it's hard to find any actual reporting on this shift. Here's a ZDNet article on the subject (unless ZDNet's gotten better since I last did, don't open without an ad blocker). Thanks for sharing!