RE: https://owo.cafe/@stage7/114760041821102294

#InternationalDayOfLatex × Pride × Drawing I did last year.

PSA for #AsahiLinux users: Do NOT upgrade to macOS 27 Golden Gate!

Apple has changed how the boot picker and Startup Disk applications detect valid OS boot volumes. When using either from macOS 27, your Asahi partition will not be visible! We believe this to be a bug, and have filed a report (FB22994760).

If you have already upgraded to the beta and noticed that your Asahi partition has disappeared, do not stress. Your Asahi partition is still there, and you have not lost any data.

If you have already upgraded to macOS 27 and have a secondary installation of macOS 26 or below, set this as your default Startup Disk to restore access to Asahi. The Apple Silicon boot picker is a full-fat macOS app running in the default boot volume's recovery environment, so its behaviour is dependent on the default boot volume's macOS version.

If you insist on trying out macOS 27 as soon as possible, please ensure you install a secondary copy of macOS 26 first, or install macOS 27 itself on a secondary volume. We will not support users who have installed the macOS 27 beta without making contingency or rollback plans (such as ensuring at least one stable macOS version is installed).

We have patched the Asahi Installer to prevent it from running on macOS 27 until we have some idea of what's going on. It will print a version of this message and then exit if you try to run it from the macOS 27 beta.

The four organizations who maintain your favorite open-source DNS software, ISC, CZ.NIC, PowerDNS and NLnet Labs, gave a lighting talk at @dnsoarc 46 about the avalanche of LLM-assisted security reports for their projects, and the effect it has on us and our users.

The last slide ends on a “Hug your OSS maintainer" note, but I think this is understating the gravity of this situation. I hope we put forward a stronger message during the repeat of this presentation at RIPE 92.

People need to consider that we are in a situation where developers with talent, purpose and experience have created something valuable for the internet community over the last 20+ years. They could have chosen to work at $MEGACORP for twice, three times the pay, but they chose to do something meaningful.

Now, the body of work they carefully designed and maintained over the last decades is being picked apart by an LLM. Yes, as a result the products become some definition of “more secure” but there is no reasonable prospect that this avalanche of reports will end. Ignoring them is not an option. Feature development has come to a halt.

As an employer, what am I supposed to tell my developers? Thanks for creating this amazing DNS software over the last 20 years, it looks like you’ll spend the next couple of years triaging and fixing bugs and coordinating CVEs with your peers.

How do we keep people motivated to do open source and even if we do, how do we keep this development model sustainable? We can’t pivot to the ‘agentic era’ just like that and even if we could, I think my colleagues do this job to create something amazing—artisanal if you will—not to to maximize output at all costs so shareholders get rich.

Practically though, encouraging organizations to purchase a support contract will certainly help on the short term, because:

- You will get access to world class support;
- You will get early security vulnerability notices under NDA, keeping your critical infrastructure safe from a whole new class of LLM fueled risks; and
- In the grand scheme of things, you will help keep this open source model sustainable so your favorite DNS software continues to exist and thrive.

#DNS #LoveDNS #LLM #FOSS #OpenSource #RIPE92

https://indico.dns-oarc.net/event/56/contributions/1233/

This thread is such a massive failure of the community bug reporting process.

https://www.reddit.com/r/Fedora/comments/1s8jevj/a_message_to_fedora_devs_please_stop_interfering/

Apparently there's a small but significant fraction of users who see their browser home reset to the Fedora Home on Firefox updates or other circumstances... and they're all convinced this is some kind of evil intentional Fedora packaging feature that hijacks your preferences on every update, and that it must happen to everyone (it does not).

So far there is one known hypothesis for why this can happen (it involves Firefox Sync), but that doesn't cover all instances because some affected users claim not to use Sync. I reported this one upstream so hopefully there will be a solution soon. Nobody had until now...

Meanwhile, not a single affected user has bothered to write up reliable repro steps or follow through with maintainers on tracking down the root cause.

I've also looked at upstream bugs and found several shaped like "Firefox lost my prefs on upgrade", but none of them were followed through to a root cause either.

Of course, when Firefox loses the home page pref and it reverts to about:home, people shrug and set it back... but when Fedora Firefox does the same and it reverts to start.fedoraproject.org, it's clearly a Red Hat conspiracy to hijack people's browsers and they demand Fedora remove the default home page branding override entirely, instead of working with a developer to get the bug fixed...

the precise timeline of how OpenAI fucked over the RAM market

> October 2025: Sam Altman flies to Seoul and signs simultaneous deals with Samsung and SK Hynix for 900,000 DRAM wafers per month. That's 40% of global supply. Neither company knew the other was signing a near-identical commitment at the same time.

https://xcancel.com/aakashgupta/status/2038813799856374135

edit: this guy is a seriously bot-pilled pumper, but this seems to be a good summary of known facts. doubt the AI memory use trick he mentions is load bearing tho.