Because I dont need to pay rent for my files and I don’t have to worry about AI and VCs trying invade my privacy.

Hence the groups having the ticket name related to the task I am working on. When the task closes I delete that group once I’ve ensured anything important for future context is documented and then I say goodbye with confidence.

I don’t bookmark things for work tasks, I log them in tickets or commit it to readme/code comments/team docs somewhere.

Edit: I should also note that my workflow uses Simple Tab Groups and not much of this new core feature.

Simple tab groups hides all other tabs and you switch groups via a dropdown. I usually only have 10-12 tabs open at once.

Agile and task reprioritization at work.

To many projects to work on at home.

Games.

The way they did it though… the tab group name cant be collapsed so it takes a lot of room. I find I’m still using task oriented groups from the Simple Tab Groups extension, and then using the new core groups feature as a way to group subtopics for that task.

And before you say “you must have a million tabs”… I used to have millions of tabs, but now i average less than 100 when I have a lot of tasks I need to balance, and I know what all of them are open for. So when I complete a task I delete the Simple Tab Group and say bye to all those tabs.

Mandrake was my first Linux OS.

The problem I see with this is that a Meta employee literally came out on Mastodon recently and revealed that non of these settings do anything and are false flags.

https://misskey.de/notes/a3ax4tqomg

Never mind, youtube faked me out. Looks like the new one will require a proxy

The deb version is a pointer to the snap in their repos. Nothings being replaced, it no longer exists. The deb version of Firefox in Ubuntu repos is a wrapper that installs snap and has no binaries in it. Has been for 3 years or so.

You don’t need special docks in KDE, its all configurable through the default desktop settings. You have enough knobs to make it look like anything.

In Plasma 6 there are a crazy number of ways to skin and change the look.

This video was a good way for me to learn some of the basics. https://youtu.be/R6C-RNhHMrE

KDEs vision is letting users have the experience they want. You can have a vision without limiting configurability and cramming bad UX down the pipe to your users.

I used Gnome Shell 3 for 4 years before giving up on it and going to KDE.

The huge differentiator is that KDE may look like windows OOTB on most distros, but if you want you can easily make it look like Gnome, Mac, Unity… whatever. The panels and menus are infinitely configurable.

And that is why this meme is dead on the money. I’ve come to hate dev teams that have “visions” that they cram down users throats regardless of the experience. And the irony is that Gnome 2 used to be much more configurable than older KDE versions.

I did a wtf at dude 4 in frame 3 until I realized he was getting punched and not… well… if you don’t see it maybe I’m just net-warped.

Hey no worries, I dunno why I even called that out. Lack of sleep due to back pain and responding to posts at 2am I guess

That’s some shitty ‘hacking’…

But what makes these shell commands ‘bash’ exactly? Seems like this could be a half-dozen shells.

Also… why are ‘hackers’ always using a shell in some gui program?

I missed this, someone have the TL;DR for the clueless?

I feel the same way about having to use Mac for work and going back to a Linux PC at the end of the day. God damn I hate Mac’s UX. From the entire UI, to the CMD key, to the fact that END functions as PGDN and goes to and of page instead of end of line.

It’s getting good. I keep it as an alternative to OSMAnd, but find that Organic maps are harder to read and missing a lot of detail compared to OSMAnd.

Oh that’s what happened to RieserFS

Same. But I still keep critical paper work in a fireproof safe, just in case.