u/ModulusTheDutchie

For a bit of context, I do enjoy furry fandom however I can. I enjoy creating lore for my fursona and fursuiting at my local furmeets. I carry a great deal of love for my sona, who is a reflection of me. But, furry fandom, especially on the Internet, tends to go beyond the description of "sex-positive". At times it feels like others are attempting to pressure me into having sex, getting off to this "hot thing" they found, etc. whether it is direct or done passively. "Unbelievably boring" is a label I wear out of spite towards other furries who judge me for not engaging in sex or kink and having no desire to engage in either. It's apparently unusual, even by asexual standards. Having recently come off my antidepressants, I find myself consistently brooding resentment just from looking at places like r/fursuit which, of course, aren't supposed to do that, but it happens nonetheless as it's perpetrated wherever someone can get away with it.

Now, I've made an interesting observation in the sex culture of furry spaces and on the Internet in general, including R34 which composes a major part of it. What they claim to be the "rule" is, in reality, a doctrine. R34 is a doctrine in the sense that people follow it by effect of assimilation (as in, you follow it because "everyone else" is following it, or are passively pressured into following it) because they are convinced to believe it's universally true by a uniform mentality. Doesn't that remind you of another notoriously sensitive group of people? Yes, I'm saying R34 and dogmatic religions are in fact two sides of the same coin; one side exploits fear, the other exploits stress. Rule 34 isn't a rule, because there are people like me who are wise to the fact that other people on the internet use the same tactics as Christianity to ensure its prosperity, subconsciously or not. Boring furries exist along with the furries who fear and harass them for not following what they believe is correct, notwithstanding the possibility they are that way because they follow a dogmatic religion or some other doctrine.

I wrote this in my frustration over how the norm is to chase temporary pleasures without any pragmatic considerations, as well as over my own belief that there is a better answer to life than either perpetually pursuing pleasure or living in fear of punishment. I am not making yet another call to combat these things, I am merely pointing out that neither one realistically gets you anywhere. That said, this is most definitely a sign for me to personally get off the socials for a while.

I recently upgraded the LCD on my ThinkPad P14s (IVO R140NW4D -> InnoLux N140JCN-EEL). The touch still works in BIOS, but since upgrading the display, the touchscreen functionality does not work in the OS and hwinfo shows that the monitor is still my old IVO panel. I've tried finding datasheets on my panel to determine what digitizer the InnoLux panel uses, to no success. The LCD itself works fine and I'm happy it how it works as is, but want to get the touch functionality working.

Is there anyone familiar with the process of creating touchscreen drivers that I could possibly get assistance from, and how does one publish such changes? Thank you very much in advance.

I just replaced the panel in my P14s Gen 4 with an InnoLux N140JCN-EEL (from the stock IVO Panel) and am currently trying to get touch functionality working on Linux. I can confirm that touch does work in the BIOS screen, but it does not work on Linux and hwinfo returns that the monitor is still the IVO panel. I feel like I'm missing something obvious as far as getting the right driver is concerned. Is there anywhere I should look? Thank you in advance.

I just replaced the panel in my P14s Gen 4 with an InnoLux N140JCN-EEL (from the stock IVO Panel) and am currently trying to get touch functionality working on Linux. I can confirm that touch does work in the BIOS screen, but it does not work on Linux and hwinfo returns that the monitor is still the IVO panel. I feel like I'm missing something obvious as far as getting the right driver is concerned. Is there anywhere I should look? Thank you in advance.

Here's the scenario... I have three displays: Two main displays and a mini display that is supposed to exclusively run btop++. I have a logon script to open btop in Alacritty and a window rule that forces it to go fullscreen and move to the mini display (i.e. "Fullscreen" set to "Force"). I can confirm the rule works when I click the Apply button in Window Management settings, but the rule isn't enforced when btop starts via the script executed upon login.

The script in question:

#!/bin/bash
alacritty --class 'Btop++' -T 'btop++' -e 'btop'

I'm running CachyOS with Plasma 6.6.5 and just updated everything today. Is there anything I could be missing? Thank you in advance.