• 0 Posts
  • 179 Comments
Joined 3 years ago
cake
Cake day: July 22nd, 2023

help-circle














  • A good mobile alternative to Signal is Simplex, it works both on Android and GNU+Linux. It’s AGPLv3. You have it on F-Droid

    I have a Thinkpad X220 myself with Libreboot (coreboot distro). But if you do think that microcode updates is bad you can go for Canoeboot. Always check the chipset in order to know exactly what kind of me_cleaner you have to apply.

    Thinkpad X220 works out of the box with Linux-Libre (I use Guix). You probably will need a WiFi card that works with the free software kernel drivers, you can check h-node for hardware that works with free software drivers.

    The thing is that that kind of laptops aren’t too powerful. You could check more modern Thinkpads supported at Libreboot.

    There are also modern laptops from: System76, framework and Purism. Some support freesoftware more than others, but it’s a good resource. For example not all System 76 laptops have Open Source Bios and EC, most of them disable the ME though.

    The phone market is a bit different everything runs on SoC. So unless you go Purism phone or Pinephone. But they lack a lot. I would recommend using a custom de-googled Android like GrapheneOs, CalyxOS or LineageOS.

    **Since I’ve been there, take everything with calm. Change bit by bit, and don’t try to force yourself. **

    Note: There’s also Briar as a replacement for Signal, but the synching is between devices, so if the other is not connected… I prefer Simplex for now. I really like the way you share chats (since there are no IDs per se). I’ve been testing it out and it works well, you can even call and everything.

    Note2: Matrix is a bit shady since the only Matrix instance (public) is Matrix.org and for now their whole selling point is based on that, but we’ll see (I use it too though).



  • QT uses one or another, either GPLv3/LGPLv3/GPLv2 or privative. Poisoning open source? If you refer to the fact that they allow a closed source licence, yes I also dislike that. But how is GPLv3 poisoning anything? If you want to use and modify/contribute to the QT project then you have to maintain user freedoms unless you pay QT for their rights. In the end term, the user is always respected since contributions to base qt are always free software. With only a GPL licence then the developers would need to share source code for their distributions. The Multiple-Licence allows third party developers to gain “fully-paid-ownership” which allows them to close source it.

    Also since QT it’s allowed to be shiped with LGPL third party devs can close source their parts of code that link against QT.

    So it’s basically an interesting way of having a permissible licence while keeping the QT base fully libre.

    Probably you refer to the availability that open source philosophy gives. Yeah, that is the principal difference between libre software and open software. Open software advocates for fully openness for the sake of the developers no matter what they want to make later with it, libre software advocates for the source code of the end user.




  • Yeah, it depends on the specific licence clauses. AOSP uses Apache Licence 2.0 which is normally regarded as a free software licence but it also could be regarded as Open software as by the OSS definition.

    The problem with this licence is that it allows distribution of binaries based on the original source code without having to share the source or even changing the licence.

    This means that Google could effectively take the entire (some part of Google Android is already close sources) AOSP in the current state (with the contributions of thousand of individual developers) and use it to start developing a close source Android OS project. Since Google are the main developers of Android and they could shift OG Android into a closed environment that could be no longer compatible with the old one. Google also is the main provider of security fixes. Since phone manufacturera want to able to run Google Android (stock Android) this could make old Android versions (before privatization) incompatible with phones.

    For example let’s say that Google Android changes the main OS ABI or API. Then programs made for Google Android wouldn’t be compatible with other Android versions.

    This would basically make users decide or you stay with Google Android (close sourced) and you trust use because “do no evil ;)”. Or you stay with your free software versions of Android that are no longer compatible with current Android programs basically forcing you to have an OS that’s not able to run “common” programs, basically isolating you from the mainstream smart phone use cases like having banking apps, mainstream chat apps, etc.