[-] leopold@lemmy.kde.social 1 points 5 hours ago* (last edited 5 hours ago)

Unless they changed it, mobile Firefox is locked to a limited set of extensions unless you:

  1. Use Nightly.
  2. Create a Mozilla account.
  3. Log in to that account on the Add-Ons site and create an add-on collection with all the extensions you want to install.
  4. Set that collection as your source of add-ons in the Firefox settings.

You're also unable to use about:config unless you're using Nightly (or maybe Beta). So Nightly is really the only version worth using since it doesn't have nearly as many artificial restrictions as the stable version does. This is also true to a lesser extent on desktop where you have to use Nightly to install unsigned extensions.

You also can't open any offline HTML files for whatever reason and on devices with very little RAM (like 2GB) Firefox isn't viable, but Chrome-based browsers work mostly fine. Firefox is still the best mobile browser though, mostly because it supports extensions at all.

[-] leopold@lemmy.kde.social 3 points 5 hours ago

I'm surprised you could even run a Linux distro with X11 and KDE1 on 8MB of RAM.

[-] leopold@lemmy.kde.social 2 points 6 hours ago* (last edited 5 hours ago)

Qt1 came with two default themes. One of them mimicked Win95 and the other mimicked Motif. KDE1 defaulted to the former in order to look more familiar. To this day, the "Windows 9x" theme still ships with Qt and can be selected on any Plasma 6 install. Starting with KDE2 they started using their own custom themes for everything, tho.

GNOME 1 actually looked very similar, which isn't surprising because its main goal at that point was to offer a replacement for KDE that didn't depend on then-proprietary Qt. GNOME 2 and KDE 2 is when they really started building a distinct identity.

15
[-] leopold@lemmy.kde.social 6 points 6 days ago

Yeah, I mean Google caring about Linux isn't exactly breaking news. We knew that already. Android and ChromeOS both exist and as web company they kinda have to care about the OS that by and large runs the web. But this is Phoronix and they'll make articles about anything as long as they think as it'll get engagement. "Chromium" and "Wayland" are pretty good buzzwords as far as that goes, thus this article. My point is more so that maybe it isn't productive to have every acknowledgment of Chromium's continued existence be overwhelmingly negative regardless of context.

[-] leopold@lemmy.kde.social 14 points 6 days ago

This isn't something to complain about, IMO. Chromium is a popular app and it is a good thing to see work on supporting FDO protocols and improving Wayland support. I prefer Firefox myself, but it's nice that Linux support isn't just an afterthought for Google either and more importantly it trickles down to the countless apps on Linux that depend on Chromium in some form (usually through Electron). I personally use several, including but not limited to Slack, Discord, r2modman and VSCodium.

[-] leopold@lemmy.kde.social 3 points 6 days ago* (last edited 6 days ago)

Generations VI, VII and VIII all had fewer than 100 new Pokemon.

[-] leopold@lemmy.kde.social 1 points 1 week ago

I see. Will avoid, then. I don't like lucid dreaming, always wake up right away. Whenever I notice I'm dreaming it becomes hard not to notice that I'm in my bed and that I can feel my covers and by that point it's all over, so whenever I notice I'm dreaming I just cut the crap and open my eyes for a couple of seconds to wake myself up and then close them again so I can get back to proper sleep.

[-] leopold@lemmy.kde.social 4 points 2 weeks ago* (last edited 2 weeks ago)

Is this really useful? Like, is this something people ever need to do? I don't do lucid dreams very often, but the rare times a dream has lead me to the thought of "hold on, am I dreaming?" were basically immediately answered by just, uh, vibes, I guess? Like, it's always just been instantly obvious that I'm dreaming the moment I'd start questioning it, no tests necessary. At worst I might have to try to remember what I did the day before and what I was supposed to be doing that day and see if that is at all compatible with the scenario I'm dreaming about, which it usually isn't.

[-] leopold@lemmy.kde.social 6 points 2 weeks ago

Why do you believe a "nutrition brick" would be at all more appetizing than the things described in OP?

[-] leopold@lemmy.kde.social 4 points 2 weeks ago

