Migrated to @autumn@autumn.moe

Migrated to autumn (npub1w8d…slcy)

Migrated to: autumn (npub1w8d…slcy)

Last Notes

2025-07-04 13:45:30 GMT

to the idiots using xlibre: this is the code quality of the changes
https://media.idtech.space/media/8c/7b/4f/8c7b4f0bc32b71cd15e985a9fd52d9d257ac1b435174b2a7455f95e7e32b8cd5.png

2025-01-16 18:22:08 GMT

what the FUCK does Jack Dorsey know about "Open Source Culture"?!
https://media.idtech.space/media/ea/a4/23/eaa4230a0a4775079a5d16dc9c853a2b7653f42b727fee8bba36fd98933e5099.png

2024-12-02 13:57:24 GMT

- reply

nah, networked apps are unsafe.
but yeah.

2024-12-02 13:47:40 GMT

psa: the music player can read my music folder
no freaking way... im freaking out right now about this... i didn't realise that.
uninstalling this unsafe application!!!
the flathub "safety" guidance is such a fucking joke it's not even funny.
https://media.idtech.space/media/f4ea4e32214861557e4e6fc314cfc812f272721148050d62d45a4da9a4ba2efc.png

2024-09-23 21:10:25 GMT

Announcing: **Frog Protocols for Wayland** 🐸
*Let's create Wayland Protocols but much more iterative.*
Wayland Protocols has long had a problem with new protocols sitting for months, to years at a time for even basic functionality.
This is hugely problematic when some protocols implement very primitive and basic functionality such as `frog-fifo-v1`, which is needed for VSync to not cause GPU starvation under Wayland and also fix the dreaded application freezing when windows are occluded with FIFO/VSync enabled.
We **need** to get protocols into end-users hands quicker! The main reason many users are still using X11 is because of missing functionality that we can be shipping today, but is blocked for one reason or another.
Check out the repo here!
https://github.com/misyltoad/frog-protocols
and the Mesa MR that adds support for frog-fifo-v1 to fix these issues and goes into much more detail:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31329/

2024-07-30 02:11:12 GMT

https://media.idtech.space/media/f67e935a8ad21e1bd1225fa016b5b8d06a59a5b254a77a83cf40539488351b03.png

2024-07-03 13:13:54 GMT

I am having a horrible time trying to make Gamescope's shutdown more robust.
It essentially needs to act as a subreaper that also kills all of it's children on death -- even if Gamescope crashes.
Why is that so damn hard and annoying to implement? I feel like I am missing something obvious.
I've tried signal handler stuff, a child watchdog process that kills all of it's children, but nothing seems perfectly robust.
What am I missing?

2024-05-14 03:36:35 GMT

- reply

Some cat gimmick account that reposts other people's content, made a post announcing you can now subscribe to them.
I QT'ed with "Why the fuck would I pay you to repost other people's content, you grifting fuck."

2024-05-14 02:59:53 GMT

Looks like I angered the vocal dumbasses that pay for Twitter today.