Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)I

InnerScientist

@ InnerScientist @lemmy.world

Posts
1
Comments
340
Joined
3 yr. ago

  • SearXNG doesn't load the settings ...

    Jump

  • Head of the Signal app threatens to withdraw from Europe

    Jump

  • Nah i don't. I can hope though and the backdoor is a threat not just for consumers but also companies.

  • Head of the Signal app threatens to withdraw from Europe

    Jump

  • I hope more follow, would be funny if "all chat apps have to include a back door" leads to "there are no official chat apps"

  • rootless backup of rootless podman volumes?

    Jump

  • It is expected, the users inside the container are "real" users. They just get offset inside the container and some mapping is applied:

    Root inside the container is mapped outside to the user running the container, everything that has the owner "root" inside the container can be read from outside the container as your user.

    Everything that is saved as non-root inside the container gets mapped to the first subuid in /etc/subuids for your user + the uid inside the container.

    You can change this mapping such that, for example, user 1000 inside the container gets mapped to your user outside the container.

    An example:

    You have a postgres database inside a container with a volume for the database files. The postgres process inside the container doesn't run as root but instead runs as uid 100 as such it also saves its files with that user.If you look at the volume outside the container you will get a permission denied error because it is owned by user 100100 (subuids starts at 100000 and usid inside container is 100).

    To fix: Either run your inner processes as root, this can often be done using environment variables and has almost no security impact or add --userns keep-id:uid=100,gid=100 to the cmdline to make uid 100 inside the container map to your user instead of root (this creates a new image automatically and takes a while on the first run)

  • 2025 Self-Host User Survey: Open for Submissions

    Jump

  • I though that was the point of surveys?

  • Deleted

    Permanently Deleted

    Jump

  • xkcd #3148: 100% All Achievements

    Jump

  • Bro did not get a degree, he got a whole rotation.

  • Google's shocking developer decree struggles to justify the urgent threat to F-Droid

    Jump

  • Theoretically, google could keep that workaround in the code, yes.

    Practically it will be gone in 3...2...1....

  • Self-Host Weekly (26 September 2025)

    Jump

  • Maybe

  • Never!

    Jump

  • They start at 50€/Month but get cheaper over time!

  • Public toilets in China demand ad views for loo roll

    Jump

  • Wouldn't people use tissues and cause pipe blockage in the long run?

  • Steady

    Jump

  • You could even say they have the stediest vitals of them all.

  • Open-WebUI v0.6.29 release

    Jump

  • I don't like Source-available software, especially when they've changed from a more open license to this.

  • Steam Will End Windows 32-bit OS Support Next Year - Hopefully Linux Follows

    Jump

  • side eyes Debian

  • Open-WebUI v0.6.29 release

    Jump

  • Get ready to see ads on your… Samsung refrigerator

    Jump

  • it was of course a horrible laggy mess.

    So the freezer froze?

  • If I use Caddy for reverse-proxying into another local machine... is my local connection not HTTPS?

    Jump

  • There are multiple reasons but the most important one is: You didn't enable it.

    Caddy fully supports https to the reverse proxy targets, though you'd have to get those targets trusted certificates otherwise caddy wouldn't connect.

    The default protocol for backends is http, most of the time this isn't a problem because:

    • The web server runs on the local machine
    • The web server runs in containers/vms on the local machine
      • or is running in a VM and has a direct virtual connection with the caddy vm
    • The connection to the Backend is encrypted with a VPN
    • Caddy and the web server are directly connected or connected through an otherwise isolated network

    Because https requires certificates that are somewhat difficult to set up for internal servers (and were even harder to get before) the default mostly is just to encrypt on another layer of the stack. Afaik at least.

  • hold up!

    Jump

  • Like a headache but with pictures.

  • 2026 Nintendo

    Jump

  • Don't you know? I invented those laws!