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/)BO
Posts
10
Comments
3,349
Joined
2 yr. ago

  • Windows 11 has the option to protect parts of your filesystem. You may want to enable that.

    Why? Because otherwise, pretty much any app with the exception of those locked in a web browser can read anything in userspace on your pc. Which is basically everything unless you've taken extra steps.

    That's been the norm for quite a while, and unlike android, microsoft is hesitant to ditch the old thing and add in a prompt "app x is asking for file permission (yes/no)" because they want old software to work with new things.

    On for linux, you'll have to make an extra user, install acl support and pray it doesn't accidentally get written incorrectly by some random app. That is, if you get something like hexos for example. You can roll your own as well.

    On mac, don't bother. Apple has been caught routinely lying about their security and just straight up not fixing major security flaws. Dump your stuff on an external drive and unplug it when you're done. That goes for their desktops and phones.

    edit: inb4 "whats on your iphone stays on your iphone"

  • Part of this is also the demand. Especially in places like the us, a lot of food is wasted, or nearly spoiled before it gets to the customer, or just straight up processed into heckin' fuel and plastic.

    That's not to say that it's a bit odd that subsidies from the cold war are still in effect today, and that those subsidies are being used to lobby for more subsidies :/

    It does make my 3d printer filament cheap tho, thank you American taxpayers!

  • I might just start bundling my apps inside an environment setup with nix inside docker. A lot of them are similar to identical, So those docker images actually share a lot of layers under the hood.

    My apps after compiling and packaging are usually around 50mb. That's 48mb of debian, which is entirely shared between all the images that I build. So the eventual size of my deployed applications isn't nearly as big as they seem from the size of the tarball being sent around. So for 10 apps, that's not 500mb, that's 68mb.

    If anything, the docker hub and registry are a bit of a mess.

  • you can trust the nix repositories aren't going to change

    That, I do not. And storing the source and such for every dependency would be bigger than, and result in essentially the same thing as an image.

    I think you're trying to achieve something different than what docker is for. Docker is like installing onto an empty computer then shipping the entire machine to the end user. You pretty much guarantee thing will work. (yes this is oversimplified)

  • The issue is, nix builds are only guaranteed to be reproducible if the dependencies don't change. Which they shouldn't, but you can't trust the internet to be consistent. Things won't be there to be fetched forever.

    Images do. And you can turn one into a container in seconds. I suppose it's a matter of preference. I like one a package to be independent