Esperanto has grammatical gender.

[-] leopold@lemmy.kde.social 19 points 2 weeks ago* (last edited 2 weeks ago)

Do you... not know how multi-licensing works? You can use the project's code under the terms of whichever license you prefer, you don't use all three at once. Simply putting the AGPLv3 does remove unfair restrictions, because it means you don't have to use either of the proprietary licenses the project was previously only available under.

[-] leopold@lemmy.kde.social 12 points 2 weeks ago

I don't follow. ElasticSearch was only available under proprietary source-available licenses. Now, it's also available under the AGPL, which is open source, meaning ElasticSearch is now open source software. What part of this is deceptive or contradictory?

27
KStars 3.7.2 Released (knro.blogspot.com)
20
20
Kate and OrgMode (akselmo.dev)
29
Release of KDE Stopmotion 0.8.7 (gruenich.blogspot.com)
13
26
39
103
submitted 5 months ago* (last edited 5 months ago) by leopold@lemmy.kde.social to c/kde@lemmy.kde.social

Amarok was KDE's flagship music player during the KDE3 and Plasma 4 days. For Plasma 5, a new music player called Elisa was created with Kirigami which is the current KDE flagship music player. The last full release of Amarok was 2.9.0 in 2018, still targeting Qt4. A Plasma 5 port was started with the intention of being released as Amarok 3.0, but despite a usable alpha 2.9.71 release in 2021, the full 3.0 release was never completed. Outside of the occasional odd pull request, the project was essentially dead and was listed as unmaintained by apps.kde.org.

Two weeks ago, occasional contributor Tuomas Nurmi, author of over a third of these pull requests, made a push to become an Amarok maintainer, starting this thread in the mailing list: https://mail.kde.org/pipermail/amarok-devel/2024-March/014748.html

In the thread, Tuomas expresses his desire to revive Amarok. He believes a second alpha for 3.0 can be released in mid-April and a full Plasma 6 port could be completed within 2024 after the release of 3.0. Tuomas has since created a fair amount of merges and fixes in preparation for 3.0 and has shown no sign of stopping.

This is very exciting news. For many, Elisa isn't a satisfying replacement for Amarok. It simply doesn't come close to matching Amarok's power and features. It also has the drawback of being a convergent application, meaning compromises have to be made to make the interface work well on smartphones.

It's also victim to the many drawbacks of Kirigami. Theming is worse since Plasma has to convert QtWidget themes to QtQuick themes, which works great for Breeze, but meh for everything else. There is no good equivalent for KStandardAction/QAction, KHamburgerMenu or KStandardShortcut. Any Kirigami app that wants customizable toolbars and shortcuts need to go out of their way to implement them, while QtWidgets apps just get them for free. You also don't have a good QDockWidget equivalent that I know of. Apps that do bother to reimplement some of these features (Haruna is the only one I know of) still don't have toolbar customization to nearly the same extent QtWidgets apps do. Most Kirigami apps don't bother with this at all and lose a lot of customizability in the process. Elisa is not Haruna, tho. There is no shortcut customization, there is no toolbar to customize and that hamburger menu can't be turned into a menubar.

For years, the solution was Strawberry, a fork of Amarok still under active development. Thing is, Strawberry is a fork of Clementine, itself a fork of Amarok 1.4. That's old. That's 2008 Amarok, not 2018 Amarok. Clementine had its first release in 2010, when Amarok was still going strong. It was for good reason, Amarok 2.0 introduced a very divisive redesign of the interface, which prompted a fork. But this means 2.0+ Amarok and Strawberry are actually very different beasts. For those who were using Amarok 2.9, switching to Strawberry meant switching to a new music player, making it far from an ideal successor. So I'm very much excited for the return of Amarok, the best music player KDE has had.

26
Haruna 1.0.2 (haruna.kde.org)
13
Kile 2.9.95 / 3.0 beta 4 released (gruenich.blogspot.com)
27
Breeze Icon Update March 16, 2024 (anditosan.wordpress.com)
view more: next ›

leopold

joined 9 months ago