The second two are orders of magnitude easier than the first. Out of date code usually just means it relies on some ABI that was deprecated, so it needs to be updated with the new functions. Microphone pin quirks are fairly common so there are a lot of resources available a search away.
I was fully onboard with everything you said until this. It pretty much defeats the point of a boycott to continue using the service in a way that makes them profit.
Okay, so you already admit he HE LIED. And it's a ridiculous reason anyway, hospitals don't get masks at the grocery store, they have their own suppliers. He could have even told people to wear cloth masks!
There absolutely were mask shortages. Full stop. You are the one lying.
Your first sentence also contradicts this-you said "There were mask shortages and they wanted to ensure the front line medical staff around the country had masks first" There it is, he knew masks were working, and he told people not to wear masks. Not because of 'new data' but because he wanted to prevent mask shortages, which didn't work anyway and helped the disease rapidly spread because people were told not to mask.
Convenient of you to leave out the part about ASYMPTOMATIC TRANSMISSION that I mentioned, which they didn't know yet. Masks for symptomatic people and people caring for the sick were always recommended.
There were mask shortages and they wanted to ensure the front line medical staff around the country had masks first
When he said that we didn't yet know about asymptomatic transmission.
There wasn't any data yet on how the virus spread.
There wasn't data on if homemade cloth masks would be effective.
He reversed this stance a month later when the data supported the guidance.
This is the kind of bullshit peddling that causes people to mistrust science. He made a decision based on the best evidence at the time, and then continued to update that stance as new information came in. What you're doing is exactly the kind of post-mortum FUD that the person you replied to was talking about.
If I'm not mistaken, you can make rules per device ID. Keychron devices show up as a keyboard/mouse and a "Link" device. You could make a passthrough rule just for the Link, thus not granting access to the actual input device.
That's great, just be sure your rules are specific enough for that device but didn't rely on some randomness for detection. I.e. Matching on the current evdev or hidraw devnode is bad because it can shift with more devices being added, changing ports, or some randomness in enumeration speed. Instead, do an attribute walk on the devnode to find specific unique attributes for that node, such as VID + PID + subsystem + bInterfaceNunber should be unique. Things like names and phys patch aren't guaranteed to be unique or consistent in different operating modes. You'll also want to check the devnodes of the other interfaces to be sure they won't match by doing a test.
The commands for those things are:
udevadm info -a /path/to/devnodeudevadm test /path/to/devnode
Could you elaborate on the OpenRGB thing? I've used it a few times but never paid attention to the rules it asks for
Sure. While not technically necessary for some devices, they have pretty open blanket udev rules. This is because most keyboard devices require the use of hid reports directly to the device to make changes.
From their page:
On Linux, OpenRGB needs permission to access the hardware interfaces used for RGB control. These include USB and I2C interfaces. To make accessing these interfaces easier, OpenRGB provides a udev rules file that tells your operating system to allow your user account control over these hardware interfaces, allowing OpenRGB to run without root access while still controlling the hardware.
Notice the complete lack of warning about any security issue from doing this.
If they wanted to be secure they could make a root level daemon that does all the hardware interfacing, and provide a dbus interface managed through polkit to allow making those changes from the userspace UI.
Be careful with this. These udev rules usually grant uaccess to your entire keyboard. uaccess is explicitly disabled for keyboards by default because it presents the event device to all of userspace, which allows any unprivileged app to log all key presses. This includes any malicious scripts running in a browser. If you do want to set up these rules, use them only for the single session you're setting up your device and don't type any passwords with it active, or change them immediately after (you won't be able to remove them without your sudo password).
For the same reason, stop using OpenRGB for devices that don't have kernel drivers.
I agree with you, but so does the person you're responding to. I think you're missing the semantic argument they were making that criticized the absolutist language used to describe Yoko's artistic endeavors. They were highlighting that the term "objectively garbage" was in reference to something inherently subjective.
I live here because it's a good place to live. If the country goes to shit, I move on.
If something negative starts happening in my community I work to fix or resist it, so it starts a good place to live. Instead of selfishly running away I work hard for the coming good. That's what patriotism is about. You sound like someone who wants to reap the benefits of a good society without doing the work to make one.
This is also an absurdly privileged take. Very few people have the economic means or are capable of handling the emotional impact of moving from their family.
Do you feel patriotic love towards the supermarket you shop at? Or do you go there because it's currently the place where you get the best deal? Do you love your petrol station? Do you love the highway or train you use to get to work?
This is an absurd strawman. I care about the people who work in those places, and that those places are effective and equitable.
Maybe it's the american weirdness that you guys don't value love so that you mistake thinking that somethig is ok is automatically deep love or something weird.
Inflammatory rhetoric from someone who clearly doesn't actually know Americans.
Patriotism has exactly on purpose: to keep idiots in line and stop them from thinking.
Considering you can't stop conflating patriotism and nationalism in your responses, perhaps you should be a little more careful of who you call an idiot.
I think you're more of a patriot than you realize. A patriot loves their country for what it does and criticizes it when it does things they don't like, while a nationalist loves their country regardless of what it does and criticizes those who want to change it.
The second two are orders of magnitude easier than the first. Out of date code usually just means it relies on some ABI that was deprecated, so it needs to be updated with the new functions. Microphone pin quirks are fairly common so there are a lot of resources available a search away.
I was fully onboard with everything you said until this. It pretty much defeats the point of a boycott to continue using the service in a way that makes them profit.
Why yes, of course ! 100% of low income people are fully served by public transit everywhere. Why didn't I think of that?
There absolutely were mask shortages. Full stop. You are the one lying.
https://pmc.ncbi.nlm.nih.gov/articles/PMC7129293/ https://www.theatlantic.com/health/archive/2020/04/why-were-running-out-of-masks-in-the-coronavirus-crisis/609757/
They then told people to make masks at home and leave the N95 for healthcare workers.
https://www.healthline.com/health/how-to-make-a-mask-out-of-fabric
https://twin-cities.umn.edu/news-events/diy-face-masks-during-covid-19
Convenient of you to leave out the part about ASYMPTOMATIC TRANSMISSION that I mentioned, which they didn't know yet. Masks for symptomatic people and people caring for the sick were always recommended.
https://www.latimes.com/science/story/2021-07-27/timeline-cdc-mask-guidance-during-covid-19-pandemic
All of these articles were posted during COVID. You're full of shit. Stop spreading lies.
Lied is doing a lot of dishonest work here.
This is the kind of bullshit peddling that causes people to mistrust science. He made a decision based on the best evidence at the time, and then continued to update that stance as new information came in. What you're doing is exactly the kind of post-mortum FUD that the person you replied to was talking about.
That's great, just be sure your rules are specific enough for that device but didn't rely on some randomness for detection. I.e. Matching on the current evdev or hidraw devnode is bad because it can shift with more devices being added, changing ports, or some randomness in enumeration speed. Instead, do an attribute walk on the devnode to find specific unique attributes for that node, such as VID + PID + subsystem + bInterfaceNunber should be unique. Things like names and phys patch aren't guaranteed to be unique or consistent in different operating modes. You'll also want to check the devnodes of the other interfaces to be sure they won't match by doing a test.
The commands for those things are:
udevadm info -a /path/to/devnodeudevadm test /path/to/devnodeSure. While not technically necessary for some devices, they have pretty open blanket udev rules. This is because most keyboard devices require the use of hid reports directly to the device to make changes.
From their page:
Notice the complete lack of warning about any security issue from doing this.
If they wanted to be secure they could make a root level daemon that does all the hardware interfacing, and provide a dbus interface managed through polkit to allow making those changes from the userspace UI.
You know that meme from the office where Pam is told to find the difference between two pictures?
Pretty sure 'vulnerable' was intended.
Be careful with this. These udev rules usually grant uaccess to your entire keyboard. uaccess is explicitly disabled for keyboards by default because it presents the event device to all of userspace, which allows any unprivileged app to log all key presses. This includes any malicious scripts running in a browser. If you do want to set up these rules, use them only for the single session you're setting up your device and don't type any passwords with it active, or change them immediately after (you won't be able to remove them without your sudo password).
For the same reason, stop using OpenRGB for devices that don't have kernel drivers.
Okay, but also time machine.
There's no way that could backfire, surely.
Because that worked out so well the last time...
The super Nintendo had a mouse controller. You could use it to swat fly's in Mario Paint https://youtu.be/L9oJRsw_Abs
You can care about more than one thing
This person's writing style is, frankly, well, pretty obnoxious.
I agree with you, but so does the person you're responding to. I think you're missing the semantic argument they were making that criticized the absolutist language used to describe Yoko's artistic endeavors. They were highlighting that the term "objectively garbage" was in reference to something inherently subjective.
If something negative starts happening in my community I work to fix or resist it, so it starts a good place to live. Instead of selfishly running away I work hard for the coming good. That's what patriotism is about. You sound like someone who wants to reap the benefits of a good society without doing the work to make one.
This is also an absurdly privileged take. Very few people have the economic means or are capable of handling the emotional impact of moving from their family.
This is an absurd strawman. I care about the people who work in those places, and that those places are effective and equitable.
Inflammatory rhetoric from someone who clearly doesn't actually know Americans.
Considering you can't stop conflating patriotism and nationalism in your responses, perhaps you should be a little more careful of who you call an idiot.
I think you're more of a patriot than you realize. A patriot loves their country for what it does and criticizes it when it does things they don't like, while a nationalist loves their country regardless of what it does and criticizes those who want to change it.
Bruh, they moved rename file. That shit has been in the same place since 3.1. Fucking why.
It will be enabled by a kernel config option, yes.