Redjard

Females

jucky.

Also probably a function of the intended audience. Only happens when content farming stuff that hits a certain audience, and then it’s equally done by all creators. If you’re not an attractive woman you just put someone else in the thumbnail, like someone you interviewed, or if it’s game-related a character.

Don’t do it often enough to remember which is better and which is worse. The first search result isn’t garbage enough to bother with something else.

In those cases it’s less painfull to use a website to extract the transcript and read that.
You can skim around text way easier than a video.

TLDR: ddr ram refreshes itself, making cpus freeze sometimes when reading ram. High speed traders don’t want that so they figure out ways to make data live with two copies on two different portions of ram that freeze at different times. This is impractical for normal programs. Most of the effort is spent on working around multiple abstraction layers, where the os and then the ram itself changes where specifically data goes.

Every 3.9 microsconds, your RAM goes blind. Your RAM physically has to shut down to recharge.
This lockout is defined by the Jedex spec as TRFC or refresh cycle time. Now, a regular read on DDR5 might take you like 80 nanoseconds. But if you happen to accidentally get caught by this lockout, that’s going to bump you up to about 400 nanoseconds.

Think for a second. What industry might really care about wasting a couple hundred nanconds where one incorrectly timed stall would cost you millions of dollars? That’s right, the world of highfrequency trading.

[custom benchmark program on ddr4 ram and 2.65GHz cpu:] When you plot the gaps between the slow reads, they’re all the same, 7.82 microsconds [20,720 cycles] apart every single time. […] So, the question is, if this is so periodic, can we potentially predict when the refresh cycle is going to happen and then try to read around it?

See, it’s not like the whole stick of RAM gets locked when the refresh cycle happens. It’s a lot more granular than that. With DDR4, for example, the refresh happens at the rank level. And then DDR5 gets even more complicated where you can like subsection down even further than that.

The memory controller does what’s called opportunistic refresh scheduling, which basically means that it can postpone up to eight refreshes and then catch up later if we happen to be in a busy period. […] how the heck are you going to predict opportunistic refresh scheduling?

Then stuff about virtual memory management in modern OSs

And I take two copies of my data and I space them nicely 128 bytes apart. And I’m feeling pretty good about myself, but for all I know, it could be straddling a page boundary and then the OS could have decided to put them wherever it felt like putting them.

physical ram address issues:

So the exor [XOR?] hashing phase kind of acts like a load balancer baked like directly into the silicon itself. Takes in your physical address, does a little bit of scrambling, and tries to spread it out evenly across all of the banks and channels.

This also helps with rowhammer attacks where writing close to a physical address lets you write to that other address.

So, DRAM [XOR] hashing strategies were already not documented publicly. But then after the entire rowhammer thing, obviously, there was even less incentive to publish these load balancing math strategies publicly.

If AMD and Intel documented this kind of stuff, they’d kind of be like locking themselves into a strategy because customers would start to build against it. And then next year when it comes around, it’s really going to make your life difficult because you’re not going to be able to change things nearly as easily. But if you just don’t document it, well, who’s going to complain? only weirdos doing crazy stuff like me.

Inside of your CPU, right next to the memory controllers, there’s actually tiny little hardware counters, one for every channel. […] If we do a simple pseudo [sudo] modprobe AMD uncore, it reveals those hardware counters to the standard Linux Perf tool. […] If I write a tight loop of code that constantly flushes the cache and hammers one particular memory address, then that means one counter should start to light up. And theoretically, this should tell us exactly what channel that our data is living on.

Can’t really tell what’s going on here. Well, that, my friend, is OS noise. […] The problem is these counters are pretty dumb. So you can’t tell it only count the reads from this particular process. […] All we need to do is run it 50,000 times. […] See that spike? Super cool. And now I really know where my data lives.

So, to me, I don’t really care which channel I’m ending up on, whether that’s channel 3, channel 7, whatever, doesn’t matter to me. All I need to do is make sure I’m ending up on different channels. […] The mathematical answer is that XOR is linear over GF2 which is actually really simple. Basically that means that no matter what scrambling the memory controller does, flipping a base bit will always flip the output no matter how many things are chained together.

Goes on to write low latency benchmarks which show lower latency.

ubo has a button to disable javascript. For news pages that tends to be the easiest way to make them barely usable.

Lots of huts probably have an ac or heater. This could all be the same device, at which point it’d definitely be easier than running the pipes for water and maintaining pumps and a dedicated tank.
Don’t see a reason you couldn’t have a simple ac window unit that also has a warm water port, which you plug a single cable into going straight to your pannels on the roof.

Edit: And once batteries are more affordable (or if you have a few grand to burn) you can then plug in a battery pack conveniently on the indoors side of your window unit.
The indoors side can just have a few regular outlets you can extension cord around to where you need them.

Modern solar into a modern heat pump is gonna be more efficient than heating water. It’s also more versatile and convenient, cause it maintains that efficiency when you pull power from the grid at night. And of course lets you use the power for other purposes.

In serious, most ways to loose blood and need blood infusions will loose the plastics too, so the donated blood just maintains the concentrations, the samw way it does for the other components.
Everyone has plastics in their blood.

But then if you donate frequently your blood will have lower concentrations due to all the previous donations, so don’t just donate, donate often.

You should to regularly let donate blood to expell the bad humors microplastics.

can make it round so the syrup spreads more evenly from the center.

Oops you made pancakes

Not sure how far you wanna go. I know my way around mediawiki from the sysasmin side (installing, updating, installing extensions and themes, configuring weird features like ldap auth, …), the admin side (css, users and groups, templates and lua scripts), and some moderation (editing etiquette on wikipedia and a few other wikis, typical style guides, organization of pages and overview pages).

I’m quite busy lately, but you could ask me some questions via dm for example and I would be willing to do some small things.

Clarity can also be achieved with a 4k panel. Once your panel gets over 600ppi it’s gonna blow an eink screen out of the water at its own game. Those phones were barely ever made only Sony even tried. Probably due to battery life, or maybe noone realized what they do to the reading experience.

Either way we’re gonna improve battery life and maybe even get microled before eink ever gets competitive with emissive screens. Someone is bound to rediscover that you never truly needed eink for comfortable reading, just a significant increase in resolution.

It’s also completely fine under all international law.
Following copyright law is more like a trade agreement, so if you feel wronged enough as a nation it’s completely uncontroversial to suspend all or all international copyright law and deal with the consequences (mainly the us being very salty about it).

The EU contingency for a US attack on Greenland for example is among other steps to suspend all US copyrights recognition and starve the US service industry.

Most lenses only care about the angular light distribution, essentially averaging over the lens surface. So a ding or crack would just add a tiny portion of grey or black to the entire image

Edit: This is for cracking the front protective glass of a camera lens. If an actual optical lens splits in two it will be misaligned and bad things will happen.