• 1 Post
  • 19 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle
  • Other stuffis not part of OpenRGB and never will be. Maybe you should have a loook at the project yourself, mainly read the contribution document.

    What is your issue? Avoiding fragmentation? Yeah me to.

    Currently,I do want to control my mouse, I need a different software that collides work OpenRGB.

    This is not fixable by trying to force stuff into OpenRGB the maintainer clearly does not want (he said so).

    After we have a working lib, with at least feature parity, I will try to convince the current maintainer of OpenRGB to outsource the device handling, and focus on the features he wants to build.

    EDIT and I don’t want to compete with OpenRGB, I want to focus the currently fragmented world of Linux peripheral development in a singular place, so every tool can use it. Ad a library, not a GUI application that just is another project that will die because it gets unmaintanable.

    So, please, have a good look at the contribution documentation and the bug tracker. Look for yourself, or try to introduce macro support or other stuff into this project. I have done so in the past.

    And to be clear: If the author and maintainer says he don’t want to have this feature, I completely understand.


  • This will not be a fork of OpenRGB. While I plan to take a huge chunk of it (the reversed generiert device protocols) the library itself, is all written from scratch.

    And, as mentioned, OpenRGB has issues. Besides the listed, technical, issues it has also design and maintenance issues:

    While OpenRGB heavily depends on Qt, and is written in C++, ur is full of plain C constructs. This is intentional, have a look at the README.md. raw pointer juggling, lifetime issues (therefore, segfaults) and most importantly:

    Making it a dependency would not aolfe any of the feature issues. A device, provided by OpenRGB, still has no support for macros, OpenRGB does all the device communication, so no way to add it.





  • I have to answer to this post directly… First of all: I am a member of the European free software foundation. I am since over 10 years.

    Using those distributions is, sadly, a security risk!

    Everybody must be absolutely clear about the fact that CPU microcode updates are property blobs, and therefore removed by those projects.

    This means: Your CPU runs with only the build in firmware and is most likely vulnerable against many CPU level attacks. CPU bugs can only be fixed with microcode , and if you drop those from the systems you leave the systems vulnerable.

    Full free software distributions are a important, but very esoteric.

    OP claims even the kernel itself is non free software. So let me just cite the kernel archive

    Is Linux Kernel Free Software?

    Linux kernel is released under the terms of GNU GPL version 2 and is therefore Free Software as defined by the Free Software Foundation.

    I heard that Linux ships with non-free “blobs”

    Before many devices are able to communicate with the OS, they must first be initialized with the “firmware” provided by the device manufacturer. This firmware is not part of Linux and isn’t “executed” by the kernel – it is merely uploaded to the device during the driver initialization stage.

    While some firmware images are built from free software, a large subset of it is only available for redistribution in binary-only form. To avoid any licensing confusion, firmware blobs were moved from the main Linux tree into a separate repository called linux-firmware.

    It is possible to use Linux without any non-free firmware binaries, but usually at the cost of rendering a lot of hardware inoperable. Furthermore, many devices that do not require a firmware blob during driver initialization simply already come with non-free firmware preinstalled on them. If your goal is to run a 100% free-as-in-freedom setup, you will often need to go a lot further than just avoiding loadable binary-only firmware blobs.

    https://www.kernel.org/faq.html






  • I don’t get what?

    There is a reason for the naming hardware, firmware, software.

    HARD, FIRM, SOFT.

    No, hardware das not bekomme Software just because it has firmware.

    And yes it would love to see free firmware.

    Look at CPU microcode. It is used to fix security issues in hardware. Without it you are vulnerable. Not using the property firmware blob to update the microcode is a very very bad idea. Does that make the CPU software…



  • What a bunch of bullshit.

    Linux, first of all, is the kernel. Linux is GPL and always free.

    And userspace zurück itself is about 90% free.

    Of course, you can choose a 100% free os, then make sure you use a free bios and only open hardware CPU and Mainboard and memory! 09 This argument is esoteric. I am an FSF member, but I use Steam on Gentoo.

    The idea behind such distro lists is to show how hard it still is to provide a really 100% open source distro.

    Let me remind you, what is non free in in most systems:

    • CPU microcode!
    • GPU Firmware
    • Wifi / BT / Ethernet firmware
    • Media Codecs

    Stuff most users need!

    And what the fuck is I distro locking me in? I can switch my distro between boots without fucking loosing any data or configs, I can choose what to install. I can install stuff from source. How can you even try to compare this with Microsofts property black box?

    Because you can not see what the microcode blob does with your CPU? The CPU you can not inspect also? Or the GPU? Or the BIOS?








  • There us so much wrong with this article. From installing a fucking browser via flatpack, over ignoring the fact that office 365 is a thing to the fact that there are alternatives to Adobe.

    Sure, not everything is perfect right now, and people have to learn new stuff.

    I have migrated multiple people to fedora in the last two years. And guess what, regardless of type or age of user, they had no troubles with it to this day. They use gimp, play, have browsers with password managers, and write office documents. Yes. MS office.

    Articles like this are one reason why people hesitate to make the switch. Doompainting, that’s all it is.

    And what the hell are you talking about vrr? Kde, sway and hyperland support it for years now under wayland. Gnome still does not have it, but that is gnome.

    And if more distributions would not per default use gnome, such misconceptions wouldn’t exist in the first place.