2·
16 days agoHm, also not a big fan of that loon, bit at least consistency is better.
it just feels too overloaded and busy for my liking :/
bright_side_
- 0 Posts
- 12 Comments
Joined 9 months ago
Cake day: September 3rd, 2025
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
4·20 days agoI tried looking into it but I did not find that much info. there are some Iranian hacking groups linked to the state or are state funded and 313 team seems to be linked to those. This is one of the better overview articles I found:
I mean…
This is so cool
I bet the gradient of the beam looks great on a crt
There are a few interesting topics you mentioned Here that I was not aware of. Thanks!
As said, xfce or mate as desktop environment instead of cinnamon might give you enough for what you want to achieve
Its a slow CPU, but will do fine for SNES emulation. But if you already have 24.04 on it (or is this a live boot), just go ahead and try. Might be fine. Xfce if it is just too slow to use but I would even give a “normal” KDE or gnome distro a shot.
I… like it 👀
Ooooh 😔
Just started looking into her work, sad to read her time has passed.The picture is fantastic, I’m fascinated by apes.
thanks for sharing.
the linked source is the kernel mailing list.
https://lkml.org/lkml/2026/5/17/896
"
From Linus Torvalds <>
Date Sun, 17 May 2026 14:29:22 -0700
Subject Linux 7.1-rc4
You all know the drill by now - another week, another release candidate.
Things continue to look fairly normal (where “normal” is the “new
normal” with a fair amount of changes). Drivers are about half the
patch, with GPU leading the way as is tradition. But there’s a little
bit of everything in driver land.
The rest is mostly networking, core kernel, filesystems, and arch updates.
Some of the documentation updates might be worth highlighting: the
continued flood of AI reports has basically made the security list
almost entirely unmanageable, with enormous duplication due to
different people finding the same things with the same tools. People
spend all their time just forwarding things to the right people or
saying “that was already fixed a week/month ago” and pointing to the
public discussion.
Which is all entirely pointless churn, and we’re making it clear that
AI detected bugs are pretty much by definition not secret, and
treating them on some private list is a waste of time for everybody
involved - and only makes that duplication worse because the reporters
can’t even see each other’s reports.
AI tools are great, but only if they actually help, rather than cause
unnecessary pain and pointless make-believe work. Feel free to use
them, but use them in a way that is productive and makes for a better
experience.
The documentation may be a bit less blunt than I am, but that’s the
core gist of it. So just to make it really clear: if you found a bug
using AI tools, the chances are somebody else found it too. If you
actually want to add value, read the documentation, create a patch
too, and add some real value on top of what the AI did. Don’t be the
drive-by “send a random report with no real understanding” kind of
person. Ok?
"