Folks, the docker runtime is open source, and not even the only one of its kind. They won’t charge for that. If they tried to make it closed source, everyone would just laugh and switch to one of several completely free alternatives. They charge for hosting images, build time on their build servers, and various “premium” developer tools you don’t need. In fact, you need none of this, you can do all of it yourself on whatever hardware you deem to be good enough. There are also many other hosted alternatives out there.

Docker thinks they have a monopoly, for some reason. If you use the technology, you are probably already aware that they don’t.

there’s a way to tie it back to circles

Not necessarily circles, but conic sections. When you take a series of a fixed exponent over a variable x, and graph it, that graph is a parabola.

A parabola is a slice through a cone. Tada, pi appears.

You wouldn’t, of course. Hearing, the way we hear, in such an environment would be useless. We wouldn’t have evolved that. This is like saying “ultraviolet radiation from the sun would be everywhere, all the time, can you imagine?” It is everywhere all the time, but as such it isn’t a useful sense to possess, so we don’t.

This also makes some very weird assumptions about what the sound would be like. If space were a medium sound could travel through then it would–like all mediums capable of carrying a sound wave–alter the wave in many ways. Intensity, frequency, etc. But since we don’t know what kind of medium that would be, and since the comment doesn’t posit any particular medium, we don’t know what the sound would sound like or even how loud it would be.

It seems like it would be super easy for them to close this loophole. If you use the model that free tier listeners (real ones) will listen to about the same distribution of songs as the paying listeners, then just stop counting all free tier listeners and multiply the amount paid out for the pay-tier listeners by an appropriate factor to make payouts the same as before.

This is what I came here to say. The clarification on the post is not about humans eating plant food, it’s about idiot fucking pets eating plant food. They eat grass, why wouldn’t they chow down on something that smells like blood.

I dare Elon to sue World Bank.

I think those are all herbivores so I’d say he’s eating well, actually.

Right? Like damn, I know that was a good cover but have we already forgotten it was a NiN song?

Can you tell a guy first, I could have shorted

Eh, they understand “number go down”

Accurate.

No matter what question you ask them, they have an answer. Even when you point out their answer was wrong, they just have a different answer. There’s no concept of not knowing the answer, because they don’t know anything in the first place.

They don’t care. At the moment AI is cheap for them (because some other investor is paying for it). As long as they believe AI reduces their operating costs*, and as long as they’re convinced every other company will follow suit, it doesn’t matter if consumers like it less. Modern history is a long string of companies making things worse and selling them to us anyway because there’s no alternatives. Because every competitor is doing it, too, except the ones that are prohibitively expensive.

[*] Lol, it doesn’t do that either

Podman is not yet ready for mainstream, in my experience

My experience varies wildly from yours, so please don’t take this bit as gospel.

Have yet to find a container that doesn’t work perfectly well in podman. The options may not be the same. Most issues I’ve found with running containers boil down to things that would be equally a problem in docker. A sample:

• “rootless” containers are hard to configure. It can almost always be fixed with “–privileged” or some combination of permission flags. This would be equally true for docker; the only meaningful difference is podman tries to push everything into rootless. You don’t have to.
• network filesystems cause headaches, especially smbfs + sqlite app. I’ve had to use NFS or ext4 inside a network-mounted image for some apps. This problem is identical for docker.
• container networking–for specific cases–needs to managed carefully. These cases are identical for docker.

And that’s it. I generally run things once from the podman command line, then use podlet to create a quadlet out of that configuration, something you can’t do with docker. If you are having any trouble with running containers under podman, try the --privileged shortcut, see that it works, and then double back if you think you really need rootless.

600 miles? Call me when they make one small enough to fit in a car

heyooooo

ARM looking pretty good too these days

1. Seems like a very reasonable objection to me. I’d guess that most of us Immich users are using it in the first place because it improves the privacy of our photos, and a third party seeing our location data certainly undermines that.
2. I would have complained had I noticed, so you might be the first one to notice. Immich’s userbase isn’t huge right now, it’s definitely possible.
3. Featurewise, I’d like: a) a clearly documented way to disable map data leaving my server; b) a set of well-integrated choices (maybe even just two, as long as one of them is something like openstreetmap); c) the current configurability to be well documented.
4. I’d love it if all such outbound data streams are also documented. Many security and privacy-focused products give you a “quiet” mode of some kind, where you can turn off everything that sends your data somewhere else. It’s a requirement in many enterprise installations.

Imagine any internet company lasting 50 years.