Are you calling for a ban on human driven cars? They killed more than zero people yesterday! If you aren't, you've accepted a human-driven vehicular homicide rate above zero.

I mean, that sucks, but it's not like things are going to get better once you're outside of the conditions mentioned

That's the plan! But it's still nice to know if these are the find I thought they were even if I don't plan on reselling them any time in the near future.

OK, so I looked though my browser history, and here are some relevant pages I found:

• keepassxc-browser Issue 1267
• keepassxc-browser Issue 1631
• keepassxc-browser Issue 1783
• browserpass-native Issue 93

I don't remember how much I used each one, but eventually I pieced together enough information information to get the Browserpass extension working in the Google Chrome flatpak. But three of those links are KeePassXC, which should be useful for adapting this for your use.

The main file that was having problems was the Browserpass Native Messaging Hosts file in my config directory for the Chrome flatpak, ~/.var/app/com.google.Chrome/config/google-chrome/NativeMessagingHosts/com.github.browserpass.native.json. Originally it was a symlink to a file at /usr/lib/browserpass/hosts/chromium/com.github.browserpass.native.json:

{
    "name": "com.github.browserpass.native",
    "description": "Browserpass native component for the Chromium extension",
    "path": "/usr/bin/browserpass-linux64",
    "type": "stdio",
    "allowed_origins": [
        "chrome-extension://naepdomgkenhinolocfifgehidddafch/"
    ]
}

The call to /usr/bin/browserpass-linux64 did not see to work for me, so I ended up making a copy of the file in the NativeMessagingHosts directory and modified it to point to a script in my home mount:

wile_e8 NativeMessagingHosts $ diff com.github.browserpass.native.json.orig com.github.browserpass.native.json
4c4
<     "path": "/usr/bin/browserpass-linux64",
---
>     "path": "/home/wile_e8/.config/browserpass/browserpass.sh",

I don't remember why I picked to do it inside the ~/.config directory, but it worked so I left it. And here is the script I put at ~/.config/browerpass/browserpass.sh:

#!/bin/sh
cd ~
/usr/bin/flatpak-spawn --host /usr/bin/browserpass-linux64 2>/tmp/error.log

I don't remember how I came up with that script, it must be somewhere in the four links at the top.

Finally, I needed to use Flatseal to allow access to the script. In the Google Chrome settings, under "Filesystem->Other files", I added an entry saying ~/.config/browserpass:ro. Also modified from the default in Flatseal, I have "Filesystem->All user files" enabled, along with "Socket->D-Bus session bus" and "Socket->D-Bus system bus". I don't know how necessary the last three are, but I'm not messing with it now that I have it working.

So, that's what I did to get the Browserpass extension working in the Google Chrome flatpak. You'll have to modify some things to get it working for KeePassXC, or for Firefox. But that general pattern should work.

Keep an eye out, I'll come back to this. It involves posting config file diffs and a script I wrote, it'll be a longer post I don't have the time to write right at this moment.

But yes, the fact that I need to find the time to post all the changes I needed to make to get this to work is part of the problem here.

FWIW I figured out how to get a password manager (Browserpass, not KeePassXC) to communicate with flatpak Chrome if you want some advice on how to get it to work.

But yes, it was way more difficult than it should have been (which is "should work out of the box, just like a regular package"). So if you're just listing some of the shortcomings of flatpak, never mind.

It's kind of amazing it took this long - I don't know why they didn't do it this way from the start.

Wait, are photo passes really happening this time? Google has made a couple of blog posts announcing the feature, but I've been regularly checking for the last several months and haven't seen it. It was a nice feature of the original Google Wallet that was removed in one of the rebrands, I'd really like it to actually be back instead of just "coming soon" (not that soon)

And then a whole bunch of them will turn around and vote for anti-LGBTQ+ Republicans because "They're for the economy" (please ignore how the economy actually performs under Republican control)

Hasn't Android had a thing for a while where it gives update priority to people who manually check for updates? Like, my phone (7a) didn't say an update was available, but then I clicked the "Check for update" button, and now it said Android 14 is available.

So I don't think anyone who really wants the update soon needs to sideload the OTA, just check for an update and you'll probably get it.

Go check out a review of Michigan's opponents this past week, unless you're lacking sufficient intrathoracic dog.

Is there any mirror for this? I don't know if this has been posted to some other site as well, but the web site seems to be overloaded with traffic right now and I can't see the article.

Get your F-35 analogies before they're dated!

Well, I don't know if Buchner is actually going to be better than Milroe. But from what I saw on Saturday, Alabama isn't going to win anything significant with Milroe under center. So maybe it's worth a shot to see if Buchner can perform against live competition.

Come for some fun analysis of most of the Big Ten, stay for existential dread about your fingertips

Am I crazy, or does 8.76M for Texas/Alabama seem low? I was expecting at least 10+M for a hugely hyped, prime time game between two of the biggest fan bases on the sport. Was it because it was on ESPN and not a broadcast network?

• Back in the day, it used to be cheaper to buy season tickets than to buy tickets for every individual game. So a whole lot of if it inertia from being the standard way to go to all/most home games.
• Knowing you have the same seats in the same location near (mostly) the same people for every game it pretty nice.
• You can just relax with the comfort of having tickets in hand before a game instead of regularly having to go through the hassle of finding decently priced tickets before any game you want to attend.

But yeah, the administrative need to maximize revenue in the next quarter and the enshittification of everything means these benefits are hardly worth the cost any more. Which is why we've seen lots of articles the past few years about decreasing attendance in stadiums nationwide. Surely it must be because the fans aren't supporting the teams hard enough any more!

These weekly articles were fairly popular on that old site people used last season, and I figured I'd bring them to the CFB community that actually has people posting now.

Thanks, that's close, and has all the filterable options I was looking for. However, it seems more tilted towards "individual cars that are for sale in your area now", while I was thinking "models that fit our criteria so we can order one for delivery in the future". It's useful for looking at options, but doesn't list things that aren't available here right now.

The United States. And I've been checking for it since it was originally announced at the beginning of June. And.... I guess another announcement means it's not dead. Yet.