The onslaught includes LLMs finding bogus vulnerabilities and code that won't compile.
arstechnica.com/security/2026/…
I am strongly considering shutting down Pomf because the US Department of Justice continues to manufacture outright lies against people who are innocent until proven guilty.
Running the service (despite my best efforts to mitigate risks well beyond what the law would require me to do up to and including full fledged cybersecurity research) exposes me to some level of legal or criminal threat to my livelihood. I knew this going in five and a half years ago, and the calculation at the time was acceptable because even if the feds came knocking at my door, I was confident the evidence would be in my favor and that a reasonable and functional court system would make the right decision. I was also confident that what happened to Les De Ridder almost eight years ago (archive.is/PJTzS) wouldn't happen here in the USA, because Europe was a communist shithole and we had rights over here.
Well, as the US continues to backslide into a fascist regime with a completely captured judicial branch that is utterly subservient to the executive branch, my evaluation of that risk level compared to my maximum tolerance of risk continues to inch closer and closer to parity, and when that risk exceeds it, I am out. If I am not convinced that I can adequately defend myself against potentially spurious claims and threats due to a corrupt and unequal justice system, then my next defense mechanism is to remove any and all ammunition from those who would try to harm me, and the largest weapons cache someone can bring to bear against me at this time is undoubtedly Pomf. I have never considered the government to be part of my overall threat model, but now I do, and I do not have the energy or resources to fight an entire government at this time despite it being morally the right thing to do.
If this does happen, there will be a reasonable and well defined sunset period, with a final archiving of all Pomf content to cold storage in hopes that in the distant future the risk comes down to a level in which I am comfortable bringing it all back online. I would never wipe Pomf - only make it unavailable at worst.
One last thing - if you think I am some big baby or think I have nothing to fear, consider this simple statement:
If they can do it to them, they can do it to you.
Qwen3-TTS Family is Now Open Sourced: Voice Design, Clone, and Generation
I haven't been paying much attention to the state-of-the-art in speech generation models other than noting that they've got really good, so I can't speak for how notable this new …Simon Willison’s Weblog
I see Node.js tries to solve the AI slop issue on hackerone like this:
require a Signal of 1.0 or higher
nodejs.org/en/blog/announcemen…
Node.js — New HackerOne Signal Requirement for Vulnerability Reports
Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts.nodejs.org
For the last decade, the #EU has been funding #Mastodon #KDE #Phosh #Nextcloud #OnlyOffice #PixelFed, #Libreoffice, #CryptPad, #Kdenlive, #Lemmy and many other Open Source projects you know and love through its #NextGenerationInternet programme.
But now that programme is ending and they are thinking about its successor.
They want to hear from you on what it should look like: Share your feedback to make sure the Commission keep funding amazing Open Source projects!
reshared this
AI is the recuperation of the anti-copyright critique.
“Plagiarism is necessary. Progress implies it.” Lautréamont, 1870
1/8
Anti-copyright has been fully recuperated, and it feels like only a matter of time before a tech billionaire claims that ingesting copyrighted material into AI is détournement.
However, only when it is an input to production.
7/8
8/8
A woman who I follow on the fediverse just had to delete a post due to sexual harassment.
Men if you want more diversity on the Fediverse you need to speak up and call in your peers. You need to educate them and if they persist ban them. Make it clear they aren't welcome.
Otherwise you're making it clear we aren't welcome.
It shouldn't just be us doing the work
Rust 1.93.0 has been released! 🌈 🦀✨
This release includes a new musl version for the *-linux-musl targets, adds support for #[cfg] inside asm!(), and adds [T]::as_array, VecDeque::{pop_front_if, pop_back_if}, Vec/String::into_raw_parts, fmt::form_fn, and more! ✨
Check out the blog post and release notes for all the details: blog.rust-lang.org/2026/01/22/…
Announcing Rust 1.93.0 | Rust Blog
Empowering everyone to build reliable and efficient software.blog.rust-lang.org
U.S. firm involved in Quebec's digital health records is sued by Texas
> A U.S. software engineering firm that’s responsible for Santé Québec’s two pilot projects involving digital health records is being sued by the state of Texas [...] and is maintaining a monopoly that has proved costly to taxpayers.
> Santé Québec, however, is standing by Wisconsin-based Epic Systems despite cost overruns for its projects of nearly $135 million to date.
montrealgazette.com/news/local…
U.S. firm involved in Quebec's digital health records faces major lawsuit in Texas
The lawsuit alleges Wisconsin-based Epic Systems restricts parental access to children's medical files and is maintaining a monopoly.Aaron Derfel, Montreal Gazette (Montreal Gazette)
Liam Erven
in reply to Josh • • •Liam Erven
Unknown parent • • •