I mean that’s the thing - it does happen, but those people are already being caught

And once they catch one, they catch a bunch of others that were part of the whatsapp/telegram/whatever group.

They don’t need these backdoors to catch them, because the ones caught like this are the stupid ones they will catch regardless.

It sounds like you’re looking for a hard link, like the one between the far right and china/russia. There is none, as far as I am aware.

The fact they aligned their views about NATO and the Ukraine invasion with Russia (the “NATO threatened Russia, so they had no choice” narrative you also mentioned), and their general affection towards the USSR is more what I was getting at. To me, that’s sufficient to be considered pro-russian.

As to why I called them “more dangerous” (not “worse”, I agree that the far rights ideas are considerably worse) - It’s a couple of things. I feel they are more competent in general than the right. They’re also more idealistic and consistent.

Those by themselves are not dangerous traits, but I also question how far that affection towards the USSR and China goes.

While I actually agree with much of their points, I’m just not that sure how much of the USSR/China they’d actually like to replicate. Regardless of that, I believe they would be fairly successful in implementing much of it - hence why I think they are more dangerous.

They oppose NATO membership, and are parroting the Russian talking point that the Ukraine invasion was the west’s fault.

While they might not be explicitly supporting Russia (which would be political suicide tbh), some of their talking points sure do align quite nicely with Russia.

I personally find them more dangerous than alt right at this point in time.

The far left party in belgium is pro russian.

So far right are fascists, far left are tankies. Maybe one is worse than the other, but both are bad enough for that not to matter.

According to the dutch news orgs, he made a “threatening gesture” towards a (female) camera operator, after he asked not to be filmed, repeatedly (there were not supposed to be cameras at that point, so the request was not unjustified). There was no physical contact.

Here’s the source (in dutch)

Should be 99% for everything above a certain threshold. Any money you make above that number is pretty much guaramteed to have come from exploiting others, so they shouldn’t get to keep that.

Hey, it’s me, your friendly neighbourhood corporate shill, telling you to not buy any more nonstick cookware because I love Tefal so much. More for me!

But seriously, I’m not disputing that the chemicals you listed are bad, just that the coating itself doesn’t affect you.

PFAS bad, but only there during production. PTFE fine, and that’s what’s on your pan. PTFE does not get into your blood. Any PTFE you consume comes back out, because it is not PFAS.

TL;DR: use pan until pan bad, then buy pan with no PTFE.

There’s no PTFE in that list.

Yes, the final product comes back out. The final product is PTFE, not PFAS. PTFE is harmless unless degraded or overheated (which is why you shouldn’t do that with non-stick cookware).

To produce PTFE, PFAS are used (or are intermediaries in the process), which is why the production is dangerous, but the product isn’t.

That stuff sticks to (aka reacts with) literally nothing. That’s the point of it. The whole innovation of nonstick cookware was the fact they got it to stick to something. It’s not even dangerous if you ingest it, it doesn’t react with anything so it just comes back out.

What IS dangerous is the by products and intermediate products, as well as the stuff that comes off if you overheat it. (And also, like you said, when they get old)

This whole movement against non-stick is alright, but so many people do it for the wrong reasons. If you have nonstick, just use it and don’t buy nonstick next time. Throwing away perfectly fine cookware like that is like boycotting charmin by flushing down all your remaining rolls in one go and going to the store to buy new toilet paper from another brand.

I can see the case for some of them after you’ve been in a crash (although if the pyro fuse has blown, not much requiring switches will work anymore, regardless of the type of controls), but if you want physical controls for the rear view mirror for safety, you should probably start adjusting that before you start driving.

Same for cabin lights, whatever you’re doing that needs the lights on should probably be done stationary, if you care about safety.

it’s still comically bad compared to various alternatives, even apples-to-apples alternatives like C#.

I’d be interested to hear why. IMO Java has the superior ecosystem, runtime(s!), and community. The best part is that you don’t even HAVE to use java to access all this - you can just use kotlin, groovy, scala,… instead.

In terms of the language itself, while it (still) lacks some more modern language features, it has improved massively in that area as well, and they’re improving at a significant rate still. It also suffers from similar issues as PHP, where it has some old APIs that they don’t want to get rid of (yet?), but overall it’s a solid language.

And the people hating on it somehow never used any version above 8, which is 10 years old and EOL.

The difference being that when you’re 10 billion into a renewables project, you usually have SOME generation already, whereas your nuclear reactor isn’t doing shit until it’s fully completed.

I don’t mind nuclear, but the fact is that the reactors take decades to build, whereas renewables can be deployed far quicker. Going all-in on nuclear, and then twiddling your thumbs for 10-15 years while the reactors are built doesn’t sound like a great idea.

I don’t think programming language is a good metric for security. I assume everything I host has issues, and then try to mitigate from there.

IMHO, a better approach is to vet the project beforehand, looking at whether it is still actively maintained. I usually use things like commits, issues, etc to try and gauge whether a piece of software is actively maintained so that when an issue arises, it can be fixed.

You can mitigate much of the risk by using some basic best practices, like isolating all apps from each other (using docker, for example), using a reverse proxy, tools like fail2ban or a web application firewall, using proper database permissions for each app, etc

What I also do is add another layer by making certain applications accessible only over vpn. That won’t work for some tools, obviously, but also reduces the risk for tools you are only using yourself.

I’ve set up several Kubernetes clusters in a professional setting (and work with it daily), but I still use straight docker for running my own stuff.

Using tools like Rancher it’s pretty much no effort to set it up, but the overhead is just not worth it if you’re not using the orchestration IMO.

I like them as well, they work well and are easy to set up with the built-in integration.

The only drawback I find is the need to use their cloud, and the low polling rate (5min I believe).

Not dealbreakers for me, but some things to be aware of.