hated on the thing since I first spotted it and dismissed it, never to think about it again - doing everything wrong and then adding the shittiest of solutions, who's gonna fall for that, right? but that thing is gaining and this post and recent threads just make me irrationally angry.

oh, the thing is also vibecoded. if you had any reservations about letting this idiocy loose on your data, there's a relief, huh? head bozo detects ever-so-subtle AGI whilst slop-fondling and easily "verifies" 30K LoC that was shat out. stomach-churning shit.

not to mention, said bozo is doubling down on his fash idiocies. I wish I was making half of this up.

Scc is a sparrow plugin that could be run over terminal to check security best practice of your Linux conf files :

• sshd
• sudoers
• bind
• redis
• sysctl

more services are coming , check it out and let me know what you think https://github.com/melezhik/sparrow-plugins/tree/master/scc

Sorry its been so long since there was an update regarding this project.

Per my last post, (which can be found here: https://lemmy.zip/post/53113975), I continued to mess around with a mobile broadband modem, and got it working! With a caveat... it only works when plugged into wall power. The battery I have does not supply enough power to fully enable the modem through USB power, due the raspberry pi being very power hungry. Unfortunately, this seemingly simple problem is actually a larger problem that seems to only be solved by an overly complicated solution: designing a custom battery controller PCB that responds to the pi5's (or ideally, a different processor entirely) needs more appropriately.

Take a look at the state of the device here:

Last time I posted here, many interested folks responded with great ideas and feedback. Fortunately, one of the comments lead me to the project that would ultimately end this project in its current state. Link to that comment here: https://lemmy.zip/post/53113975/22779544

Its flaws are visible. While the device has personality, it lacks ease of use. These days I use it as a "cyberdeck"/field debugging computer, and I use it with a small controller-sized Riitek keyboard, because the screen's touch capability is on the fritz, likely because of the poor design choice to leave the screen's ribbon cable partially exposed.

This leads me to the conclusion: this project is falling into "hobby" or more accurately, unsupported status. I like the device for my personal use, and I may update the design in the future for my own purposes, and release it for free for public use, though I don't imagine there will be a huge amount of interest in building this device considering the skyrocketing cost of Pi devices nowadays. There is a more reasonable path forward, and I alluded to it earlier: custom PCBs. That's where the SPIRIT project comes in: https://github.com/SPIRIT-org/SPIRIT

You can see in one of the pictures above, the SPIRIT project is designing a phone that can be completely replicated at home. Well, once they get there it will be. I've exchanged brief communications with the individual running the project, Jan, and while he hasn't stated that these projects are linked in any way, I'd like to think that the SPIRIT project carries forward the values and goals of the project I started. If you were at all interested in my project, give the SPIRIT project github a like or favorite.

Take a look at the v3lectronics youtube channel where Jan livestreams work on the SPIRIT project: https://www.youtube.com/@V_Electronics

The spirit github link again: https://github.com/SPIRIT-org/SPIRIT

Please contribute if you have any level of knowledge to contribute! These projects thrive on the careful contributions of other humans across the world!

Just learned about it recently. It has received a lot of praise as a rolling release distro. Also it uses runit instead of systemd.

It has been praised also for being more stable and better designed than Arch.

And I wonder how it compares to OpenSUSE Tumbleweed,

I have a number of hints that my internet connection doesn't work right. I see things like can't connect to addresses from docker, pages will be slow in my browser. Before I used ethernet to my router, I would sometimes disconnect from the internet. Aside from disconnecting, none of it was a clear sign something is unusually broken. Is there some linux (Ubuntu) tool I can use to assess the long-term health of my connection?

A nice to have: the tool would tell me whether a fault is in my drivers, settings, adapter, router, connection to the house, or my provider.

For those interested on the question of age verification and GNU/Linux: be aware that Systemd v261-rc1 was recently released. It now implements an optional birth date field in the JSON user database (see second item under "Other changes").

The implementation of this field was prompted by age-verification or -attestation laws.

(Age-verification status of Open Source Operating Systems.)

Writeup by @pglpm@lemmy.ca

looking for non-systemd solutions out there and thought I'd share this, didn't see it posted.

if you haven't seen any of tony's videos, you're in for a treat. enjoy!

cross-posted from: https://feddit.org/post/30198502

System:

Debian 13 KDE (actually MX Linux, but doesn't seem to matter)  
Wayland (xwayland installed as well)  
Docker 29.5.2

Dockerfile:

FROM debian:trixie

ENV DEBIAN_FRONTEND=noninteractive
ENV LANG=en_US.UTF-8
ENV LANGUAGE=en_US:en
ENV LC_ALL=en_US.UTF-8

# Set locale
RUN apt-get update && apt-get install -y --no-install-recommends \
        locales && \
    apt-get clean && \
    sed -i '/en_US.UTF-8/s/^# //g' /etc/locale.gen && \
    locale-gen

# Install Wayland-specific packages
RUN apt-get update && apt-get install -y --no-install-recommends \
        dbus \
        libwayland-client0 \
        libwayland-egl1 && \
    apt-get clean

# Install X-specific packages
RUN apt-get update && apt-get install -y --no-install-recommends \
        dbus-x11 && \
    apt-get clean

# Add contrib, default is only main
RUN sed -i 's/^Components:.*/Components: main contrib/g' /etc/apt/sources.list.d/debian.sources

# Add 32-bit arch for Steam libraries
RUN dpkg --add-architecture i386

# Install Steam
RUN apt-get update && apt-get install -y --no-install-recommends \
        steam-installer \
        pciutils && \
    apt-get clean

# Additional
# TODO: What is really needed?
RUN apt-get update && apt-get install -y --no-install-recommends \
        vulkan-tools \
        mesa-utils \
        x11-xserver-utils \
        libvulkan1 \
        mesa-vulkan-drivers && \
    apt-get clean

# TODO: Does `-storebeta` even work?
# https://developer.valvesoftware.com/wiki/Command_line_options_(Steam)
CMD ["/usr/games/steam", "-storebeta"]

To run the container:

xhost +
sudo docker run -it --name steam \
    -e XDG_RUNTIME_DIR=$XDG_RUNTIME_DIR \
    -e WAYLAND_DISPLAY=$WAYLAND_DISPLAY \
    -v $XDG_RUNTIME_DIR/$WAYLAND_DISPLAY:$XDG_RUNTIME_DIR/$WAYLAND_DISPLAY \
    -e DISPLAY=$DISPLAY \
    -v /tmp/.X11-unix:/tmp/.X11-unix \
    --privileged steam:trixie

(The --privileged part is only temporary until I found out which capabilities are actually needed. Please don't run your containers with --privileged.)

I get the GUI dialogs to download Steam just fine, so at least some display forwarding is working:

The installation works fine, but when starting Steam it seems like it's not able to find Vulkan devices and then doesn't open any Steam window. (The container is not stopping and I'm seeing repeated ./steamwebhelper output after this.)

[...]
Running query: 1 - GpuTopology
CVulkanTopology: failed create vulkan instance: -9
CVulkanTopology: failed to create vulkan instanceFailed to query vulkan gpu topology

Failed to query vulkan gpu topology
Response: 
Exit code: -2
[...]
Vulkan missing requested extension 'VK_KHR_surface'.
Vulkan missing requested extension 'VK_KHR_xlib_surface'.
BInit - Unable to initialize Vulkan!
[...]

However, Vulkan is clearly working fine in the container, as this commands displays the cube rendering just fine:

$ sudo docker exec -it steam vkcube
Selected WSI platform: xcb
Selected GPU 0: AMD Radeon RX 550 / 550 Series (RADV POLARIS12), type: DiscreteGpu

(I've also tried it on another (pure) Debian machine with a 2080Ti, but I've got the same issue.)

I've created other GUI containers in the past (Firefox for example) and didn't have these problems.

Does anybody have an idea and can point me in the right direction?