Yes, but these internal connections can be done in a variety of ways - for example the most common way to connect laptop displays (which I would definitely classify as internal) is using embedded DisplayPort.

But Wayland isn’t a thing on its own, there’s no “Wayland server” or anything else equivalent to the X server. The compositors like Kwin or GNOME’s Mutter are Wayland implementations fully responsible for handling the display output.

You can blame Wayland for the lack of universally supported global hotkeys or for issues with apps that need to know exactly where on the screen they are - these are issues with the protocol - but not for bugs in one compositor’s implementation of display management.

OK but Wayland is not responsible for arranging monitors

OK, I use GNOME on Wayland on EndeavourOS and have no problems regularly running a script in my phone’s internal storage root directory. Go file a bug report to your distro, or at least provide some details.

I can’t speak for these specific laptops, but unlike x86, ARM generally doesn’t have a way for an OS to discover the available hardware, and most ARM platforms historically didn’t do anything to help. There is a standard for UEFI on ARM where the UEFI is supposed to tell the OS about the hardware, but as far as I know this is only a thing on ARM servers and these laptops might not support it.

Without any way of probing for hardware or getting the information from UEFI, Linux has to somehow be compiled with all the info about the hardware built-in. And the build will be model-specific (there’s a way to pass a file describing the hardware to Linux from the bootloader which enables a single kernel to be used on multiple models and have just a small part of the bootloader be model-specific, but somebody still needs to make that file and the manufacturers clearly don’t intend to do that).

This is about USB

proprietary Google-only format

Keyhole Markup Language

KML became an international standard of the Open Geospatial Consortium in 2008.

(…)

The KML 2.2 specification was submitted to the Open Geospatial Consortium to assure its status as an open standard for all geobrowsers.

They probably fixed all the bugs they considered essential, and the rest is just nice to have fixes that can be moved to the next cycle if necessary (and they still have a week to work on them before release, although they might be careful not to introduce severe bugs now).

The general idea with this approach is that it doesn’t make sense to block a release on a few bugs worked on by only a subset of available developers and having the rest idle - the project can be finished faster by moving the remaining tasks over to the next release and accepting the bugs in the meantime.

Not familiar with the API, and I’m not entirely sure if it’s not just a bug in Eternity (fork of Infinity), but lemmy.one doesn’t have downvotes and I don’t get the option to downvote anywhere.

The comment you replied to is a direct reply to the comment you linked - I don’t think it was intentional, but if it was, then I’d like to say it’s not a very helpful reply as OP already read it.

someone just plain lying about what OS they’re using in order to break fingerprinting.

The idea with avoiding fingerprinting is to look like whatever the biggest group of users looks like, because that’s who you share the fingerprint with. If you use an uncommon value for something, you make fingerprinting easier.

That’s one of the reasons why for example Vivaldi on Linux sets its user agent to match the latest version Chrome on Windows.

You’re supposed to use fingers

That really depends on the technology used. For example, all modern Ethernet standards (which includes both copper and fiber optic) are full duplex, meaning they can provide the full bandwidth in both directions at once. So a gigabit Ethernet link can do a gigabit in one direction AND a gigabit in the other direction at the same time (but not two gigabits in one direction).

It’s easy to dismiss as an ad. I did, too.

Well, Vivaldi’s built-in in adblock apparently agrees with this categorization. The video shows up if I disable it. Lol

Where’s the article?

Salt from the seawater

Sounds like most of that would be handled by the kernel with non-Deck-specific modules - it won’t forget to notify the userspace that a device has disappeared just because it was in sleep mode at the time it was physically disconnected.

The only problems I ever had with sleep on Linux were all inability to wake up some part of the motherboard or the GPU because of crappy firmware, never with connecting/disconnecting external stuff.

Seems more like a featureless slab to me

Fair enough. I misunderstood, my bad.

Then what’s the meaning of this whole part?

On non-corpo linux syslog can be disabled if you want, though I’d prefer to just symlink/mount /var/log to a memory filesystem instead.

Is it just a random tidbit that could be replaced with a blueberry muffin recipe without any change of meaning of the whole comment? Because it sure won’t help OP at all with their Arch-specific question, so it’s either that, or it provides contrast to the “corpo Linux”, which is how I interpreted it.

And here’s the remaining part of your comment I left out, just to make sure people won’t lose the context between two three sentence long comments (for those without any attention span, it comes before the previous quoted part):

If you’re on arch you use redhat’s garbage.