LoSnoCo Network

Why am I like this? I see someone trying to remind me not to boost un-CWed politics into their timeline, and I wonder why anyone doesn't want to be overstimulated.

Am I the only potentially #autistic person who receives pleasure from being overstimulated? I love hot pepper foods, the hotter the better. I love all forms of carbonated drinks, and thoroughly enjoy that my rather hyper senses are drenched in a burning sensation as the carbonation goes down. I like combining these two as well, drinking carbonated beverages just after consuming super spicy food. I also find this last step is perhaps the quickest way to eliminate the residual burning.

I also somehow thought that essenced soda water actually had a strong flavor on its own and that the "drove the truck past a fruit orchard" jokes were nonsensical, since surely everyone can taste the almost fruit punch like strength of fruit flavor from the soda water, right?

I wish I could stop immersing myself in social media garbage every time I look at my social media reader apps. I actively click through every content warning prompt, because I don't want to miss anything. When I probably am doing untold psychic damage to myself in the process of reading all this crap.

I really need a media manager to tone down the garbage on my accounts so I can stop seeing this lot, but then I already do a fairly good job by spending multiple days at a time just not paying attention to social media at all. It helped that I switched my fedi usage entirely to client apps, and closed the web tabs I had opened on my desktop, and use a janky ass desktop client for fedi. And for Bluesky, I follow less than 200 people, and my feed doesn't auto refresh, so I barely see anything when I do look at that tab.

Another thing that does psychic damage to me, though, is being exposed to ideas of new electronics I may want. People keep bringing me back to wanting a damn gaming monitor for my desktop, with full P3 color range and high refresh OLED. But I'll never have the money for that. That's a form of stimulation I wish I could get less of, because I'm fairly happy already with what I have now. Stuff like this makes me wish tech would stop advancing incrementally and actually make some leaps and bounds so that the updates would be justifiable purchases.

So I guess I like some forms of hyperstimulation, but could use near zero exposure to other forms of stimulation, due to how they make me feel about life. I feel like I'm living when I'm burining my senses or listening to loud music, but feel like the world sucks when I'm exposed to all the depressing crap I find all too much of. I wish I could strike a balance somewhere, but I find that next to impossible.

Oh well, bed time, maybe I'll feel better again in the morning.

Seeking testers for wlroots-git atomic modesetting tearing: Basically, you need a 6.9.x kernel or newer, and maybe also wlroots-git and labwc-wlroots-018-git, both from the Arch User Repository. You'll also be testing whether or not it functions better or worse with the following Merge Request:

https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/4746

Basically, I've found that the whole atomic modesetting tearing functionality merged into wlroots-git is completely broken, due to how the kernel functions and limits the use of async commits.

I made a change to make it function, but it doesn't necessarily function 100% of what a user who wants tearing would expect. Basically, it sees the commit failures, and re-sends the commit immediately, as a synchronized commit, to allow the property changes that the kernel is blocking on.

This is likely because I have hardware cursors enabled, because the thing that the kernel blocks on every time, is changes of the framebuffer of the hardware cursor planes, which apparently must be synchronized.

My workaround tries again on failure, synchronized. Further commits without any cursor bitmap changes, or just flipping the primary plane, should be asynchronous proper.

I've been told this isn't the correct approach. Perhaps it needs a different one, at the compositor level. Or perhaps a way for the library to notify the compositor that it synchronized a commit because async failed. Whatever everyone can agree on.

Either way, I'm sticking with this hack in my personal use until a proper solution can be reached. I'm looking for someone, anyone, to test these things and make sure they work. Apparently it's not enough to expect the wlroots developers to test the results of the original async commit patch for atomic modesetting, as they would have found it completely broken at the outset.

#wlroots #wine #proton #gametesting #labwc

God fucking dammit, someone is setting off fireworks again. Leave us the fuck alone, assholes.