Communication is explicitly a more than one person endeavor. If the other party isn’t willing or able to use signal, then sms might be the required option. Signal removed their SMS functionality from their app.

There are perfectly valid reasons to use Google messages instead of signal.

I’m surprised their website works and uses web standards and they didn’t just NACK everything about HTML and go off and do their own thing.

The point of a terminal like this isn’t necessarily to have more features. I have the tabs turned off (I also just use tmux). The point is to render smoothly and look/feel nice.

Some people would rather spend a lot of money on a nice pen. It still is just a pen that writes. No additional features over a 25 cent Bic pen. But the smoothness of the writing, the hand feel, consistency of line thickness, etc… to some people that matters. No extra features, it just looks and feels a bit better… But if all you are doing is writing a grocery list, you may not care. And if you don’t care, you aren’t wrong. This just doesn’t apply to you. If you don’t have a reason, you don’t need to find one. It’s just not applicable.

But some people do care. They do have a reason. And they are also not wrong to care. Their reasons just may not apply to you because you have different workloads or priorities (or maybe they do, and you just haven’t realized that it’s a thing you care about)

I think this just happens to fall under the category of “some people care about milliseconds of rendering time, and some people don’t.” I don’t know if the GPU acceleration has anything to do with it, but this terminal emulator also has really good font rendering.

If you are happy with your current terminal emulator, continue using it. If you heavily use your terminal emulator for a lot of things and in some things you’ve found that it stutters a bit, and you wished it was a bit smoother, get a GPU accelerated terminal emulator.

And secret bonus option: Even if you are happy with your current terminal emulator, give it a try anyway. Ghostty has a “zero configuration” policy where their goal is for most people to never need to configure anything. Sane defaults. It’s a good out of the box experience. Give it a few test drives, and if you’re still perplexed about why you should care, then maybe it’s just not for you and you can switch back. If you go “that was pretty smooth, i dont have a reason to switch back” then maybe you’ll think about it differently.

I was using alacritty. Ghostty feels snappy like you said. I dont know if it’s “noticeably” faster in any meaningful way. but the out of the box config settings make the font rendering look much nicer than I had set up for alacritty.

I told myself “I’ll use this for a while” as well but then realized… I don’t actually have a reason to change to anything else. It gets the job done. So until some other new shiny thing comes along, this is probably where I stay for a while.

Some games can detect if they are running a VM and block that as part of their anticheat. You may not be able to get roblox or fortnite running in a windows VM.

Some games just flat out require actual Windows, so your options are “Have an actual Windows drive/partition” or “Just don’t play those games”

The cofounder of sticker mule went real hard on trump support this past year so I’ve just done without stickers.

Which version of of SDDM (and presumably KDE) are you using?

One of the comments one of those threads you linked points out that the bugs you’re sharing are for has changed.

The components have been reworked since the button was disabled so maybe that helped. It used to be a PlasmaComponents2.TextField, now it’s a PlasmaExtras.PasswordField.

PlasmaExtras.PasswordField has the button enabled! However, the implementation in the theme explicitly disables it.

If you open up /usr/share/sddm/themes/breeze/Login.qml and scroll down to line 106. You’ll see rightActions: [] – this bit of code basically overrides the default behavior. It says "normally you have some actions here, but instead use this list, but [] is an empty list.

So if you just comment that line out by adding // to the front of it… Everything should just work, since it will then revert back to using the built in value.

However, the reason this was removed in the first place is in a comment on line 105: // Disable reveal password action because SDDM does not have the breeze icon set loaded

If the icon set fails to load for whatever reason (if youre using a custom icon theme or something, i dunno why it might not be loaded), the button will fail to load again.

You can test drive the SDDM lockscreen by running sddm-greeter-qt6 --test-mode --theme /usr/share/sddm/themes/breeze/ from the terminal.

And this all assumes that you’re using the default breeze theme. If you are trying to use a different theme, not sure if any of this applies.

https://wiki.lineageos.org/devices/beyond1lte/

