I got the same treatment recently. All tech departments were issued M4 Mac Book Pros because that was more cost effective than than dealing with the non-compliant fuckery of W11. Unfortunately non-tech departments got the old inventory and are suffering the abhorrent instability of W11. It somehow refuses to play nice with just about everything in our corporate ecosystem.
Funwayguy
joined 2 years ago
The first mistake was thinking OpenAI gives a damn about privacy given they're more than happy to sell that out to Police. Whether it's a judge or a hacker, it's only a matter of time before someone gets a hold of that nuclear bomb worth of data.
If you don't use the VPN for normal things then you leave yourself open to indentification by correlation. It's the same rule for naive Tor users. The more normal and distributed it appears in traffic, the harder it is to correlate other pieces of data they they already have access to.
My tinfoil hat theory is that this instance is less a cashgrab and more an attack from AI slopbros to drown out criticism their billionaire overlords.
Really keen to sit down and read this book though.
I like how we're all skimming over the fact that they fed federal compliance data into Azure OpenAI seemingly without permission or oversight.
How after "5 hours" of decision making was it ever an option at try and appease any demands of the Russian government. It never works and never ends.
Heck if you wanted to even try this, make it a geolocation based visibility filter and let the VPNs do their thing.
I switched to KeePassDX for this reason among others.
Same on my M4 work mac. Tahoe has annoying graphical glitches in several liquid glass modals and the damn calendar app wont scroll through my weekly meeting schedule properly anymore. The UI overall feels half baked and far less customisable than the marketing otherwise suggests.
Also, if anyone knows how to shutoff that god awful 'bounce' animation on every damn tooltip that fucks with my eyes while I'm trying to write code, it would be greatly appreciated.
See that's the fun part. Google is the ad company so it's all 1st party data. Google can package the Trojan horse however they please, which why it's such a fine line for the blockers to walk.
It wouldn't matter whether it was intentional or not. Put simply, Google can continue indirectly punishing creators for tolerating adblockers then redirect blame, even though they could have easily separated the metrics from the advertising and telemetry endpoints that blockers filtered. This way they get their money either from unblocked ads or from creator's reduced view counts, win-win for Google.
As an added bonus for Google, by ensuring view metrics get fucked up, it double punishes creators featuring sponsored content that rely on those metrics to determine how much the sponsor should pay them. Meanwhile Google could, in theory, sell ad placements attached to their own internal metrics that differ from the affected ones publicly visible.
More of an assisted drop than a mach 5 launch (though that kinda liftoff would be fun to see), but yeah it would have to take the armour with it, not that it makes much difference if the battery is ready to toast everything in the vicinity.
If airbags going off at highway speed isn't an issue, we can probably do just as well checking several conditions (controlled stop) before pulling the trigger. Then again, this is assuming the brains are smarter than the ones yeeting a burning battery into a sidewalk.
view more: next ›
The immediate issues I see are:
The bulpup arrangement gives it a moment arm that would bend your wrist rather than push into the palm of your hand on recoil.
Even if your wrist is fine, the hot gasses escaping the cylinder would be directed straight into your forefinger and thumb with every shot.
Finally, a break action or flip-out reload would now use space occupied by your hand around the grip. Not to mention a break would require the trigger and hammer mechanisms to be on opposite halves adding complexity and potential reliability issues.