Yeah, let’s not mention Gnome breaking every peace of itself every update

This is not my experience.

It's the fault of copyright. Restricting what shows you can stream to your users instead of, for example, being required to pay a royalty, inevitably leads to this situation. Netflix being the sole company allowed to stream every show and film would result in a monopoly that would be bad for everyone as they progressively sought to increase profits year over year. One company having all that power would not be a good thing for anyone, including content holders.

The solution is simple: every streaming service should be allowed to stream every show/film in every country. Then, piracy can only compete on price. That requires significant copyright reform, however, and is very unlikely to happen.

There's Lightworks, too, although it's geared toward the editing process. I like it, though, and have been able to make it work for general video editing. The color correction tools are better than Kdenlive and not as good as DaVinci Resolve, but unlike Resolve, it will decode/encode H.264 and AAC. It's powerful without being quite as overwhelming as Resolve can be for newbies. There's no advanced setup involved unlike Resolve. The playback is responsive even with 4K footage. Kdenlive is great too, if you don't need more advanced features or are working with a lot of 4K footage.

Aussies tend to be quite direct. It's basically our natural state. I get how it can be perceived as hostile, but I don't actually think Brodie is very abrasive. He seems like a pretty relaxed guy.

What non-AGPL software were you hoping to be compatible with fediverse software? Or am I misunderstanding why you want non-AGPL software?

I also had a pretty terrible experience with Fedora KDE not too long ago. Too many issues to count. In the end, I couldn't start a Plasma session from the display manager anymore so I gave up.

I really wanted to like Fedora, but...well, Fedora does not seem to like me. My experience on Arch KDE has been great. Like night and day. Still a few small bugs, but annoyances and not showstoppers. My experience with GNOME on Arch has been fantastic. Only one program was broken in GNOME that isn't in KDE. It makes me wonder why I ever tried to leave...

Thanks for posting this! It was a long read, and while I was familiar with a lot of the history, I learned some new things.

As I've said before:

I would support Red Hat if they only made their free software offerings available to paying customers. I think this is how a free software company should work. Most free software is not sustainable today, and it would be nice if Red Hat could be a good example of how to build a successful free software company.

Even if Red Hat terminates the contracts of customers who share the sources, this wouldn’t be against the GPL, but I think it would be nasty to scare your customers into not exercising their granted freedoms under the GPL.

My position is that I don’t think this is how a free software company should behave, but I’ll refrain from voicing any further opinions until Red Hat actually terminates a customer’s contract for redistribution.

This is good advice. For example, here's a tricky one: https://github.com/IanLunn/Hover/blob/master/license.txt

Hover.css is made available under a free personal/open source or paid commercial licenses depending on your requirements.

Would you need to pay Ian Lunn Design to incorporate the library into your portfolio website? It's used for a commercial purpose technically, but you're not selling the website to a client. This is a source-available license, rather than a free software license. A free software license permits you to use the software for anything, with the only obligations usually being around keeping copyright notices intact and licensing your code in a certain way.

Generally, free software licenses are simpler and you'll usually be fine so long as you keep your code available under the same terms. Of course, things get a bit tricky when combining incompatible free software licenses...

Compatibility is important if you want to combine software with two different licenses into one major work.

Generally speaking, most software on Github tends to be licensed under a few free software licenses, which are interoperable with each other:

• MIT License
• GPL, LGPL, and AGPL Licenses, which have one major difference in obligations between them
• ISC License
• Apache 2.0 License
• Mozilla 2.0 Public License

However, when you combine MIT and GPL together, you may be obligated to distribute any changes you make to the MIT-licensed portion, depending on how strongly it's associated with the GPL portion. This is because the GPL is copyleft—that is, it requires you to provide anyone you transmit the binary form of the software to the associated sources if they ask for them. The MIT license does not require this obligation.

None of this really matters for a website, though, because you're not transmitting the software; you are instead providing a service. Do keep an eye out for the AGPL, because this one applies even with server-side software interacting with clients.

I think writefreesoftware does a good job of explaining licensing for developers in simpler terms than the GNU Project: https://writefreesoftware.org/learn/licenses/

Sorry for the length...it's kind of a complex topic.

GIMP is currently missing non-destructive editing (a rather core feature), but that's something they're aiming to fix in 3.2. I don't know when that'll be here, but that will be a good day for GIMP.

You might have better luck with Affinity Photo—it doesn't really work well through Wine yet, but it's getting there: https://forum.affinity.serif.com/index.php?/topic/182758-affinity-suite-v204-on-linux-wine/

I personally use Affinity Photo on macOS and I'm really happy with it. I like it more than Photoshop, actually. Fair warning that it will rasterize all your text layers in .PSD files, so you'd want to be using only .afphoto files, but it's impressive how good the .PSD support is otherwise. So, give it a year or two, and Affinity Photo might be in good shape in Wine! I mean, I can hope.

Thankfully, it appears this is no longer necessary in most cases since 2022: https://wiki.archlinux.org/title/Pacman/Package_signing#Upgrade_system_regularly

Though, it's still worthwhile doing it for computers you don't power on for most of the year, as the service likely hasn't had a chance to run.

Oh, cool! Since when? I always thought that was something the user shouldn't need to remember and that Pacman should automatically prioritize it.

This is exactly why I love making these kinds of comments. Someone always comes along to teach me something new!

I actually do remember hearing about this somewhere, but even though I have their blog/updates in my RSS reader, they never officially mentioned this before this user brought it up—maybe in their Discord server? Thanks for pointing this out! I can imagine they really wanted to get away from Bing after the price surge, as that was only a signal of more to come. Duckduckgo seems to be paying for that with the massive increase in ads.

However, it is still disconcerting the degree to which Kagi is hugely reliant on Google. Doesn't change any of the positive aspects about Kagi, though.