Ullebe1

Please elaborate.

Proton uses XWayland, this is for proper, native Wayland support. It will make its way to Proton eventually.

Not anymore, since as of October Gitea requires a copyright assignment for contributions. More info here.

Depends on which DE in which version it is using, but anything with recent Gnome (Fedora, Ubuntu) will. Not sure if KDE distros generally default to it, and for more niche DEs the answer is probably “no”, unless it was explicitly made for Wayland.

I doubt it’s ever going to be a part of the core protocols, but it doesn’t have to be, you can just use Waypipe.

I did, yes. TBH it is very anti-Matrix right out of the gate, makes a mountain out of a molehill and it even admits that it contains FUD.

There’s a couple of things that are misleading in it (for example the section on bridges) and the critique basically boils down to “if you use the identity servers that are run by Matrix.org with your self-hosted homeserver they can see the info you send to them” and “Google Analytics in Element is bad”.

All in all I didn’t find it very convincing, and very lacking in nuance.

deleted by creator

Do you have a source for the claim that collecting userdata is ultimately what funds Matrix?

Does this support DRM protected streams, for example with Widevine? Whether one likes DRM or not, it is clear that support for it is a hard requirement for any streaming apps to support this.

Can’t Waypipe do this?

It is supported by systemd to use FIDO2 + pin to decrypt luks partitions with many security keys, including Yubikeys. I use it every day on my laptop.

I guess that depends on which power your agenda aligns with. That power is generally a safe choice, compared to services from a power where your agenda is orthogonal.

Seems like a solid bunch of iterative improvements!

I live in a time where I don’t need to edit config files by hand to allow using multiple applications with the same audio output, since I use a sound server. If you’re willing to do it by hand, then by all means continue. Though it does seem that ALSA has had support for automatically setting up dmix since 2005, after PulseAudio was released.

I also don’t know if resampling and the like is automatically handled when using dmix, but perhaps you can tell me that, since it sounds like you have experience with it?

Reading the fucking manual suggests that […]

How about we keep a good fucking tone. Yes, that’s great. However my experience is that programs all want to set those properties without a way to disable it, so in practice it doesn’t really matter.

Yeah, as you mention hardware mixing used to be an option, but AFAIK hardware generally hasn’t supported that for a long time.

Another reason to use Pipewire is to enable sandboxed access to multimedia devices, for use with things like Flatpak or Snap.

For the multiplexing, as I mentioned.

A V4L2 camera can only be opened by a single application at a time, but if that application is Pipewire, then Pipewire can allow multiple applications to make use of it simultaneously. Same thing with ALSA, it’s the reason sound servers exist at all, though I suspect you’re already familiar with that.

I also hear that ALSA has some support for multiple applications per device nowadays, though I understand it is much less pleasant to use than a fully featured sound server.

Because it is convenient for programs to use Pipewire for screensharing, as those programs can then also use the same Pipewire support for all their audio and webcam needs. Also Pipewire is good at multiplexing the various media streams.

Because Pipewire only handles and understands media streams, so it can stream the output of a window or the whole desktop, but only because the Wayland compositor has already composed the windows and other data it gets from the application to a visual and hands the final result to Pipewire.

IIRC the debacle about theming was:

a. Only about programs using libadwaita b. About their opinion that just overriding the global style like in GTK3 was causing too many issues in apps defining their own widgets or CSS to be worth it.

IIRC they were willing to accept a contribution of a more advanced theming system (but building it themselves was not something they wanted to prioritise over other things), but lacking that they’d rather enforce using adwaita in libadwaita.

What about ease of use, simplicity, faster to quickly setup, backwards compatibility,

The syntax of systemd timers is MUCH easier to read for newbies (and everyone else, really) as it uses words instead the placement of the characters on the line to convey meaning. If you can’t remember or don’t know the syntax well you can still understand a systemd timer, but that is much hard for the crontab. Granted, crontab uses fewer characters, but if you only set up either once in a blue moon you’ll need the docs to write either for a long time. And is backwards compatibility really an issue with either one? All major desktop and server distros use systemd, and has for a while. Fedora doesn’t even include a Cron by default anymore.

“crobtab is where everyone will look at when looking for a scheduled task”?

If it was a distro release from the last decade I’d definitely start by checking the systemd timers, rather than the crontab.

If systemd was implemented right, it would create the systemd files and autoconfigure default tasks by reading the crontab, for backwards compatibility.

You can to totally do this, using this systemd generator.