• 2 Posts
  • 14 Comments
Joined 11 months ago
cake
Cake day: August 7th, 2023

help-circle
  • Exactly this.

    Just because you wrote your documentation a certain way, doesn’t automatically mean that you feel a certain way about any particular group, or that your users are primarily a certain gender. It may just be writing what pronoun you are most familiar with.

    In this particular case, we can see that the author didn’t exactly make the best case for himself.

    However, there was never a problem to begin with until the person that requested the change also accused the the author of assuming that the user/dev of the OS is male.

    If that little bit of accusation would have been left out, and they just put a note like “grammatical correction” it may have just been accepted and moved on. Instead they asked for a change while accusing the author of feeling a certain way.


  • There literally wasn’t a problem.

    Until the person that asked for the correction literally assumed that said dev was assuming. Since thats what they said in their comment.

    So I can understand being a little pissy at someone pointing to you and accusing you of assuming something. It’s stupid.

    I may have been a little irritated too if someone accused me of assuming something. I wouldn’t have reacted the same, but I would have been clear that I in no way assume anything related to gender identity.

    If the person wouldn’t have put that assumption into their comment, the change may have been more likely to happen.

    Instead they assumed something and got push back which turned into the scene we see now.

    Ass u me… I mean it’s pretty clear.



  • To be fair, it’s also kinda dumb to point out something as an issue when it clearly wasnt, and saying “assuming the user/developer if the OS is a male” means that the person complaining is assuming that this dev was assuming something because he used the word he.

    The issue was that the person decided that it bothered them so much that they needed to ask the dev to change it.

    This has idiots on both sides written all over. Why is that person being nitpicky over something so stupid. Women use she/her in their writing all the time, just like men use he/him, and people with other pronouns are more likely to use what is familiar to them such as they/them.

    I say this as someone with a child that has been reading books to them and noticed that an authors gender and the pronouns they use seem to correlate more often than not. Unless the book focuses on topics of or relating to understanding and accepting the differences in people. Both people are dumb in this scenario.

    Edit: let me put things into a perspective that maybe some of you can understand. Let’s take anything related to gender or being PC out of the equation.

    I ask you to make a change to your documentation because I don’t like the way you said something, then accuse you of being or believing a certain kind of way because of the grammar you used.

    That is what this person did.

    Now let’s assume (yeah I said it) for the sake of my argument that the person doesn’t feel any kind of way about the thing that they were accused of being. I’m pretty sure that person might just take offence to that. Which in this case is exactly what happened.

    Had there just been a change that said something along the lines of just a simple grammatical correction. It probably would have be pushed and ignored.

    In this case the dev definitely seemed like an ass, but that’s not the point. The point is the whole fucking situation is stupid.



  • I didn’t at first, but after the response from @mranderson17 I ended up doing just that. Which seems to have resolved that issue.

    Prior to enabling testing/unstable repos for access to Plasma 6.1, CM was working fine on Wayland. However after the update it seems to have broken it but changing to X11 fixes the issue. So it’s likely a combination of me messing with my system and something with Plasma 6.1.


  • Thank you for that.

    It didn’t help but it definitely got me moving in the right direction. I remembered that I recently (yesterday) enabled the testing and kde-unstable repos in my system so I could install Plasma 6.1 to check it out. Prior to this change I had CM working properly but was having issues getting CSP to work. Well, I figured out a workaround to getting CSP to work (after this change) by just copying over my install directory from windows on top of the install in Linux. However since I had already updated to Plasma 6.1 it came with the new issue of the drop down menus.

    I was using Wayland. Just swapped over to X11 and it’s working as intended. So something with Plasma 6.1 on Wayland is causing the issue.

    So mostly a bunch of messing around with my system is probably what is causing the issue and for whatever reason disabling the testing and unstable repos isn’t allowing me to revert back to the previous version of Plasma. Not really sure why but that’s a totally different issue.

    I really appreciate the time you took to give me such an in depth response.




  • Again, it is not a “Custom OS” you aren’t installing it as an OS from an ISO. You are still required to have your own licensed version of windows and install that prior to using AtlasOS. Using it does not cause security and instability issues as long as you understand what you are doing. Yes it is stripping things from windows. It’s also open source so if you were so inclined you could see exactly what is being done.

    If you equate using an automated solution to do things that you could do manually albeit with a bit more work involved, then every single OS is custom the second you change anything on it.

    I do use Linux for what it’s worth and have been for around 20 years. I’ve also been working in Tech for the last 15 ish years. I wouldn’t be blindly recommending something that would wreck someone’s security.

    Please do some research.

    https://github.com/atlas-os/atlas

    There’s a link to their source code. They even state that you have options to what security settings get messed with. So again, as long as you READ and understand what you are doing, you aren’t necessarily breaking your systems security.