Welp, the conflict of interest was clear. I’ll have to watch this drama later tho

Not the best example in the us, perhaps. But you get the idea

Yes and no. They’re still humans. They should be held accountable, but they should also have the privacy to live their lives.

It’s not a simple black and white situation. There’s more nuance here

I suppose, either way it makes harassment and more misbehaviour more easily available

It would make it easier for these people to be harassed, or worse. Privacy is important

I think it’s more akin to a “get guns ez pz” article. Even if most people can get them, a lot of people don’t because it’s a hassle. But to be fair, if it’s public information then heck, it was only a matter of time until there was a website making it ez pz.

That’s not this article’s fault. And some important context I managed to miss at first :/

The concern was the lack of knowledge that this was public. I noticed it’s in the article, I may have read over it

A. A gun is a tool as well, doesn’t mean you should make them public available

B. That makes a lot of sense. I’m not from around there, sorry for the misunderstanding

Is this not doxxing? Posted by a mod no less

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

It also adds more fodder for insurance companies to try to not do their job

Aw, meh. From what I saw it’s more like a jail, there’s no imaging the containers

Ah, then they don’t have to worry

Why does github have access to your bank account?

No I threw it in a docker container

Hold up, nix added containerization? How did I miss that? I will have another look now!

Also, you’re right. For small quick scripts docker can be a hassle. Nowadays though I add building a docker image as part of my project’s build/compilation process. The main reason I do this is so that I can work with whatever machine I happen to be on, then just copy paste the app to whatever machine I want it on. No extra config or even a look at the environment required. Just install docker and forget about the rest

update: installing docker on nixos (on a vm) with a nix package failed, not sure why. Perhaps some dependencies were no longer available?

update: nix is is available as a docker image. I’m running it now, we shall see how it goes

Perhaps it’s improved over the last year, I can give it a shot. But yes, for my own packaged applications without shared dependencies, docker is handy. And that’s exclusively what I run

Ye that’s handy, until some script inside a library or something doesn’t