Yeah, CTS and RTS is useful for the module since you may overflow the module buffer (instead of the module overflowing your UART buffer). With proper HW flow control, hopefully your device UART respects the signal and pauses the tx until it is clear again without you having to code the pause yourselves. It can happen when the GSM bandwidth is lower than the UART bandwidth.

The module suddenly talking should also be handled by your device UART gracefully. When your rx buffer is full for whatever reason (not reading it for a long time?), the module won't be sending anymore data until you read your rx buffer. Theoretically, no data should be lost that way.

Yes, sounds about right. For general purpose decoupling that is a good value. Make sure to place it as close to the IC as possible. A longer path will add more "noise" to the system. Do read more about the capacitor type too since it can matter a lot. I suggest looking at Phil's Lab video on YouTube to learn more about this stuff

Nothing comes to mind. DRM literally means digital rights management and unless you wanted to be petty, like blocking a certain person from using your app, then DRM for something free is not something that I can think of a use case for.

What I mean by that is, this is just an API/SDK for app developers to use. Google does not enforce the use of such things. Much like steam does not force the use of their drm for example (please note the difference between the marketplace and the drm). App developers can always choose how they make and distribute their app.

I think a better solution is to truly emulate what really happens in the real world via peer to peer networking, and appointing / trusting certain individual as an admin/moderator for the node. That way a node can choose to become independent or have a quorum system or fully trust a single other node. That is my idea anyway, I haven't dug much deeper into this idea.

I dig it. Do you install the theme from freedesktop/plasma theme store or is it distro specific? I want to try it out too but I have never tried to theme that extreme before

I love the wording that you use

Yep, the problem with the compatibility layer is that a game can be very particular about the version too.

You're very welcome. This is after all, the essence of Arch. Now you know what is happening and why HDR is not yet widespread on other linux. On the other hand, you get to experience HDR gaming when other distros may not yet support it.

I can confirm that I do have the same issue regarding brightness. However, I never tried to investigate further as my mechanical keyboard has a fn keys to adjust brightness (fn + f1/f2) so I don't need to open settings to wiggle the slider. I can understand that it can be an issue for others. I suggest reading more regarding display and monitor. If all else fails, try asking the forum. I think it is DE specific (because wayland).

Gay field... A word I never imagined will encounter in my life

I am sorry but this is too funny. "If I have a dollar for every time I accidentally drive into a tornado I'd have $2. Which isn't much, but it's weird that it happened twice"

I think technically, the source should be the native format of whatever image manipulation program that you use. For vector graphics, there is svg format but the native editor is still preferable. Otherwise, whoever gets the end copy cannot easily modify or reproduce it, only copy it. But it of course depends on the definition of "easy" and a lot of other factors. Licensing is hard and it is because I am not a lawyer.

If you are fine with the older office suite (2019 I believe), there is a codeweaver program called crossover. They are the teams that make WINE a reality and they have a one version license so you can own it forever. Or yeah, you can also use VM.