> "You're convinced you should buy the one recommended in his video so you scroll down and find the affiliate link to that product"
Hold up, that's something people actually would do, click a link in a YouTube description instead of opening a new tab to search for it? Wild.
With Amazon, apparently the creator gets a percentage commission on your entire cart. Without the affiliate link, the price to me is exactly the same - Amazon just keeps the money. I assume AmazonSmile was basically using the charity you selected as the “affiliate”, but they shut that program down.
So yeah, it hurts my individual privacy stance, but it’s a drop in the bucket compared to all the data Amazon has about me already. Commission affiliate links at least redirect some of the revenue to the creator themselves.
If you don't add "RemainAfterExit", the service will run at every boot, because after a reboot it is considered "inactive. This will execute your shell code, which effectively toggles wakeup.
"RemainAfterExit" is meant for unit files that change the state of your system. After running once, the service will be considered "active", until you manually deactivate it, which will execute whatever you might have set in "ExecStop".
"Type=Oneshot" is necessary for "RemainAfterExit".
In this case I still would prefer doing it via udev though. I've made it my rule of thumb to evade shell scripting wherever feasible, because it usually ends up being more brittle, and more prone to footgunning :)
I remember there being some strange interaction with the wakeup behaviour being toggled otherwise. But this could be due to me being on NixOS.
I am not sure how correct this assumption is. S3 is supposed to cut power to everything but RAM, but for example Gigabyte Aorus motherboards are notorious for an NVMe SSD sleep bug that randomly prevents the system from properly sleeping or waking.
This is fixed by adding the following udev rule:
# Generic PCIe fix for sleep bugs by preventing wakeup from any PCIe port
ACTION=="offline", SUBSYSTEM=="pci", DRIVER=="pcieport", ATTR{power/wakeup}="disabled"
or more targeted: # Gigabyte sleep fix by preventing wakeup from problematic PCIe port, depends on motherboard model
ACTION=="offline", SUBSYSTEM=="pci", ATTR{vendor}=="0x8086", ATTR{device}=="0x43bc", ATTR{power/wakeup}="disabled"
You can find any glitched PCIe wakeup device with: 1. cat /proc/acpi/wakeup (you'll have to trial and error your way through the wakeup devices if it isn't immediately clear)
2. cat /sys/class/pci_bus/*/*/yourWakeupDevicePci/uevent | grep PCI_ID
3. prepend "0x"
You also have the option of: udevadm info --attribute-walk /dev/whatever
but for that you need to know some basic identifier of your glitchy device.Or if you want to shellscript it (less reliable than letting udev do it for you and needs to be done via systemd service file or another automation):
# Gigabyte sleep fix, port depends on mobo model
/bin/bash -c 'if grep 'RP05' /proc/acpi/wakeup | grep -q 'enabled'; then echo 'RP05' > /proc/acpi/wakeup; fi'";
Yes I really hate this (and other) Linux sleep issues.Running `echo GPP0 >> /proc/acpi/wakeup` into a systemd unit at boot solved the issue for me... except the first sleep after a boot would always wake back up immediately.
I applied your udev rule and that issue seems to be resolved as well!
Then one year my family went on a long car trip for a few weeks -- without the cello or even a radio since our car didn't have one -- and when we came home, my pitch was gone. It took just a few days to get back, but I realize that I have some sort of short term memory for pitch but do not have perfect pitch. It's not something that I'm concerned about practicing or maintaining. I'm a jazz bassist today, and my pitch is good enough for picking things up by ear, and maintaining my intonation while playing.
I wonder if there's a "spectrum" of pitch ability, and also a spectrum of how readily different people can learn it.
I always imagined the mental pathway for people with perfect pitch as being completely different from mine, but I could see it being a spectrum as well.
Intro EE is kinda brutal in that there’s a lot of theory to cover, and you need to build the intuition on how it applies to real world circuit design on the fly.
I had a bit of an epiphany when I was in a set theory/number theory class and some classmates were breezing through proofs that I struggled with. I was having to do algebraic manipulations in a way that was novel to me, but was intuitive to math nerds. I felt like that guy who didn’t “get” the intuition in an intro programming or circuits class.
But yeah, students often get some context for math or programming in high school, but rarely for circuit design. E&M in physics at best. EE programs have solved this by weeding out anyone who can’t bash their way through the foundational theory… which isn’t great.
If you’re still interested, I would recommend the Student Manual to the Art of Electronics. It’s a very practical, lab-based book that throws out a lot of the math in favor of rules of thumb and gaining intuition for circuit design.
How would a compound lens lead to a better estimate of the expansion rate of the universe?
> This unique configuration offers the opportunity to combine two major lensing cosmological probes: time-delay cosmography and dual source-plane lensing since J1721+8842 features multiple lensed sources forming two distinct Einstein radii of different sizes, one of which being a variable quasar. We expect tight constraints on the Hubble constant and the equation of state of dark energy by combining these two probes on the same system. The z2=1.885 deflector, a quiescent galaxy, is also the highest-redshift strong galaxy-scale lens with a spectroscopic redshift measurement.