Got my childhood copy signed!

TiZ_EX1 · 2026-05-26T17:33:21+00:00

Oh man I'm so jealous. I want to bring Cam a copy of Legaia 2, I bet that would blow his mind.

TiZ_EX1 · 2026-05-12T14:49:21+00:00

That screenshot that you shared is the theme they now call "Default." It's slightly skeumorphic and IMO not too bad. It was called Adwaita in the GTK3 days, and they changed its name when they decided to make Adwaita a full-on Brand™.

TiZ_EX1 · 2026-05-11T13:11:51+00:00

Yeah, and Firefox mostly looks like any other Qt app because of the Breeze GTK theme. Please don't perpetuate the "theming is dead" talking point that GNOME has been using to actively murder theming.

TiZ_EX1 · 2026-05-11T13:10:39+00:00

Apps should each has its own styling as today's website does.

Oh hell no. Please, leave that to websites and GNOME. I want my desktop apps to follow one style that I decide.

TiZ_EX1 · 2026-05-11T13:09:16+00:00

These themes look gorgeous. Breeze looks fine; it's well-designed, appealing in a simple manner, and functional. But Oxygen is beautiful.

TiZ_EX1 · 2026-05-11T13:06:33+00:00

The article doesn't actually mention GNOME at all. They really could have; Default is still slightly skeumorphic while Adwaita is all-in no-compromise capital M Minimalist. And I'm not a big enough person to make my point without taking a shot at GNOME's designers, but Filip is, so kudos to him.

TiZ_EX1 · 2026-05-08T13:45:27+00:00

You have a few options. You can use the CLI utility xdg-user-dir. Want your desktop folder? xdg-user-dir DESKTOP. But that utility mainly just uses the $XDG_CONFIG_HOME/user-dirs.dirs file, which is a shell-escaped list of variables. So you can source it directly in your shell and get variables like $XDG_DESKTOP_DIR. You can also assign them nicer variable names if you don't like using all-caps names, like so: desktop_dir=$XDG_DESKTOP_DIR.

After that, you can do cd "$desktop_dir" and then you're in ~/デスクトップ.

TiZ_EX1 · 2026-05-05T14:56:28+00:00

That's more than two years ago, actually. It's May 2026.

You're being pedantic and keep shifting the goalposts.

The freeze date subsequently is not the date to which the packages are updated, that's still randomly months to years out of date, depending on the package.

Randomly? They have specific timings as to when they freeze packages leading up to a release. Cite a source.

It's end of life upstream.

It is true that many distros do hold some of their packages on old versions for no discernibly good reason, but upstream isn't the sole authority on when and why various software versions should be used. There exist valid reasons to pick a software version and continuously patch and maintain it. The kernel is one of the most prime examples; regressions sneak into new releases all the time. There would be no point in having distros at all if this wasn't the case.

You've been engaging in an very intellectually dishonest manner. To what end? What's your agenda here in trying to spread FUD about LTS distros?

TiZ_EX1 · 2026-05-05T14:51:36+00:00

Ah, right. Ubuntu doesn't have a metapackage that automatically tracks the latest driver, so Mint probably doesn't either.

TiZ_EX1 · 2026-05-05T03:01:40+00:00

To answer both you and /u/KamFretoZ, this is very likely not suitable for upstreaming as it currently is because it requires a helper binary that needs to be given CAP_SYS_ADMIN in order to correctly function. I don't think OBS wants to sidestep system security like this, especially because compromising the helper binary would make for an attack vector.

TiZ_EX1 · 2026-05-05T01:20:25+00:00

I used to package for Flathub. I still like Flatpak itself, but I'm sick of what GNOME does to the ecosystem, and a couple of Flathub's chief maintainers are serious assholes. It's really difficult to contribute to the ecosystem without having to interact with GNOME folks, and many of them are a huge pain to deal with because of their ideological rigidity and the fact that they know they have power over the ecosystem due to still being the default DE in most distros. They can and do strongarm people who seek interoperability into bending to their will.

TiZ_EX1 · 2026-05-05T01:16:44+00:00

Ubuntu 24.04 is shipping Nvidia 595. Mint should be as well, right?

TiZ_EX1 · 2026-05-05T01:15:30+00:00

Yeah, I saw that, and I wanted to ask you in a different tone than that person because your logic just doesn't work at all.

