⊥ᵒᵚ Cᵸᵎᶺᵋᶫ∸ᵒᵘ ☑️ @falken@qoto.org

I am currently conversing in a forum thread about Linux Audio, and a couple of developers are saying that it is not worth it to develop for Linux. They are complaining that Linux users are only a tiny fragment of the population, and it is a waste of development time.

Is there developer here in the Fediverse that can give me some positive quotes of their experiences in Linux Audio development that I can give to balance the argument a bit?

#Linux #LinuxAudio #MusicProduction #Plugins #VST3 #FOSS

can't help getting astrology × audiophile vibes from llm enthusiasts: "oh no honey you can't use opus 4.8, it's so nerfed, try glm-5.2 or the codex 5.5, they have a warm gemini sound, very well rounded on details and tone. but don't use google's gemini models, they are really leos, they have good treble response but you can't trust their mid-range"

⭐ Nearly a Million Passports Just Exposed on the Public Internet https://cambridgeanalytica.org/data-breaches-scandals/passports-driver-licenses-exposed-public-internet-2026-51096/

"a platform that manages membership and age verification"

And this is why I will stand firm on never uploading ID documents to an age verification service. I will stop using the internet before I hand that over.

∞ https://rknight.me/links/nearly-a-million-passports-just-exposed-on-the-public-internet/

This is why @pluralistic is always preaching about #DRM-free digital media and software. Sony is deleting over 500 movies customers paid for through the PlayStation Store because they don’t want to renew their license with Studio Canal. #enshittification

@ChrisMayLA6 As a seasoned and amoral grifting fascist I’m sure Fartage will find some equally nefarious ways of topping up his Coutts bank account.

46 years ago today

"Love Will Tear Us Apart" is a song by English post punk Joy Division, released on this day in 1980 as a non-album single

#punk #punkrock #postpunk #lovewilltearusapart #joydivision #history #JoyDivision #otd

Do you think we'll be saved?

Right, that's a bunch of #libreoffice patches merged for the big memory usage bug I've been working on for a while; the original one was using ~10G and is now under 2G, and the BIG one is down from 185G to 45G.
So I've closed the 10yr old bug that complained about the 10G case crashing; onto just doing stuff on the big one.
I've got some ideas left - not sure how far I can take it.

Home Office knew AI age checks for migrant children were flawed – but rolled it out anyway – The Home Office knew an AI tool that would be used to check the age of small boat migrants was flawed but pressed ahead with its rollout anyway, The Independent can reveal.

https://www.the-independent.com/news/uk/home-news/ai-migrant-border-age-technology-home-office-b2994568.html

Do you live near a data center that makes a noise loud enough to bother you in your home? If so, please DM me. Also, please boost this so I get some responses. I need some information.

Just filed an EU DMA complaint against Alphabet for gatekeeping against secure Android derivatives like @GrapheneOS via Play Integrity.

TL;DR: not certified ≠ not secure. Google lacks a FRAND certification process for non-OEMs that comply with objective security requirements.

*gently grabs the cheeks of all programmers to stare deeply into their eyes*

All I want is a dry tech manual. A boring, well indexed manual that defines every function. Not a chatbot. Not a training. Not a million "articles" that I have to search through. Not a "community forum".

My rice cooker came with one. I want one for every piece of software I have to interact with.

Go get yourself a technical writer if necessary.

I. Want. An. Instructional. Manual.

A while ago I heard someone describe LLMs as "like having a clueless junior engineer working under you - one who knows every language and nothing about architecture".

I'm inclined to agree... in the hands of an expert they save a decent amount of grunt work (especially painful copypasta refactoring). If you don't review the output though, you're likely to be chasing bugs and slop for ages.

@eliasp Also, the KHTML and KJS code did not suck. It was rather incomplete and raw, but it was well-written and something I knew could be a project my browser-inexperienced team could learn on.

It wasn't until I lured David Hyatt away from Mozilla, after he started Firefox, that we really began to change KHTML and KJS.

Hey private enterprise enthusiasts. You believe that the public sector can save money by handing over utilities to companies, which are inherently more efficient.

Here's why this doesn't work.

You have to pay someone to monitor the private companies. Because they have no incentive to deliver what they promised. They always cut corners in the name of profit. And that monitoring eats the savings you hoped for. While you have no control over your utilities.

#capitalism

It's been over 6 years since I moved in here and I've only just realised that the reason the lights in the extractor hood don't work is that nobody had ever installed any bulbs in it

Nature published a peer reviewed paper arguing that Microsoft's claims of a quantum computing breakthrough last year are based on bugs in their Python code and selectively choosing which data to base their results on.

The author of the paper claims "I demonstrate that Microsoft's tune-up software is flawed and that coding errors resulted in incorrect statements to peer reviewers"

This is extremely embarrassing for Microsoft and they've pushed back on the paper's claims.

https://www.theregister.com/research/2026/06/24/boffin-claims-microsofts-supposed-quantum-leap-does-not-compute-due-to-basic-python-errors/5260489