gxt

This message has been brought to you by the Minister of The Truth of the Government of Canada. /// Ce message a été émis par le Ministre de La Vérité du Gouvernement du Canada.

Thank you for directing your hate at the specified target. /// Merci d'aiguiller votre haine à la cible sus mentionnée.

Assuming the interlocutor is stupid, at any scale, 1-1 to the whole of american politics probably just highlight that you don't fully grasp their point of view, because then it wouldn't be stupid. You'd be able to explain it to them and get them to see the matter from your perspective. If you can't do that, then you don't know you're right, you might be, but there's no way for you to know, truly.

> Your comment is nothing more than a broad ethnic slur

Have you considered that it may not be an insult but legitimate criticism?

The official government stat is 1.05M FN members. They have been targeted by over 200B$ in federal wealth transfers alone excluding tax incentives, provincial and municipal funding since 2015. That's almost 20K$ per person per year, more than what most Canadians pay in taxes each year and yet many FN communities don't have running water.

I think to ask about potential corruption or at least gross mismanagement is absolutly legitimate.

Anybody with access to these models can challenge it to test the hypothesis that spacetime is a 4d viscous fluid with the speed of light being spacetime's sound barrier, mass relating to viscosity, blackholes being cavitation bubbles, Hawking radiation our perception of surface tension, and gravity just being a pressure differencial? Thanks

You can implement a BTree with nodes stored in file-backed memmaps. It's plenty fast for the usual business case.

I'll take this opportunity to remind anyone on Azure that if you enable service endpoints on a subnet without applying service endpoint policies, anyone with the resourceid of an affected subnet can silently backdoor your network. Your NSGs do not matter for service endpoints.

You can audit your dependencies for crates with security vulnerabilities reported to the RustSec Advisory Database, also block unmaintained crates, and enforce your license requirements using SPDX expressions with cargo-audit and cargo-deny.

You can ensure that third-party Rust dependencies have been audited by a trusted entity with cargo-vet.

And you should have taken a look at where those 3M locs come from, it's usually from Microsoft's windows-rs crates that are transitively included in your dependencies through default features and build targets of crates built to run on windows.