Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)LE
Posts
46
Comments
329
Joined
2 yr. ago

  • OnlyOffice is not based on LibreOffice. There might be a point in joining forces with OpenOffice if OpenOffice actually had forces to join with, but it doesn't because it is a dead project.

  • Indeed, but GNOME is big enough to veto against anything they dislike getting into Wayland. And indeed, TWMs were brought up as a big reason why CSD sucks; window decorations primarily contain controls for the window manager and the form these controls should take depends entirely on the nature of the window manager, therefore the window manager should draw the controls. But GNOME doesn't want to perform the oh so difficult task of providing window controls to apps that don't provide their own under Wayland, so too bad.

  • Firefox and LibreOffice aren't part of KDE, but Kate and Okular are. So the fact only the former two support this feature indicates it's not from KDE. This should probably be supported by KDE though (or by Qt? perhaps this should be done on the toolkit level rather than on the application level). Holding ctrl to multi-select is standard behaviour in a lot of applications and is quite useful. For what it's worth, Krita does support this, but you need to hold shift instead of ctrl.

  • The Foo is obviously from Foobar. Google translate says "fuyin" is "copy" in Chinese, which I guess could make sense since it's a copy of foobar2000. It also says "fooyin" is "I'm sorry" in Somali, which is probably a coincidence because that makes no sense.

    EDIT: One of the screenshots in the README is in Chinese so yeah that's probably it.

  • When I last tried it (around the time that article was posted, could've improved since), you needed to mess with gconf to enable the feature, which was for good reason because the compatibility was abysmal (ublock origin did not work and neither did dark reader or violentmonkey or really any extension I wanted to use).

  • It's even more bonkers than it sounds. If you look at the code locations for that KDE count, you'll see it also includes just about every KDE project. That's not just Plasma, that's hundreds of projects, including some really big ones like Krita, Kdenlive, Calligra, LabPlot, Kontact, Digikam and Plasma Mobile. Hell, it even includes KHTML/KJS, KDE's defunct web engine as well as the ancestor of WebKit and Blink. It even includes AngelFish and Falkon, KDE's current web browser frontends.

    Same deal with GNOME. It includes just about everything on GNOME's GitLab, even things that are merely hosted there without strictly being GNOME projects, like GIMP and GTK.

    And yet still they are both that far behind Chromium and Firefox. Modern web browsers are ludicrous.

  • Well, it is basically LibreJS logic applied to an entire distro, like your typical FSF-approved distro. It's a distro by free software extremists for free software extremists and no one else. It's is completely impractical for actual use. But really it's worse than the average FSF-approved distro. It takes things several steps further by removing many things that are 100% free software, but just subjectively disliked by the maintainers, including even the Linux-libre kernel, as the project is in the process of moving to an OpenBSD base. The OpenBSD people naturally want nothing to do with them, so I'm looking forward to seeing that play out.

  • is this flamebait? we really don't need this stale-ass debate revived for the millionth time. everything that had to be said has been said and no one is going to budge from their positions. there is nothing to be gained from reposting some old controversial 2021 blog post about this outside of more flaming. it's time to move on. this is a waste of everyone's time.

    if you're a developer, support themes if you want to support them, don't support them if you don't. if you're a user, use the apps you want to use. if you care about theming, use the apps that support it. if you don't, good for you. there doesn't need to be anything more to it.

  • VP9 is AV1's predecessor and VP8 is VP9's predecessor. Dunno what the “264K 360° Surround sound 3D VR” thing is about, but AV1 is a good general purpose video codec and I recommend using it, with Opus audio.

    EDIT: I should add, h264 and h265 are non-free because of software patents, for which there are licensing fees. There are free implementations and there always have been, but the extent to which these implementations can actually freely be used legally is limited by this. Cisco's OpenH264 is an exception, because there is a cap to the licensing fee and Cisco is already paying the max amount. This allows them to freely distribute binaries for their h264 implementation without having to pay additional licensing fees for every user. It's a clever loophole, but there are still limitations, namely that you have to be using Cisco's pre-built binaries. If you want to use the source code, you still need to pay for the licensing fee.

    Because patents last twenty years and the initial release of h264 was made in August 2004, the key h264 patents should all expire within the next few years, which will eliminate the problem. h265 however was introduced in 2013 and its patents still have a good decade left in them.