In that case, it's time for the average workers to sabotage the bossware. Let the leech class solve the problem they create.
The licenses alone are enough to ensure that the opposite happens.
I think assembly was easier back then. Some architectures still are. But many architectures like x86 got incredibly complicated.
So you hate flatpaks and not flathub in specific?
Most websites still use standard back ends with RSS support. Even static site generators also do it. The only difficulty is user discovery.
You never reach a phase when you can confidently say that you understand git. But it's certainly possible to go from "When something goes wrong, I just delete the repo and clone it again" to "Aha! Now I can deal with most of the issues".
Mine was when I realized that git commands come in two flavors. Those that deal with commits as snapshots (commit, checkout, switch, reset, etc) and those that deal with commits as changes/diffs/deltas (merge, rebase, cherrypick, revert, etc). (Note: This isn't about how git stores commits on disk). I believe that this is actually the main source of confusion for beginner and intermediate git users.
We don't ask for forums because we don't want features of Discord. We ask for forums because we want features that Discord does not offer:
- Ability to search the discussions from a web search engine
- Proper segregation of threads - a question followed by related replies (similar to github discussions, issues and PRs)
- Ability to back up the discussion history, so that it doesn't disappear if the server goes down.
- Ability to operate unimpeded if the silo operator decides to monetize the information by holding it hostage.
Note: Privacy is not what we need here. We need the solutions to open source problems to be public - especially, searchability.
I didn't advocate for IRC. I'm strongly on the side of forums. But in case you want to compare, IRC is still a better deal than Discord. IRC has loggers and searchable web archives where it matters. Discord on the other hand is holding the conversation hostage. Someday the closed nature of discord will come to bite. The honeymoon isn't going to last forever.
I don't completely agree with many of RMS' stances on sexual abuse. It often feels like he is a bit tone deaf in that regard. However, the cancel campaign against him was very much motivated and they twisted his words completely out of context in several cases. I'm not going to get into the tiresome argument of if he was right or not. But one thing I noticed back then was that many involved in the campaign had clear vested and conflicting interests with undisclosed financial motives. Watching it live, it was pretty clear that the campaign was sponsored by certain big names in the industry.
The anti-FSF campaign you mentioned and the anti-copyleft propaganda I mentioned shouldn't be seen in isolation. It might sound like a conspiracy theory, but there were clear indications of a long term corporate-funded smear campaign to attack the foundations of FOSS - a hit job, if you will. Too bad I didn't bother to save those back then. A lot of illuminating messages were forcefully deleted.
They really took advantage of the outrage mentality of common people. Meanwhile, people took the bait and went after the small fish while being completely oblivious to the big sharks feeding the outrage.
Stay away from google play if you can - forget buying from them. From logging you in without consent to requiring credit card for unlocking geo-locked app, Google play is a very scummy, anti-privacy malware.
- Lack of privacy
- Arbitrary cancel culture with no recourse
- Corruption and bloating of open standards like web
- Non consensual logins (android, chrome)
- Sabotage of federated services (email, xmpp)
- Suggestion of new tracking methods (like FLoC) when old tracking methods (like 3rd party cookies) are phased out
- Centralization of information flow (eg: AMP)
- Bait and switch tactics (like YouTube ads)
- Support for horrible laws (like illegitimate DMCA strikes)
- Locking down devices (with remote attestation, safetynet api, etc)
- Geolocking apps unnecessarily
- Invasive use of credit card information to prove location (why not just use GPS or cell info?)
- Incompatibility with open standards to achieve user lockins (eg: IMAP, caldav, carddav)
- Riding the open source wave with projects that don't behave like one (AOSP, chromium)
- Untrustworthiness when it comes to long term presence of services
technom
0 post score0 comment score
Nvidia is a mess on Linux in general, though it's gradually improving. They decided to neglect everything that the other GPU manufacturers and the community were doing and roll out their own buggy concepts.
This really isn't the fault of Mint. PopOS works with it just because its developers System76 also has a line of nvidia based hardware. However, as I said before, nvidia is slowly starting to implement the standards and situation on other distros like Mint will gradually improve.
Meanwhile, I'm curious. What hardware did you try Mint on?