• 28 Posts
  • 45 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle
  • Well, I made it.

    Notes:

    • I did add a whole small can of tomato paste (6 oz), and given how red it is, I probably would have been fine with a couple scoops.
    • I forgot to add the beef and stir it around in the sauce to get it coated before adding the broth - I just went right to the broth while I had the measuring cup in my hand from the wine. I didn’t notice this until I went back to see if your broth was as red as mine.
    • I cooked the potatoes for 45 minutes, and they weren’t fully cooked through yet. I was thinking I need to cook them longer next time, my wife said it would be a better idea to just cut them smaller next time.

    So, pretty good, but not great given a few things I did wrong. At least I know what to fix the next time I make this.


  • OK, so I was adding ingredients to my grocery list to try and make this this weekend, and:

    add the tomato paste. Cook and stir this for 3-5 minutes. then

    You have tomato paste mentioned here. I clearly see you add it in the GIF. It is not in the ingredient list. How much should I add?








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

    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.












  • 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.











    • 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!