I just recently got rid of my oneplus 5 because the volume button stopped working. So I understand the motivation. But LineageOS has Android 14 running on the S10 and its very possible that when they release an Android 15 version, they also support the S10

The archinstall script has a list of “profiles” that you can select from (custom, desktop, minimal, server, tailored, xorg)… And if you select “desktop” it will prompt you which DE or WM you want to install. (awesome, bspwm, budgie, cinnamon, cosmic, cutiefish, deepin, enlightment, gnome, hyprland, i3, lxqt, mate, plasma, qtile, sway, xfce4).

By the time you’re done with the archinstall script, you basically have a fully functioning arch (ive never used the script seriously, so I have no idea what all remains not set up doing this).

The main difference between Arch and Ubuntu in this regard, is that if you want to run KDE Plasma, you download the common Arch ISO, and select Plasma at installation time. Compared to Ubuntu where you would download the “Kubuntu” spin, so you are selecting Plasma when you acquire the ISO in the first place.

There is no “default” arch DE, so when you install Arch, there is a lot of decisions to make (and you may not know how to make those decisions if its your first distro), whereas Ubuntu makes a lot of decisions for you, so you have to answer no questions to get set up (but you may be set up in a way you weren’t expecting). In this regard, Arch really does just feel like building a PC from parts, you just have to pick all the parts. Ubuntu is more like buying a pre-built.

The “start button” is the kde plasma logo. So this would be Linux of some sort (makes sense given the community and what OP has said) and not windows

The question is just whether OP is using steamOS that comes on the deck (and uses KDE plasma for desktop mode) or if they have installed a different distro that fits the desktop use case a bit better.

I disagree with your definition of “killed Linux gaming.” It killed native Linux development perhaps. But using Linux for gaming is more viable than ever thanks to Valve. They single handedly boosted Linux gaming, if anything.

And they also offer more than the competition. For a while there games on EGS were just telling people to get support on steam forums because epic had nothing for supporting games they sold. Steam has forums, screenshot storage, achievements, remote play, friends lists, a shopping cart (🙄) and is adding new features like clips. I’m not using steam because it’s a monopoly, I’m using it because it’s a better platform.

You’re right. There are multiple definitions of the word stable, and “unchanging” is a valid one of them.

It’s just that every where else I’ve seen it in computing, it refers to a build of something being not-crashy enough to actually ship. “Can’t be knocked over” sort of stability. And everyone I’ve ever talked to outside of Lemmy has assumed that was what “stable” meant to Debian. but it doesn’t. It just means “versions won’t change so you won’t have version compatibility issues, but you’ll also be left with several month to year old software that wasn’t even up to date when this version released, but at least you don’t have to think about the compatibility issues!”

Debian aims for rock solid stability

To be clear, Debian “stability” refers to “unchanging packages”, not “doesn’t crash.” Debian would rather ship a known bug for a year than update the package if it’s not explicitly a security bug (and then only certain packages).

So if you have a crash in Debian, you will always have that crash until the next version of debian a year or so from now. That’s not what I’d consider “stable” but rather “consistent”

From the neovim 0.10 changelog:

‘termguicolors’ is enabled by default when Nvim is able to determine that the host terminal emulator supports 24-bit color.

So for me, i previously had vim.cmd.hi 'Normal ctermbg=none' as the method for disabling the background. But now, nvim was deciding to use gui colors for the terminal, and I was only setting terminal background to none.

The options are:

• vim.cmd.hi 'Normal ctermbg=none guibg=none' (also none out the gui bg)
• vim.cmd.hi 'Normal bg=none' (flat unconditional bg none)
• vim.opt.termguicolors = false (just disable the now enabled by default function to go back to terminal colors)

I had to SSH into a server for dev work at a previous job. And vim was the obvious best answer for “IDE like” experience in a terminal. I needed more power than nano.

And then vim stalled in development. Neovim was created in response to that, and it had new shiny features (many of which vim also has now), that caught my eye (async tasks were added to neovim before vim).

So I was a vim user out of necessity and I switched to neovim to chase new shiny things, and have found 0 reason to go back.