Read more about our transformational work happening inside of BITS - linkedin.com/pulse/bits-unders…

Wayland nits:

- external monitor doesn't change its scaling to native when I close my laptop lid. This was working for me correctly on X11 unless I mirrored the screen feature even once, then I have to set it manually again

- If I close my laptop lid too quickly after logging in it just goes back to sleep again, and then this has angered the gods and things usually freeze.

This is possible to trigger on X11 too -- I think it's because whatever power management things KDE has just isn't running yet. The only sane way to fix this is to make the power management stuff run when the DM is running before login, but it would mean at that point it must know you can't choose a different desktop environment; the login screen needs to be *directly* integrated with the desktop, especially so other common background services universal to every user that may login are already running too. Like make a real OS, not a bunch of disparate projects glued together.

- kwin_wayland process seems to spike a lot higher in cpu than the x11 counterpart but I didn't do a clean comparison to verify

"Soon AI agents will be writing better, cleaner code than any mere human can, just like compilers can write better assembly."
— Nick Hodges, in Infoworld, 2025-11-26
infoworld.com/article/4096265/…

I look forward to a contined consulting revenue xtream, fixing the disasters that result from managers believing this bulls***.

He likens this to compileds writing better assembly code than humans. That works because the semantic level of high level languages like C, C++, etc. are not that far removed
1/

This entry was edited (3 weeks ago)

reshared this

Edit: I should mention that I'm trying to integrate this word/phrase into a cyberpunk book title...

Fediverse hive mind: I'm looking for a word or phrase that means a windfall (receiving something unexpectedly), except to such a great extent that it's overwhelming and not actually that great (example: a previously unknown relative passes away and leaves you one million sheep but no land to house them). Ideally this phrase would be in English, but at this point I'm desperate and any language may be helpful.

Please boost for a bigger hive! ;)

#writing #WritingCommunity

This entry was edited (1 month ago)

Ok, I need to vent for a sec. Ableton released Live12.3 yesterday, and I was really excited to try out the new Splice integration, the one feature I was looking forward to using the most. Come to find out that on Windows, Splice it's pretty accessible with a screen reader. You're able to search for samples and easily add them into your project. On Mac, however, at least on Sequoia, VoiceOver doesn't see the Splice web UI at all.

If I try and use VOCR to click on random things with the mouse, VO says there is a web content Area somewhere on the screen, but I can't tab to it, if I use the VoiceOver cursor it completely skips over it, I even tried turning VO off and on to see if maybe it would refresh or something, but nothing. I'm completely locked out.

I'm hoping upgrading the OS will fix this, I really don't want to move to Windows just to use Splice in Live, but I have no idea if this is an issue that Apple has to fix on their own or if Ableton can do anything about it. Honestly some days I really hate being totally blind, and yesterday was definitely one of those times.

in reply to Zach Bennoui

Ok so quick update on this. Ableton are definitely aware of the issue, an employee responded to me on Discord saying it's something to do with how VoiceOver interacts with the UI, and it's a tough thing for them to fix. They said hopefully they'll be able to figure it out, but if you can find some way to get focused into the splice window, it should be accessible with VoiceOver.

The importance of appropriately putting emphasis on a subject avoids misplacing blame towards groups that have no control over a given situation. For example:

"Wayland has a lot of compatibility issues with XYZ"

This makes Wayland the subject of the sentence, thereby putting emphasis on it, which implies that Wayland is the culprit, and thus misplaces the blame on Wayland.

Wayland has existed for over a decade. Several entities with a large amount of customers have actively sabotaged Wayland development by the lack of involvement, including and especially NVIDIA. Sure, these companies are now involved with the ecosystem, but for the longest time they have refused to properly support Wayland, worked against Wayland by implementing their own "solutions", or by doing absolutely nothing, which slowed down progress for so many years.

So the proper way to phrase this is "XYZ has a lot of compatibility issues with Wayland". This makes XYZ the subject and thus puts emphasis on that, rather than Wayland.

This is very similar to putting emphasis on Linux when making a statement about hardware compatibility: "Linux doesn't work well with XYZ" — no, likely XYZ doesn't work well with Linux, not the other way around. Most of the time, the hardware is the one at fault for not properly supporting the Linux drivers.

This entry was edited (3 weeks ago)
in reply to TheEvilSkeleton 🇮🇳 🏳️‍⚧️

I'd write a reply to this say it's a hard no, and that Wayland developers have created an insufficient platform for some applications, but since I don't want to get dragged into an interminable, soul-draining discussion, I will only say:

Nope, it's not the application developer's fault that apps running on wayland have problems.

It's been fifteen years and moving an application from xcb to wayland is still hell, parts are impossible and there no improvements for the user.

in reply to TheEvilSkeleton 🇮🇳 🏳️‍⚧️

the last part doesn't make any sense. Drivers are written to drive hardware. It's not the fault of the hardware if the driver doesn't work or doesn't exist.

I know what you mean by Wayland & NVIDIA, but to be clear, they did support Wayland, it was just that nobody liked their solution (EGLStreams), so nobody supported it, and instead demanded libgbm, so at some point NVIDIA made a thingy to support libgbm. Afaik there was also the thingy between the Linux dmabuf Wayland protocol and NVIDIA's EGLStreams, where once again nobody wanted to use EGLStreams. Dmabuf & GBM are just thin wrappers around the kernel API, EGLStreams is more high-level.

Now, the fact that the NVIDIA prop driver had neverending bugs is nothing new, but w.r.t. the API itself, I am yet to see anything against it that isn't just "NVIDIA bad" (yes) or "NVIDIA prop drivers buggy" (yes).

