Waiting for IPv8 when the delivery guy takes a slice and feeds it to me so I don't need to worry about greasy fingers.
ulterno
joined 8 months ago
My ASUS laptop has this problem where, if there is no sound output for a while (that "while" is just a few seconds) then the next sound will start with a big pop sound.
Probably either a firmware thing or problem in the sound card itself (does the same on Linux).
I'd say, every time, generate a new page with some variations:
- randomly change the position of the checkbox
- randomly change the contrast colour of the checkbox as long as it is visible enough to humans (sorry accessibility)
- randomly change HTML tags (id, class etc) to prevent finding the check box by parsing source
- add trap checkboxes with
display: none - add "I am a robot" check boxes at other locations on a page
- write them before the actual checkbox in HTML (to catch parsers), but use CSS to display it such that the user looking at the page will see the correct one more conspicuously
- write "I am a human" next to the trap checkbox in HTML, but use CSS to position it next to the correct one (this might be harder to implement properly)
That way, if one is to use a bot to click it, they will have to use machine vision, which will be expensive enough and satisfy Redex's condition.
Keep your banking related system separate from the system in which you install closed source stuff.
That includes stuff like GPU drivers.
I wish that could include stuff like microcode.
Guess if you can afford RISK V, then it's worth it.
That's competence, not incompetence.
Just that their goals are different from ours.
I thought it was depicting Urashima Taro but I guess it could be what you said.
I don't get either of those contexts.
When I read "Quakers", I just recalled Quake III Arena and thought, "that doesn't fit".
I might have ended up doing the same if I didn't have to earn
YAML definitely felt less intimidating to me than XML, when I first saw them.
But the YAML examples also had much less information in them than the XML ones.
But not having to type all those brackets definitely helps.
In case of XML, I am always looking to just get a GUI going for it instead, because typing it out feels cumbersome (I'm from C++)
StealersOf.info would have been more fun...
it just had less brackets and <> symbols when they were done.
Hence making the parser more inefficient than XML?
What is the rationale behind GPU heatsink fin design?
So I have seen a few GPU heatsinks and I wonder why some of them are how they are.
GPU placement in Cabinet
The originally intended and most widely used placement for ATX cases at least, is installing right on the PCIe slot, which goes horizontally and with the air incoming from the front of the case.
Then we have the "vertical" placement using the riser cable, which changes the direction from which the GPU fans take in air, but keep the GPU front, in the same direction, again lining up with the incoming air from the front.
Finally the very rare vertical placement, which has the front of the GPU rotated towards the top of the case, making it not line up with an airflow incoming from the front.
This also makes the GPU's ports inaccessible the standard way, giving a reason to the rarity.
Some examples I found for this
Here we see that the first 2 placements would make up most of the ATX PC builds with the third one being either for different case styles or for extensively customised builds.
Fins, fans and airflow
I would assume that having the air flow along the fins would be better than it crossing the fins at ⦜90°. And even if the air flow due to the case inlet is being ⟂ to the airflow from the GPU fans (in case of front incoming air flowing along the fins), it should still lead to overall increase in air pressure (hence, air density) between the fins.^[Source: Mental simulation] Considering that GPUs tend to have gaps in the IO shield to let the air go out the back, I would assume they (designers of the thermal dissipation solution) want air from the fins to go out the back, which would be better with fins parallel to front incoming air.
Inference and Doubt
From the above 2, it would make sense for most GPUs to have their heatsink fins going along their length instead of their width, right?
Then what's up with the ASRock lineup, with all cards other than the Passive model, the Creator cards (which have the front covered by the shroud anyway, so no incoming airflow) and the watercooled cards (which is not applicable) having the fins ⟂ to front air inlet?
And of course they are not the only one doing it that way.
Follow Up
While discussing in this thread, I realised another point (which I didn't state anywhere in the comments):
- While it is desirable to have higher air density, it is not desirable to have air increasing in density while in the inter-fin space. Because that would cause the heat released when changing density to be transferred to the fins.
- Another way to say that is, the air will get hotter, while increasing its density. So, how much this factor matters, will depend upon the initial temperature difference between the air and the fins and how long the dense air stays in the inter-fin space. Oh and also the composition of air.
28
[~~Help~~ Diagnosis] How to turn off power to NVMe SSD? OR Why/How is my SSD heating up in weird ways?
(programming.dev)
I have a multiboot system.
One of the installed OS's does not use the NVMe SSD installed on the motherboard at all.
At the time of taking the screenshot, all the SSD partitions are unmounted, so apart from detection, the SSD is mostly unused.
- I would like the temps to drop down to SYSTIN (≈35°C) levels.
- I know, it's right next to my GPU, but I am not doing anything GPU intensive, the GPU temps are ~37°C ^[apart from GPU memory, which is 48°C due to the awful AMD 7th gen Zero RPM, which has no workarounds on Linux]
For the unmounted and unused HDDs, I just use hdparm -Y, but there seems to be nothing in terms of that for the SSD.
And even though I appreciate the additional heat in winters, this is going to be too expensive for me. I'd rather burn some cheap Nichrome than my data storage device.
I checked out a Debian forum thread and from that, I checked the following:
❯ sudo nvme get-feature /dev/nvme0 -f 2 -H
get-feature:0x02 (Power Management), Current value:0x00000004
Workload Hint (WH): 0 - No Workload
Power State (PS): 4
Showing it is already in the lowest power state.
Update: I probably checked that at the wrong time before. Did so again after Sleep and realised the Power State was 0. So just need to make sure the Power State went back to 4 after wake.
I have no active cooling setup for the SSD from my side. This becomes relevant soon.
-
Checking the SSD temps (using the same widget as in the image), the temperature on Sensor 2 starts out at ~40°C (after a normal reboot) and slowly increases to >50°C as shown at the start of the graph. Power State (PS) is still 4.
-
Running KDE
partitionmanager, which probably does some reading to check the partition information, at 50°C stage, causes a temperature drop, as shown in the image. -
Running KDE
partitionmanagerright after reboot, when the temperature is increasing very sloowly, seems to do nothing significant.
- Turns out that after a few minutes of System Standby, the SSD doesn't return to
PS: 4, so I have the culprit. - Running
partitionmanagerafter that causes it to go back toPS: 4
So we have a solution! All I need to do is run partitionmanager on wake. nlol jk
Motherboard: MSI MAG X570S TORPEDO MAX (MS-7D54)
SSD: Samsung 980 512GB (correct firmware, bought long before the fakes started coming out)
view more: next ›
Could be some sort of an overly convoluted money laundering method.