🖖Calling all Star Trek fans … new Trek in Time video episode is out on my other channel: https://youtu.be/YptDHoaavHo Audio: https://shows.acast.com/trek-in-time/episodes/6a4e3c6b1c8f5a97d84fc1ed Sean and I talk about what killed Star Trek in Star Trek TOS Season 3, Episode 16, “The Mark of Gideon.”
Language disparities are just one of several concerns as automated moderation becomes more widespread. The varied examples we share here demonstrate the risks of over reliance on automated moderation—and the need for stronger safeguards. https://eff.org/deeplinks/2026/07/part-2-automated-moderation-here-stay-accountability-must-keep-pace
Give yourself a mid-year gift with new EFF swag! Support for as little as $10/month to receive our new Claw Back t-shirt 😼 https://eff.org/summer
@simplenomad I’ve done several things like this and requested passing the EFF. The taxes weren’t going to be worth it
Has anyone ever refused a bug bounty payment? Curious….
I mean, if the only way to report a bug to some company is via a bug bounty program, is it possible to say “no thanks” on the payout? Or have them donate it to the #eff? I’d be interested in hearing about any such thing happening.
AI - especially agentic AI - is inadvertently creating more technical debt. But there are a few steps one can take to help mitigate the situation.
https://www.markloveless.net/blog/2026/7/2/ai-and-technical-debt
Fairly recently someone asked me about naming a vulnerability, as they were looking for suggestions. Since I kind of hate that sort of thing, I came up with the name of "Fuck". The response was something along the lines of "I can't name it that, Marketing won't like it." Yeah well, it doesn't have to be named. It just needs to be reported, fixed, and patched.
BTW if anyone catches the slight nod to Dan Farmer and his Satan tool followup, you're quite cool (and old).
Thank goodness this happened. Defenders seriously need access to Fable and Mythos.
The full moon in Arlington Texas last night was particularly interesting looking due to the haze from dust blown in from the Saharan desert (yes, across the Atlantic).
Hello fellow nerds. If you and/or your company has access to the new OpenAI models (their "Mythos" versions) the rest of us would love to hear about how good or overhyped they are.
https://thehackernews.com/2026/06/openai-limits-gpt-56-rollout-as-sol.html
I know this happened a few months ago but it is just now making the rounds via social media outside of Germany. What a sick burn.
From last April, I somehow missed this so maybe others did too. Regardless, it's fucked up.
https://futurism.com/artificial-intelligence/ice-facial-surveillance-glasses
Huh! I was today years old when I realised that the mighty @libreoffice has a great tool for generating QR. In a world where online QR code generators tend to re route via themselves this is an awesome tool to find! #opensource
The good news? Power outage this morning but the home battery setup kept all of the critical load circuits active (HVAC, frig/freezer, servers, a few other minor things) with no down time. The bad news? All of the smart switches on non-critical load circuits did NOT come back on via the Home Assistant automation I created. I had to do it manually like a neanderthal.
Looks like my blog post (https://www.markloveless.net/blog/2026/6/18/quantum-safe-openssh-and-openssl) from last Thursday on configuring OpenSSH and OpenSSL to make them quantum safe was more timely than I thought.
A new executive order from yesterday is summarized here:
https://thehackernews.com/2026/06/trump-order-sets-2030-deadline-for.html
Happy Fathers Day to all of the fathers out there in the #fediverse. And of course blessed #midsummer and happy #litha to all!
Since both myself and hellNbak were laid off recently, it seems we both have decided to make sure various coding side projects from the past year or so have been brought forward - especially hellNbak. Anyway, enjoy the fruits of NMRC labor.
Recently I blogged about the dangers posed by “harvest now, decrypt later” in relationship to quantum cryptography, and I even released a tool to assess local and remote systems running SSH and HTTPS. Now I have a new blog post where I outline configuration settings for servers running OpenSSH and NGINX to address the threat. The threat is small, but eventually your boss will ask and you can say “we already took care of it”.
https://www.markloveless.net/blog/2026/6/18/quantum-safe-openssh-and-openssl
