bionade24

The hardest bot level on CS:GO already is more challenging than low- or mid-level players. To be fair, the level below the hardest is way easier. All non-wingman standard maps don't allow sniping over much of the map. Are you talking about a different game?

Claiming the US is too dumb to trigger those bombs with a digitally encoded signal and has to use an analog one which can be triggered accidentally is straightup ridiculous. Additionally, he states that Stoltenberg is the leader of the NATO, which is wrong, same as that he's a strong Anticommunist and was hating Russia already as prime minister. He actually solved the disputes Norway and Russia had and is member of Norway's socialist party.

This is wrong. Yes, they didn't install the turbine even after it was delivered, but for the most time, there was still heavily throttled throughput. Only a week or so before the explosions Putin shut the pipeline entirely.

Jamal pipeline was closed by Poland early on in the war.

Transgaz is probably more secured on the landside and blowing it up would also limit Ukraine's ability to get gas from western europe. There already were times before the invasion where Gas was pumped towards Ukraine.

The Black sea isn't a safe space to operate in, obviously.

The FSF says they only care about the GNU project license violations. https://sfconservancy.org/ has an actual record of fighting against license violations.

Y combinator website hugged to death by hacker news. Lmao.

This is different, because we don't have lasting evidence (yet). If circumvent a B-Ray's copy protection some person knowing I ripped them could still report me years after.

> What happened?

Isn't that obvious? Circumventing the copy protection of your own property is a crime.

On 2nd march I did 105 searches and Kagi tells me it costed $1.31. I'm currently paying more than I search. Still, with the new model, I'd pay more. Guess I'll cancel my subscription, too.

The lenses are still garbage too, where "wiki.*" doesn't match "wiki.domain.tld".

If they support python packages exposing the C ABI and expose a C ABI for embedding, I can't see why not.

Because you use a 1st party screen. It's like saying "Linux doesn't have any problems, look at my Pixel phone". Try multiple 3rd-party ones that aren't recommended by Apple and you'll see where the problem lies.

Linux Laptops with no S3 support use S2, not S0 as on Windows. Still buggy as hell. My XPS sometimes loses 70% in 4 hours standby and then just ~5% in 2 days of standby. Most of the time the battery drain is insane. At least the overheating in bag issue never occured to me.

> Comparing Python to Java 8 and saying it’s more readable isn’t showing much.

It shows an obvious reason why a lot of beginners choose python, even when learn Java basics in university first.

The Jolla phone got 7 years of updates before being sorted out. You can buy plenty of "real Linux" phones just now and also LineageOS preinstalled phones which will probably be supported for a very long time.

https://blog.jolla.com/jolla7/

> FP2 is the second device on the "promoted" devices page. That feels like a recommendation?

The FP2 is a very old device lacking some features and probably got recommendation back then because other devices were worse. https://devices.ubuntu-touch.io/device/fp2 Otherwise I'd also could have recommended the Nexus5.

On FOSDEM 2023 Ubports developers didn't show off this old phone, either.

There are plenty devices that work well with UT and are available in the US, e.g Google Pixel 3a/3a XL. Mentioned devices still have an Android Kernel and many limitations. Waydroid on the Volla phone isn't stable, Ubports itself mediocre compared to SailfishOS and suffers from competing for developer time over other Linux on Mobile OSses.

You're overestimating the Volla phone and Fairphone, 1st one still doesn't support VoLTE which I heard is essential in the US, 2nd thing isn't even recommended by UT.[1]

Either go with an Xperia + SailfishOS [2] if you want more than a toy or Pinephone + PmOs [3] if you love to tinker on your daily driver. Both have VoLTE support.

1. https://devices.ubuntu-touch.io/

2. https://shop.jolla.com/

3. https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-...

Apple has giving up on having consistently non-blurry fractional scaling, pushing apple users to buy monitors "recommended by Apple", even if they are from other vendors.

On Windows not all Apps do scale on a HiDPI display. You then have to fiddle in the program's launch options and hope it's not too blurry when scaled.

Wayland does only have blurriness with certain Xwayland embeddings.

It's not a solved problem.

The docker way is a way of using coontainers as a form of contained application building & distribution, which builds itself (optionally on top of layers from docker hub) from a Dockerfile and is configured by a docker-compose file, minimizing the need for external configuration tools that may have problems to keep up with new features. The other feature are the layered builds, which you can mix from multiple bases.

Docker does not compete with LXD which just runs containers like VMs, but with distrobuilder + LXD + including the init.yml in the deploy process.

It certainly was the handling and the strategy how they'd introduce it. First, they obviously should haven't repurposed an existing badge. Im my opinion, setting a lower price in the 1st three months and openly communicating that the price will increase a bit seems like a choice to get quick adoption. 8$/month is too high when people can't experience the value of it yet.

If such an obvious thing happens to a company because they're too smart to read documentation, they would have run into big problems with LXD or sd-machined, too.

You can prevent docker from doing that by editing its config, but you have to read the documentation to know that. As you have to, to actually know what a certain command does, too.

This is not about being unnormal, this is a design decision. Just because people use docker in the "tradional admin way", too doesn't mean it's a wrong decision to do this. Wishful thinking about what a command of a software does without looking it up is generally dangerous. There are abstractions to help people that don't want to bother, e.g. portainer.

There is a option to hardcode DNS and also an option to don't abstract networking and use host mode. Fiddling with your container's resolv.conf is necessary for docker networks between containers.

The 1st thing only happens when users explicitly misconfigure docker, the other one is a real security problem when docker runs in root mode.

If you mean people that install Docker as an "app" on their NAS, they most likely use portainer and don't run into this issue. There are ways for people that don't want to learn the configuration of a project.

Docker is certainly not marketed that way & even the majority of tutorials / if not all on Digital ocean or similar sites don't misguide you into doing this. It is clearly not marketed as "usable without reading docs" and even though people using it as a tool to deploy prebuilt software without learning its configuration, this doesn't apply to the docker commands itself.

If https://www.portainer.io/ would do this implicitly, your argument would be more valid. But for the docker command-line it's a bit too far-fetched.

While docker's port exposure should be more explicit, he should also mention that he used docker without reading the parts of the doc he neeeded to, blindly trusting some dangerous half-knowledge from a forum or other persons.

If he'd bind the host port to localhost or put caddy in a container in the same vlan, it wouldn't have happened. From the blogpost I'm not even sure if he's aware of the binding option.

If you argue that a software shouldn't behave this way after being configured so explicitly, Archlinux not preconfiguring iptables to limit exposure like Debian or Ubuntu is worse, because it happens implicitly.

That big release upgrades provide more hassle than benifits was also observed by Google, hence they switched to rolling release. The reason Debian breaks more at release changes though is probably more due to them patching and modifying software, which they have sometimes have to change/drop with a new SW release. Or you have a hard time deploying a newer SW version on top of the old binaries. Arch follows upstream very close, which maybe increases the times things could/have to be reconfigured, but it still mostly means running vimdiff against config.conf and config.conf.pac{new,save}. Sure Debian is more reliable if you want do want to really change deployed systems, but if your company strategy is to keep up with upstream, Arch may work better than it's reputation.

And if you'd need stability once, you could just set Archive on a specific day as package mirror on your cache server.

> going backwards ever since the British were forced out.

It was already going badly for years before UK left. Galileo was scheduled to be finished in 2021, shortly after Brexit and around the same time UK parted from the project.

Since Julia is Lisp-inspired and part of Jupyter since the beginning, I do think it's intentional.