Goofed Home

Breaking bad was just a practice run for better call Saul.

The prequel and the original trilogies just enjoy nostalgia glasses, Rogue One is the best movie and it’s not even a competition.

@secbox No, sorry. ATM there isn't even an implementation complete enough to use for myself, let alone have others use it. Working hard on it.

I hope to soon have it good enough to use it for myself. Then the next goal is to make it usable for others in their own installations. Only then I look forward to be able to provide an instance for others to use.

If anyone volunteers to run such an instance, get in touch and I'll make sure to push features you need for that.

@rs3 @wessi

Yes, #FediHired was one of the inspirations. 🙂

@zockbursche

No, it's not two way. Just what I push on Codeberg is mirrored to GitHub, and GitLab. Those mirrors are for visibility, development happens on Codeberg.

@julian@activitypub.space yeah, i know 🥲
I have a lot of things I wanna do on Misskey/Sharkey - give me a few more months and this will be totally transformed =)
@evan@cosocial.ca

Hi everyone, I’m running KDE Plasma 6 with Wayland and I’m trying to find a way to turn on the screen programmatically via the command line. In X11, I could use xset dpms force on, but this doesn’t work in Wayland due to its security model. Has anyone found a reliable method to wake or turn on the screen from the command line in a Wayland session? I’m aware of the security and architectural reasons behind this limitation, but I’m curious if there are any workarounds, compositor-specific DBus calls, or third-party tools that might help. What I’ve tried so far: xset dpms force on (fails, as expected)

Simulating keyboard input with wtype/ydotool (unreliable)

Checking KWin’s DBus interface (no obvious method exposed)

Context: I’m automating some tasks and would like to avoid switching back to X11 just for this feature. Any insights, scripts, or suggestions would be greatly appreciated! Thanks in advance for your help.

Thank you for sharing your setup. Your solution using wlr-randr in a cron job is indeed useful for wlroots-based compositors (such as Sway, Hyprland, or labwc), where the wlr-output-management protocol is supported.

For those (like me) encountering the error ‘compositor doesn’t support wlr-output-management-unstable-v1’, this indicates that the compositor in use (e.g., KDE/KWin, GNOME/Mutter, or other non-wlroots compositors) does not support wlr-randr. In such cases, alternatives should be considered.

I will be post my findings, I can’t believe I’m the only or just one of the few looking to archive this in a laptop..

This works!

Key Commands

1. List Connected Displays To see all connected outputs and their status:

kscreen-doctor -o``

Example output:

Output: 1 eDP-1
        enabled
        connected
        Modes: 1:2560x1600@60.00*!

This helps identify your display names (e.g., eDP-1 or HDMI-A-1).

1. Turn Off All Displays (DPMS) To put all displays into low-power mode:

kscreen-doctor --dpms off

Uses DPMS (Display Power Management Signaling) to turn off displays safely.

1. Turn On All Displays To wake all displays:

kscreen-doctor --dpms on

1. Disable/Enable a Specific Output To control a specific display (e.g., HDMI-A-1):

kscreen-doctor output.HDMI-A-1.disable kscreen-doctor output.HDMI-A-1.enable

Note: Avoid disabling your primary/laptop panel (e.g., eDP-1) unless you have another display connected.

1. Bonus: Adjust Brightness or Scale

kscreen-doctor output.eDP-1.brightness.50 # 0-100 kscreen-doctor output.eDP-1.scale.1.5 # Scale factor

The GNOME Project released GNOME 49.5 today as the fourth point release of the latest GNOME 49 “Brescia” desktop environment series with more bug fixes and improvements.

Coming one and a half months after GNOME 49.4, the GNOME 49.5 release is here to improve accessibility of app folders in GNOME Shell, respect the –force-animation flag in remote sessions, improve keyboard layout changing, and improve re-enabling of the touchscreen after exiting Power Save mode.

Epiphany (GNOME Web) web browser reverts to the original AdBlock filters used before version 49.4, fixes a regression in site compatibility due to adblocking, and adds support for running Web Apps in the background, with configurable toggle and quit action, even when not using the Flatpak sandboxed app.

“Wake me up when they’re in stores”
“Another battery technology we’ll never see.” “Sure, just like the last 3000 that never went anywhere.”

Ok, with that out of the way – Cool technology, seems like it can be used for quite a few applications. If I’m understanding this right, it seems like it’s a solar cell + battery in one process? So it absorbs light and can release that energy as needed?

Feels like that can be used for a lot of off-grid tech. Solar powered lights, rural villages, general infrastructure that doesn’t need to be hooked up to anything.

I could be reading this wrong, cause funny-words-magic-man-speak is kinda obtuse.