So a Lemmy shitpost is just a reddit cross-post? The actual OP didn't give any context to the images. Even if this isn't a bot post, it might as well be one.

https://www.reddit.com/r/funny/comments/1u8qzwv/bathroom_doors_i_painted_in_a_bar/

Not yet.

I think there is a much higher probability of oil prices being manipulated in the short-term.

You forgot about the radio towers that have been in Belarus that allow Russia to control long range drones. Ukraine took a few out already, but there are likely more. (I'll have to check recent drone paths to see if there are still issues.)

B.J. Nomnom

Compliance audits are usually handled by a third party and I am only familiar with SOC2, SOX, PCI and ISO27001. GDPR is a beast, from what understand. I do suspect it's also ran by a third party during an audit period.

Most of the above compliance programs require network architecture reviews and checks to ensure that their policies actually match how their internal processes and software actually works. This typically includes compliance enforcement mechanisms, such as what we were discussing.

More often than not, GDPR data deletion requests work for just about anyone. Companies don't really have the time to validate what country you are currently in so these kinds of processes are usually just generic. (It's a compliance requirement and usually only gets the bare-minimum effort and funding to develop correctly.) Since any company asset is in-scope for compliance regardless of the country, companies that reside in the EEA must also purge any data for servers that may be outside of the country.

It never hurts to attempt a data deletion under the context of GDPR, regardless of your country, is my point.

But just to clarify "it depends on the country": Of course it does, but the country where the company is based out of, not where their servers are located. (Of course there are one-offs or weird situations. That kind of "data protection" is expensive and reserved for bulk data that companies really need to hide or keep out of scope of compliance.)

I also forgot to answer your actual question! :)

Trigging the overdraw protection on a PSU is generally not a horrible thing, but it really depends on how the PSU does it. I would generally assume that that Corsair uses a proper current monitoring circuit with my best guess being a resisor shunt of some kind in combination with a proper monitoring chip that triggers a solid state switch to cut power extremely fast. Cheapers PSUs may just use a resettable fuse, which is also "solid state" but may actually fully blow (ie: esplode) or become less effective over time. Absolute worst case, a capacitor may blow its top. (If you have an old PSU you can destroy, flip the switch to 115V and plug it into a 220V circuit. You will get a loud bang and some smoke, but generally, nothing extremely dangerous. Its worth it to see and understand how PSUs may fail catastrophically if you never have blown up a large capacitor.)

The biggest warning sign of overloading a PSU is heat. PSUs get warm naturally and will get hot under heavy load. If the PSU has a fan, just occasionally feel the air and if it's getting uncomfortably hot, you might be getting in the danger zone. Heat will naturally change resistive properties of different materials, leading to variations in current flow. This is normal. However, heat can trigger "thermal runaway" conditions where a component gets hot, starts to draw more current, gets hotter, draws even more current and will eventually melt or explode. Not good, but also normal. Hence: Heat is a good indicator of a device that is about to fail or shut off. (Current overdraw circuits may also use thermal sensors to shut off the device as well.)

If the device gets overly warm, point a fan at it as a temporary solution. It'll give you just a hair more wiggle room during overdraw conditions. Not much wiggle room, but wiggle room nonetheless.

In short: High current loads/pushing components over rated limits is never ideal, but it's not extremely bad either. It shortens the total life of the device itself and its safety circuitry, but it's ok for short periods if you aren't stupid about it.

(Sorry for the TED talk, but it's my way of walking through the different scenarios of what you are trying to accomplish. FWIW, I have a ton of experience blowing up electronics so I am probably more familiar with pushing safety limits than most casual users.)

Bonus: Overclocking/Overvolting is not always going to shorten the life of equipment. Damage is caused by poor and ineffective cooling, but that does take proper planning and testing. Factory overclocked devices are usually still waaaay under their actual (and usually undocumented) thermal/voltage limits. However, you are usually getting really beefy heatsinks and additional fans for those kinds of cards. If you run a "factory overclocked" card at normal load, its additional cooling will theoretically extend the life of the card beyond its actual useful lifespan since it it's being run far below it's rated thermal limits. (This paragraph sounds like a contradiction in itself, but makes sense when taking the total useful life of the card into account, before it actually is completely outdated and is only good for scrap.)

You should be ok, even if you touch 750W every now and then. Corsair PSUs are generally decent and can likely hold over 750W for short periods. What you are sacrificing is PSU efficiency, but if it's temporary, whatevers. Don't overclock the CPU and under volt the GPU and don't run heavy and continuous compute loads for long periods of time.

While the power management is likely a hair different with my flavor of 7900XTX, it has always behaved well under heavy load and benchmarking and it rarely spikes to max power unless all the OC knobs are pushed to max.

Unfortunately, I can't speak to how the 7900XTX is managed under Linux. If I am not mistaken, unless you are purposely overriding power profiles, you should be fine with whatever the stock settings are on the card itself. (7900XTX's do come in non-OC and OC variants or have a switch for a dual bios for either configuration. Manufacturer OC settings can still be quite timid, IMHO.)

Depending on your specific components, the system may crash before it hits a power limit in some cases. If the PSU can't handle the power draw requirements, the power rails might sag a little during a burst and crash the system. I have only seen this a couple of times, but it's still worth mentioning.

Ignoring all of the above, just run some tests under different power loads, and in this case, aim for the lowest power settings you can, just to be on the safe side. While not perfect, invest $20 in a kill-a-watt power draw monitor for system testing. At a minimum, you will get a rough idea of total system power draw, which is good enough here. (I have seen ~+/-5% skew between different kill-a-watts, which isn't an issue unless you are seriously working against a strict draw limit.)

I would normally say this is a parental issue. However, the quirky combinations of vitamin b, caffeine, massive amounts of sugar combined with whatever else is even slightly rumored to boost energy should be, at minimum, slightly regulated for youth.

I am not doing deep-dive research for this comment, but I would speculate that the above drinks are simply not healthy for developing bodies and brains.

I also suspect that the biggest issues are with lack of moderation.

Data is shared through a data "hub" of sorts.

Health Connect centralizes most health specs from across multiple android apps and is commonly implemented into scale apps, BP meter apps, etc...

There are limitations on what an app will share in Health Connect, and also what an app reads. This is determined by the specific health app itself. For example: Google Health will dump a ton of metrics into Health Connect, but Garmin is very limited on what it actually reads from it from other apps. (This is likely by design, by Garmin)

After comparing data accuracy from my old Pixel Watch to my new Garmin Fenix 8 Pro, the difference is quite significant. Garmin is absolutely more accurate. Stats (like VO2 max) may be calculated very differently and therefore, scores may not be "compatible" across equipment brands. (If I was a Garmin engineer, I would choose to ignore data sources that have a higher degree of inaccuracy as well, IMHO.)

However, why you are only seeing data from your scales now is anyone's guess. Any vendor involved may have fixed something, or simply integrated a few data feed from Health Connect. The main point being that Garmin may only just pull data from Health Connect and not directly from Google Health itself.

I also assumed you are running an Android phone. I have no idea what the equivalent of Health Connect would be on Apple.)