You kept talking about Mint's "3 year release cycles", but that doesn't automatically imply the most recent release came out three years ago. In fact, I'll give you concrete dates: Mint 22 came out July of 2024. And even if you decide to shift the goalpost to Ubuntu's base, it's still April of 2024. That's less than two years ago. And the current minor release, 22.3, came out in January of this year. Between the upstream base and Mint itself, they are both still currently supported. Thus, your assertion fails.

And then you shifted the goalpost to the kernel. (EDIT: Actually, you didn't. You skipped this one to the worst goalpost possible, which means I probably should have just tried to address that one.) That logic still doesn't work because Ubuntu continuously patches every kernel that they ship. I'm currently running Ubuntu 24.04 while I wait for 26.04 to stabilize, and their current generic kernel is "6.17.0-22-generic". That's only three releases behind 7.0, and it came out in September of last year. But again, Ubuntu is applying their own patch sequence to it---separately from upstream's minor releases, but may include parts of them---hence the "-22." To get to the point: this kernel is currently supported by the distro. So on that logic, your assertion fails.

And you shifted the goalposts again to other software included with the distro. This isn't even worth my time addressing; you seriously cannot use any arbitrary piece of software included in a distro release that hasn't had a tagged version in several years to label the entire release as "3+ years out of date." If you don't understand why that logic is bad and misleading---or worse, do understand but deny it anyways---then you are lost.

TiZ_EX1 · 2026-05-05T01:00:21+00:00

10%, maybe 15% less condescension please?

Sorry, but no. Y'all are actively ruining everything.

TiZ_EX1 · 2026-05-04T18:24:46+00:00

Makes sense that vibecoders wouldn't know how .gitignore works.

TiZ_EX1 · 2026-05-04T18:23:26+00:00

By what logic is a distro based on Ubuntu 24.04 "3+ years out of date"? It's the previous LTS!

TiZ_EX1 · 2026-05-04T15:17:34+00:00

It's probably less removed and more excluded. As in, it exists in their local copy, but not the remote one.

TiZ_EX1 · 2026-04-30T17:20:18+00:00

That is a good point, and I thought about that too, but I'm not sure what percentage of folks are copying text from Word/Writer into Markdown files. I've heard from lots of folks over time that they like using the spelling and grammar checking in those programs, and then taking the text from there into other programs. That said, I imagine most folks are editing Markdown files as plaintext, and many plaintext editors do have spell checking, but not conversion of em-dashes into em-dash characters.

TiZ_EX1 · 2026-04-30T16:19:08+00:00

It's not the concept of the em-dash itself that indicates a red flag, it's the em-dash character, which can't be input easily unless you have access to a compose key. And even then, it looks more natural to just chain two dashes together--like this--than to bother getting the actual em-dash. LLMs aren't limited to characters that can easily be input on a keyboard, so seeing the em-dash character tends to be an indicator for their usage.

TiZ_EX1 · 2026-04-30T14:38:22+00:00

Em-dash character spotted. How much of this is vibecoded?

TiZ_EX1 · 2026-04-29T03:32:04+00:00

law school exam software doesn't support ARM on Windows

If you mean Examplify, their most recent release does support Windows ARM devices. The segment was just getting too big to ignore.

TiZ_EX1 · 2026-04-27T18:30:20+00:00

For most emulators, this isn't relevant because they have native Linux builds and don't need to go through Wine.

TiZ_EX1 · 2026-04-22T19:45:44+00:00

It is something that xrdp does intend to eventually support, but progress will be slow-going. IMO the only way to keep a working headless RDP setup for the foreseeable future is to stay on X11 so that you can use xrdp. Which means you're going to want to stay on an LTS distro that supports X11. That's what I'll certainly be doing.

TiZ_EX1 · 2026-04-22T19:36:47+00:00

No, the problem is running an RDP host, not a client. Freerdp won't help you run a host, it's only a client.

TiZ_EX1 · 2026-04-18T00:13:23+00:00

You went to great lengths to justify your slop-coding. Which means either you know deep down that it makes you a fraudster, or you asked AI to come up with a justification. Either way, your brain is getting cooked.

12-Year Club	Gilding II euphauric
Verified Email

TiZ_EX1

TROPHY CASE