My friend, a podman container file is a simple tiny ini text file. Behind the scenes it gets converted to a systemd service unit file, which is also an ini text file. The service file has a simple ExecStart command that just calls podman run. Meanwhile podman will just set up an environment and run the container with runc or crun. The whole thing is basically one step above a shell script. I could buildroot a system with this entire stack and it would fit on my wifi router.
It's neither. A systemd generator just transforms a simple 15 line container text file to a simple 20 line service text file, and then the container lifecycle and dependencies are managed by systemd like any other system or user service.
It's not tightly coupled to anything. It just ships with a systemd generator allowing you to manage containers, pods or networks with systemd if you want. And lots of people are noticing the benefits of that arrangement.
But James Kariuki, the UK chargé d’affaires to the UN, said Britain continues to disagree with fundamental propositions of the text and was “firmly of the view that we must not create a hierarchy of historical atrocities”.
This does indeed invite a whole flurry of what-about comments and resolutions: "Are the Slavs getting a resolution? What about X, what about Y?"
I use alacritty with a small script that calls tdrop to make it a drop-down terminal, and sets a few other window properties. For tabs I use tmux as it's amazing and works everywhere.
It all works perfectly on X, but tdrop is pretty glitchy on Wayland with multiple monitors. Since I use the drop-down terminal a lot, that this was enough of a trigger to move from gnome to kde where I can still use X.
What you're missing is that they want the people to fight them so they have an excuse to attack them more. And these excuses work retroactively too. They bomb, wait for a retaliation, then they say "see, we were right to bomb them," followed by an even bigger attack. Repeat till there's nothing left to bomb.
Iirc they only want the difference in tax if you're in a country where you're paying less. I'm guessing in most (all?) EU countries you'd pay more, so you wouldn't need to pay anything. It seems quite sensible.
Ok, I looked into this again, and I think I know what the issue is. It has little to do with summit. Seems like my instance (and possibly some others) convert images to avif while creating proxy images, and I guess android 11 doesn't support decoding avif properly, or at least my install doesn't.
I actually tested this by trying different accounts before reporting here, but two things happened that made me reach the wrong conclusion. First, when looking at a different instance which doesn't use avif, summit will successfully load the images for posts from the cache, so the avif images still got loaded and showed me errors. Clicking retry on the errors actually loads the images normally.And then secondly, when testing in signed out mode, summit seems to default to using my lemmy.zip instance which again shows the avif images.
There used to be x86 Android phones. But they kept that port going even after the phones went away because it was good for development on x86 machines. You could just run a VM instead of having to emulate an arm ISA.
𝕷𝖊𝖍𝖗𝖊𝖗 𝖘𝖎𝖓𝖉 𝖍𝖎𝖓𝖌𝖊𝖇𝖚𝖓𝖌𝖘𝖛𝖔𝖑𝖑