Adalast

For now. Remember that Project 2025 aims to dismantle both organizations and privitize the NWS's activities.

Fact checking myself: https://www.pbs.org/newshour/politics/fact-checking-what-project-2025-says-about-the-national-weather-service-and-noaa

This is a cultural thing. My wife has studdied German culture, particularly relating to their relationship with their language, pretty extensively and from what she says they are exceedingly resistant to changes to their general language at all. Hence all of the compound nouns for new devices instead of coming up with a new word. Apparently the cultural adoption of "Das handy" for cellphone was a cultural milestone since they actually used something new instead of trying to cram together "Mobile Wireless Vocal Communication Device" into one word.

I hace been using noscript for like 15 years now. In my experience, it comes down to recognizing what is a required and superfluous or privacy invading 3rd party. Some websites can take me a while to get working, but I have had very few which I cannot figure out.

You assume that the governments of which you speak are not assisting intentionally. These companies did not write the EULA legal frameworks that allow them virtual carte blanch to take and do whatever they want just because the population is trapped in the endless cycle of coercion that is our life.

Why do all of these companies decide they are so tired of existing?

This is why I use a script blocker to block the scripts from marketing domains. From what I have been able to see the cookies aren't written because the code that writes it is not allowed to execute. It also stops script injections and other malware payloads that require extra-domain linkages to scripts.

Plus all the political stuff. The man is patantly off his rocker.

Incompetence might even be a little harsh. Inexperience or incompetence maybe. I prefer inexperience.

I prefer the answer of giving the giy the reins and letting him get it so riddled with viruses then when he calls for support replying "sorry, your property your problem. You have absolute dominion over it and thus we give no warranty as we have no responsibility."

Not that I know of. In the end you are editing the browser rendering parameters. Anyone can inspect the page and see that the opacity on the page is being turned down. Finding where it is happening is the only thing you can really make hard. Have a couple of the pass through scripts be machine generated and you can have it use nonsensical variable names and a bunch of dummies that lead on wild goose chases. It could all be fixable, but you can make it a pain in the ass. Add a redundancy or two and it will make debugging a nightmare because even if one is fixed, the others will make it look as though it has not.

The real answer is to have NEVER do freelance web development inside the client's firewall. Never. If they try to require it, walk away. If it is inside their firewall then they can just take the source code and stiff you. If they try to spout some BS about security, say that is precisely what you are concerned about and point blank ask them what safeguards they are willing to allow you to put in place for developing in their system. If the answer is none, walk. If they are willing to let you VPN in, run the code from a local copy over the VPN and node lock it so if someone attempts to serve it from another machine it fails.

Apologies. I'm tired and hate businesses taking advantage of "Independent Contractors".

Bury it six JavaScript and 2 php scripts deep so it is a pain in the ass to find.

They are both Gramps, Trump is just gramps wearing Kristy makeup.