emersion

To show the setting to enable this feature outside of Germany, go to about:config and flip cookiebanners.ui.desktop.enabled. Then a "Cookie Banner Blocker" section should appear in the Firefox settings.

It seems like cookiebanners.service.mode=1 might enable it outside of private browsing.

SourceHut staff here. We don't have any requirement for "real legal" names or anything -- and in fact I find these requirements very harmful in general (glad we finally got rid of them in the kernel). I know multiple people collaborating on SourceHut with a pseudonym and this causes no issue at all. SourceHut does assume a stable email address but that's about it.

That's my own take -- for Drew's see https://drewdevault.com/2023/10/31/On-real-names.html

Related: https://drewdevault.com/2023/07/04/Dont-sign-a-CLA-2.html

By "clipboard request", I meant "request to set the clipboard".

> For firefox running in Wayland, `writeXPrimary()` will only succeed when the firefox window (the main window, not necessarily the tab the code runs in) has the focus. Otherwise the selection will be cleared. At first I assumed that this is something specific to the Wayland protocol, but that turned out to be utterly false; it's just some quirk, bug or "feature" specific to either firefox itself or GTK.

Most Wayland compositors will refuse clipboard requests from unfocused clients.

Additionally, the Wayland protocol carries an event identifier, so that the compositor can tie the clipboard request to a pointer/keyboard/touch event and take a better decision. (This metadata is missing for X11 clients, of course.)

That's not true in general. Many mailing lists accept emails from unsubscribed users, some moderate them (requiring moderator approval for the first post), but I don't know of any which outright rejects such emails.

Related: https://blog.brixit.nl/developers-are-lazy-thus-flatpak/

Printed version here: https://web.archive.org/web/20151229025053/http://ianmurdock...

> Yes, that’s an actual scanned printout of the Debian announcement. I received such an overwhelming number of responses I had to print them out to avoid filling my 500 kilobyte (!) disk quota on the student Sequent Symmetry.

(2015)

seatd isn't just about multi-seat. In fact, seatd doesn't even support multi-seat at the moment. See this post for more details: https://lists.sr.ht/~kennylevinsen/seatd-devel/%3C3561460.kQ...

Updating is fine as long as it's from a auditable repository with full source code history, and built by a third-party like a distro (or the build is reproducible).

To anyone trying to figure out what the missing "Eyetests were a lot easier in the 1920s" image was referring to, here's a link to an archived version:

https://web.archive.org/web/20191128021121/http://dlewis.net...

There is an upstream KMS driver for GUD: https://github.com/notro/gud

It works by connecting the Pi via USB.

FWIW, swayidle only has an optional dependency on logind. It can be built without. In fact, we're even discussing removing the logind-related features from swayidle. (swayidle never required running as root though.)

This used to be true, but not anymore. We have upstream support for FreeBSD in libwayland now. Other BSDs have MRs which are only waiting for CI support.

Wayland itself has nothing to do with systemd, many users are running Wayland without systemd.

My go-to CD ripper is https://github.com/cyanreg/cyanrip

This is partially explained in the blog post.

I'm personally using UnifiedPush HTTP endpoints as-if they were Web Push, and it just works. I handle decryption manually on the receiving end.

Yeah, there is a lot of freedom, it's pretty similar to how an open-source project works. Pierre-Loup indicates what features would be nice to have (in gamescope or other projects), I can pick from that list. Or I can pick my own ideas and work on these. Or I can discuss with the other contractors, come up with an idea and coordinate our work. Sometimes I work on short-term bugfixes, sometimes I work on long-term plumbing efforts.

I'm one of the developers contracted by Valve to work on gamescope, wlroots, Mesa, the kernel, Wayland, etc. Really happy that my contracted work helps not only SteamOS, but very often the whole ecosystem. Examples include radv/amdgpu fixes, tearing page-flips, a re-usable library to make use of KMS planes, and the list goes on.

Wayland does send subpixel info to clients for thus purpose. See wl_output.

Heading: "Open Source Roots"

What it actually means: "As part of this commitment to modernize, we are adding an NGINX Community channel on Slack"

Oh right. It completely makes sense that open source roots involve a proprietary communication platform.

"We want Nix to ne ubiquitus"

And there it is. Every time I hear about Nix, the goal is to convince me to adopt it, as if it was some kind of religion. Every time the Nix folks are being too pushy about it.

Just stop pestering random project maintainers with Nix. If a project maintainer likes Nix, they'll add the Nix files. If they don't have Nix files, that doesn't mean they want to sign up for Nix advertising.

For display chips in GPUs, there is drm_info. For GL/Vulkan, eglinfo/glinfo/vulkaninfo.

Shameless plug: someone is trying to solve these issues: https://sr.ht/~emersion/goguma/

It uses IRCv3 chathistory + a proposed extension for push notifications.

Working on it: https://github.com/ircv3/ircv3-specifications/pull/471

FWIW, IRC still has away messages. And quit/part messages.

FWIW, Go's fmt package does the same: https://pkg.go.dev/fmt

To add on this: Valve works with upstream developers on upstream code, so their work benefits the whole FOSS ecosystem. They are funding a lot of kernel, Mesa, Wayland, Wine and KDE developers.

(Disclaimer: I'm a Valve contractor.)

XWayland as a whole is itself a Wayland client. So as long as any X11 window has focus then any other X11 window can steal the clipboard. But once a Wayland window is focused, X11 windows don't have access anymore.

This post is an introduction to color management, not a complete reference. ICC is definitely being taken into account in the course of the broader Linux work, see the rest of the repo and the draft Wayland protocol.