• 3 Posts
  • 2.23K Comments
Joined 3 years ago
cake
Cake day: June 30th, 2023

help-circle





  • for more context as to why this is not that good of an idea as it may seem - please look at curl project and barrage of false security reports made. and curl is a cli project which just handles many protocols, and does not practically do any processing. firefox and any modern browser is basically a operating system and even a hardware (in forms of wasm allowing you to run arbitrary assembly written in systems programming language).

    The difference is that anthropic did due diligence. They narrowed their scope as a research project to just the JS engine. They then fully vetted 1 issue, had a complete minimum-test-case that would reporoduce the issue, then contacted Mozilla with it.
    Mozilla then said “send over the rest, vetted or not”, who then vetted them all.
    Mozilla’s findings with the bugs found by Claude were fed back to anthropic to hone the model.

    So, it’s completely different that someone yeeting a codebase into an LLM and reporting whatever it spewed out.
    Anthropic required Claude to actually produce an example exploit of it. And it REALLY struggled to do this. But it did get there eventually, for 1 bug. Which they then reported.
    Even then, the exploit was in the JS engine. It wouldn’t have escaped the sandbox to actually be an issue. Classic defence-in-depth

    Shitty use of AI is fucking horrible. It wastes resources, it wastes time, it wastes energy.
    I think this is a responsible use of an LLM in limited scope to produce an actually useful result.









  • And it’s still faster for my linux install to boot.
    LUKS password for disk encryption, then user login to a usable desktop with network connectivity.
    Windows takes ages to get to a login screen (bitlocker is disabled, so no decryption excuse), logging in is a breeze with fingerprint reader (certainly faster than typing in a password), then it sits there for ages looking like it’s ready to be used, but the network stack isn’t ready and it is just unusable until that comes up.

    I’m so happy when I get a day of just working in Linux.
    It just… Works.


  • I’ve had one issue in the past year and a half, dual booting from the same NVMe.
    After fixing the boot partition issues from a liveUSB, the actual solution was disabling fast-boot.
    It’s been solid for a year now.

    But I always shutdown my laptop when I’m not using it. And any windows updates that require restarts, I make sure it fully reboots into windows again.




  • Yeh, I don’t quite understand docker desktop.
    I guess it’s handy for seeing running containers, volumes images etc.
    But I don’t get what it offers over CLI, or a TUI like lazy-docker.

    You might be thinking of something like portainer, which does let you use compose files via its web gui.

    Glad you’ve figured out the docker compose route. I find config files (and scripts) significantly easier to work with than figuring out a bunch of commands to run.


  • Yeh, it doesn’t look like it’s exposing the ports.
    I don’t know docker desktop.
    I just use docker compose files, even for things that don’t need it. I like having a file that describes the service, instead of deciphering run args.

    Some googling,
    https://stackoverflow.com/a/73819697
    Describes how to run a container with more specifics.

    I would strongly suggest you copy the official docker compose file, and run that with “docker compose up -d”.
    That will configure all the components required, then you can still inspect/stop/start/view etc using docker desktop.

    But I also understand the brain fog.
    Maybe you could work through the fog to install Portainer once. After which, you can use that and it’s web GUI to manage all your containers and compose files.
    Setup on Windows/WSL with Docker Desktop (but needs 2 commands: 1 to create the volume, 1 to run the container) https://docs.portainer.io/start/install-ce/server/docker/wsl

    Portainer might be more what you are looking for, rather than docker desktop (although docker desktop does make docker installation a lot easier)


  • Reading https://github.com/wallabag/docker I don’t see any mention of doc75/wallabag as an official image. Any reason you went with a 3rd party image?

    Also, might be that you aren’t exposing the port? Wallabag looks like it runs on port 80. Might be that port 80 is restricted (or in use), so docker desktop can’t bind it. Maybe forward a random port to it.

    You can also inspect the container. It will show env vars, networking binds, volume binds etc.
    Make sure they align with what’s in the official docker-compose. Once you get that working, you can start tweaking towards your requirement.