They used to have XULRunner long ago.

The author mentions FoxESSCloud, which led me to https://www.foxesscloud.com/public/i18n/en/OpenApiDocument.h... with this Python example:

    signature = fr'{path}\r\n{token}\r\n{timestamp}'

So if this is indeed the API they're using it's not only literal "\\n" but also "\\r\\n", no "POST", and no body at the end.

> you'd have to spend hours, days, months, even years (I am not kidding) just waiting for approval and agreeing on what you can and cannot do with the house.

Ah you mean like in the wayland-protocols repo? :)

(not disagreeing with your actual point though)

Bitwarden just had a similar bug with keyboard lag in their browser extension: https://github.com/bitwarden/clients/issues/17090

I wish browsers offered some kind of autofill extension API so password managers don't have to inject their own bullshit into every page.

On macOS, they do! It's not clear why 1Password and Bitwarden don't utilize it.

https://developer.apple.com/documentation/authenticationserv...

This seems to be a system API, I meant the WebExtensions API that browsers implement: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...

Isn't that just Steam's Big Picture mode?

It's an entire login session, steam game mode runs BPM via the game scope compositor, no desktop is loaded in the background, etc. The Steam client also enables hardware controls not available in traditional BPM.

You can look up gamescope-session for more info.

Its something that I generally wouldn't expect on traditional mainstream distros.

Distros do have manuals, they just usually come in the form of user-curated wikis these days. ArchWiki is usually my first stop when I run into a Linux issue, even as a fellow Debian user.

Both https://wiki.archlinux.org/title/Bluetooth and https://wiki.debian.org/BluetoothUser mention rfkill and show you how to troubleshoot.

You'd think so, but you also need to set browser.ml.chat.menu to false to remove a context menu item.

Looking at https://searchfox.org/firefox-main/source/browser/components... it is a bit weird, that there isn't a general check for browser.ml.enabled true/false.

Yeah, there should really just be one global setting.

Also note that it's browser.ml.enable (no "d") vs. browser.ml.chat.enabled, to make matters even more infuriating.

I think the option to disable the context menu item is right in said context menu. Best place to put the option honestly, I wish all AI features had a disable button right next to them.

I thought Harper is an LSP, so this sounds more like an integration issue with whatever editor you're using it with.

Vim does have a menu system, and AFAIK it's still enabled by default in GUIs like GVim.