yonixwm

It really doesn’t seem so when we experience Russia doing the opposite. It only seem to work if both parties to the conflict are democracies where meaningless war can put a toll on the government

GraphQL really did not handle fragments nicely. Why do you have to create subclasses for each use case and not just put your desired field name…

That’s the problem. In the days of jQuery/Angular2 (and even now personally), React was a blessing. Everyone hoped the same here. We should just join technology a little later on the hype cycle and have less stress.

Everyone in the comments just assume al jazera is right even tough we have well documented cases when they spread claims who are totally wrong with no journalism due process

See: https://honestreporting.com/damage-done-how-al-jazeeras-fake...

So to say truth has been silenced is off the mark imo

Edit: haaretz link https://www.haaretz.com/middle-east-news/palestinians/2024-0...

On the other extreme, Are media that spread misinformation without any due process are just protected indefinitely?

Like in this very recent case: https://honestreporting.com/damage-done-how-al-jazeeras-fake...

Edit: haaretz link: https://www.haaretz.com/middle-east-news/palestinians/2024-0...

So I guess the attack of the OP is a case AWS calculate price based on the unbounded request header and not on the actual egress

Again why mention the plugin? Just use the main caddy option… plugins are ment to expand caddy not replace existing directives

unless i am missing something and the plugin overrides default behavior then of course it’s to blame

Why is it the plugin job to mitigate IP Spoofing via X-Forwarded-For Header? Isn’t it the first gateway job? Just like I wouldn’t blame a container server for cdn not making sure X-Forwarded-For is not passed from the client…

Meaning how will the plugin know how levels deep is it in the infrastructure… and if you really care about warning devs then it should be a caddy level security bug, not this plugin specifically.

So all those spoofing items is really out of scope for this plugin…

I think you will be affected by the bigger picture. Mongo did this move also but there they were mostly in control before and after. Here there is a huge community of plugins. If before AWS shared a provider without hesitating, now they will ask themselves why contribute to a closed and possibly competitor garden.