I have one of these and a dumper.

I took all of the games we have and dumped them onto an SD card. I use it for the second switch we have that our kid uses.

No messing about with swapping cartridges and taking a chance on losing one, which has already happened once.

I ended up with a V2 which is even better. No wear and tear from popping the cartridge in and out and all the games on it.

Aside from the “inconvenience” of having to push the button to roll through the games, it was worth it.

I’m curious about the stick drift thing.

I have 3 controllers, two of which I’ve had since maybe 6 months after the PS5 was released since that’s about how long it took me to get one.

Both controllers have a few hundred hours on them, neither have stick drift. The third one doesn’t have nearly the amount of hours on it since my kid spilled juice on it and I procrastinated for a few months to take it apart and clean it lol so I’m not considering that one.

Is it really that bad or did I just get lucky? These things are almost 4 years old and still work perfectly fine.

Just a note for those interested in the local play aspect of it like I was.

You don’t need to create an account to play the game locally.

You can just exit out of the first menu and play the scenarios that are available.

I was considering that, but was reluctant to do it without any advice since I don’t know enough about the Deck and how it works other than it runs on a variant of Arch.

After your comment I did try it and it worked.

Thank you!

Edit: just realized you said US based. Tuta is not US based so that might not work for you. Sorry about that.

Tutanota (now just Tuta) allows you to use your domain. I use it, it doesn’t support external clients (Outlook, Thunderbird, etc.) but they do have Android, Linux, Windows (maybe Mac too) clients.

It’s also cheap.

I’ve been using it for a few years now, it works for me.

You can get a free account to check it out first and if you like it just upgrade to get the personal domain usage and increased storage limit.

Ahh ok, that makes more sense. To be fair though, I rarely saw any Subarus when I lived down south, but once I moved out west they are pretty much all over. So it’s not beyond the realm of having different distributions of cars in different areas.

There are Mazda 5’s for sale near where I live in the US. Where do you live in the US that they aren’t available?

Looks like Asphalt 9 was already grabbed by someone.

It’s actually being pushed as “broken” for 6.10 but should hopefully be completely available in 6.11.

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.

I understand that, but the whole point behind it was them making an assumption about something and proposing a change because they didn’t like their term that the dev used. Yet there was LITERALLY nothing wrong with the term.

The guy definitely made an ass of himself with his responses.

Like I said, both of them are idiots over this. It was pointless to make an issue out of it to begin with, and then then the dev making it even worse didn’t help.

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.

KDE is fine. I’ve been using it for some time now and never really had any significant issues that weren’t caused from my own meddling.

I say that as someone that has been on and off using Linux variants for probably 20 years now.

I run my kids machine on pop os with KDE, auto login that opens steam in big picture mode. Haven’t had any issues at all.

Because people need something to be enraged about 24/7. That doesn’t mean that there isn’t plenty out there to be frustrated or upset about, but it’s just one more thing to add to the pile.

Also, fact checking. Nah let’s just scream into the void about stuff we know nothing about nor can we be bothered to actually check what is happening.

You can put the pumps in maintenance mode. I did it on accident once looking for the mute button. I held down one of the buttons for like 10 seconds and the pump went into maintenance mode. Just leave it like that lol.

Edit: Scratch that. It worked for less than 24 hours and went back to not connecting again.

To answer my own question, I hadn’t updated the firmware on my printer as it has been working fine so I just didn’t see a need to.

Went ahead and updated just in case and voila it started working.

Looks like Bambu is locking that functionality down behind the firmware version. As I didn’t see any notes in the update log pertaining to the camera so that’s the only thing that comes to mind.