NVIDIA is handrolling their own graphics stack instead of using the Linux one, so stuff like this is expected. From a high-level view, the EGLStreams API looked okay.

And ofc, this is ignoring the Linux NVIDIA drivers (nouveau et al), that just work fine cuz they use the Linux graphics stack.

Also, Wayland is a display protocol, so the point isn't even about NVIDIA supporting Wayland or the other way around, that sentence makes no sense. It's about NVIDIA exposing the needed APIs for implementing a display server, and for sharing buffers in a reasonable way. NVIDIA can on top of that do work on Wayland (and they did), but I don't see why they would have to if they properly support what's needed in their graphics stack.

So the full story was that Wayland spec, app & compositor devs mostly refused to support NVIDIA because NVIDIA handrolled their own API for their own graphics stack but never made it work fully correctly due to implementation bugs. Trying to support NVIDIA back then is how you got things like --my-next-gpu-wont-be-nvidia. For X.org Server, they just wrote their own X.org Server module and made it work well enough over the years. EGLStreams was an attempt at exposing an API for compositors to do the same thing.

I am holding myself back from ranting about the state of the Wayland Linux GPU stuff, libgbm, etc, but uh... I do often wonder if I can play with EGLStreams at some point. That at least had an API design, rather than just being a thin wrapper around low-level stuff without any docs besides read the source code deep in the Mesa tree

I really hate getting Lyft/Uber drivers who don't speak English or use a translator. It's a problem. It happens at least once a week around here. I don't have a problem what language you speak or where you come from, I have a problem if you can't speak English and won't use the free and readily available tools at your disposal that will make it so you can effectively do your job. That is not my job, as I am not getting paid to transport someone and insure I do it effectively. Luckily I convinced Lyft to give me a $15 credit and informed them it was a safety issue that one of these drivers dropped me off at a weird location going into work this morning. It's great for me that I have the O&M skills to find my way around, I'm used to walking in Phoenix and keeping my guard up, and in a pinch I use my phone because I have the skills to do that. I know lots of people who are blind and don't. And I'm sorry but in this day and age, with all this tech floating around, there's no excuse and I have no sympathy for people who choose to do a job that requires communicating with people, don't know the language, and can't/won't employ a translator. You're getting paid my money to make sure I get somewhere, and if you can't understand "gate on x street", then maybe you should rethink. Funny how these services are so concerned about dog allergies for example, but apparently don't think about a crucial aspect of insuring their customers get picked up or dropped off safely? Hmm.

TIL: The Raspberry Pi kernel is patched so you can parse a partition number to a restart handler in the bcm2835 watchdog driver, which splits it across various (non-continuous) bits in a watchdog register, which the firmware then uses to decide where to boot from next (or not at all). Meanwhile tryboot seems to be doing some mailbox stuff instead… ​:neocat_googly_shocked:github.com/raspberrypi/linux/c…github.com/raspberrypi/linux/c…

Sandwiches tonight which is okay with me, considering how much food I'm going to eat tomorrow. As nervous as I am, I'm actually really excited. I've decided to cook the chicken myself instead of cheating. I'll probably throw it in the instant pot for a bit then shred it. This is better anyway because it means I can add my own seasonings. It's going to be both beef and chicken enchiladas, red beans and rice, the fixins' for tacos and a chocolate cake. This is going to be amazing.

📻 Avec des copains de Strasbourg, on aimerait s'initier aux savoirs et techniques pour devenir radioamateurs, et je suis à la recherche de guides de qualité accessibles aux débutants pour bien démarrer !

C'est bientôt mon anniversaire et je sais pas trop vers quel matos me diriger... Il y a des gens ici qui s'y connaissent et qui pourraient me conseiller ?

#Radioamateur

This entry was edited (1 month ago)

RE: floss.social/@kde/115617248408…

are we sure we're ready for this? i love wayland but i'm also not reliant on accessibility software. and i've heard time and time again from people who are that wayland is still far from being accessible

RE: hachyderm.io/@conjured_ink/115…

I’m gonna boost this again cause we really haven’t gotten very many applications but we could really really use the engineering help, esp if you’re an experienced #Rust #RustLang engineer.

Open source drive bys are great but having a set of folks who are willing and able to commit to just 5 hours a week would make a world of difference for the project. Please take a look and lmk if you have any questions!

Great article by Dr. Andrew Jackson @ UCD refuting the Stripe co-founder's recent op-ed in the Irish Times.

On Environmental Democracy and the Collisons’ “Abundance-Verse” elajucd.com/2025/11/21/on-envi…

Silly #Poll: where are you along the #neckbeard pipeline?

(Note: the neckbeard is metaphorical. No actual facial hair required)

Also, please remember #DanesLaw: no matter how carefully someone attempts to construct a poll, the very first comment will usually expose a glaring oversight. That's just how it goes.

  • Windows is fine (5%, 28 votes)
  • MacOS, 'cuz life's too short for all that mess. (14%, 76 votes)
  • Linux, because it's faster, and my games run great (19%, 105 votes)
  • I'm a Linux command line jockey!! (35%, 187 votes)
  • FreeBSD all the way! LONG LIVE UNIX (9%, 51 votes)
  • OpenBSD! Security go BRRR! (6%, 36 votes)
  • Of *course* it runs NetBSD! (2%, 11 votes)
  • Haiku!! It's so beautiful!! (3%, 19 votes)
  • Ha, I'm still running Workbench/Aros!! (0%, 4 votes)
  • I wrote my own OS. I'm on a mission from G-d. (2%, 12 votes)
529 voters. Poll end: 1 month ago