Strit

This seems newsworthy.

The 2 lead project members have left the project for different reasons.

They state that the project will continue as it has always done, since it has a council (which I didn't know), so we shouldn't worry.

There was an argument regarding AI policies in the projects between some of the core contributors, which I think has influenced some of this decision.

There is currently a malicious attack going towards the AUR, in the form of a botnet impersonating git users/maintainers to take over packages and adding a malicious payload.

Arch team is aware and working hard to reset/delete the affected commits and packages.

Not properly released on kernel.org yet, but 7.0 has been tagged on the kernel git repository.

Four years since the launch of the Raspberry Pi 4, the Raspberry Pi 5 has arrived with a performance boost and house silicon that adds support for PCIe 2.0.

FOSDEM is a conference where thousands of open source developers meet and learn.

Location is as always in Bruxelles, Belgium, Europe, Earth.

Any of you going this year?

Hi all.

Happy KDE Plasma user for a long time and I generally love the desktop experience. But I do have one small issue.

At work, I have 2x 4K displays. connected through a Dock. But in Plasma it's only able to give me around 1080p resolution on both of them. In contrast, the display manager SDDM and TTY displays 4k on each fine.

So am I missing a trick to get the max resolution in Plasma? My install is Arch Linux, kernel 6.4.12, Plasma 5.27, Wayland session.

I did install the displaylink AUR package, as I thought it might be the dock limiting the video output, but it isn't as TTY and SDDM seems to display it correctly.

Happy to hear any thoughts and any ideas. :)

EDIT: The screens turn on and work fine with 4K resolutions in a Plasma X11 session.

tværpostet fra: https://lemmy.dbzer0.com/post/3076577

I posted the other day that you can clean up your object storage from CSAM using my AI-based tool. Many people expressed the wish to use it on their local file storage-based pict-rs. So I've just extended its functionality to allow exactly that.

The new lemmy_safety_local_storage.py will go through your pict-rs volume in the filesystem and scan each image for CSAM, and delete it. The requirements are

• A linux account with read-write access to the volume files
• A private key authentication for that account

As my main instance is using object storage, my testing is limited to my dev instance, and there it all looks OK to me. But do run it with --dry_run if you're worried. You can delete lemmy_safety.db and rerun to enforce the delete after (method to utilize the --dry_run results coming soon)

PS: if you were using the object storage cleanup, that script has been renamed to lemmy_safety_object_storage.py