That's not the worst possible scenario, I'd love to see the Snap Store completely replaced with decentralized FOSS alternatives. Any scenario in which the Snap Store takes market share from decentralized FOSS alternatives is considerably worse.

Also, who said I wouldn't use proprietary apps? I refuse to use Snap because Flatpak and other FOSS application packaging solutions that aren't locked to a store controlled by a single for-profit company already serve my needs. I don't have any objection to using proprietary apps that don't have alternatives that meet my needs.

Silly whataboutism. When there are multiple Linux package management solutions to choose from that are functional, decentralized, and fully FOSS, including ones that work across distros, switching to the proprietary Canonical-controlled Snap Store is moving backward for no good reason.

The Snap Store server is completely proprietary and fully controlled by Canonical.

Yes, Plasma 6 was the turning point for me, since it introduced pixel-perfect fractional scaling on Wayland for just about every application.

I was responding to a comment that claimed "he isn't on the project since last year". Based on his activity on social media, he is clearly still in the project.

That's dubious, since the "former" lead developer is still referring to the project with the pronoun "we" on social media.

Direct link to PDF of RCS Universal Profile specification

This PDF link can be found on a search engine. You can also fill out the form with fake information and a throwaway email to get the link, though you don't have to.

The RCS Universal Profile is a publicly available standard, but there is no FOSS client stack that implements the standard. Google restricts RCS support on Android to the proprietary Google Messages instead of making it part of the Android Open Source Project. Apple Messages and iOS are also proprietary.

The EU should use the Digital Markets Act to force Google and Apple to allow competing RCS clients on Android and iOS.

That's just the first thing that came to mind. Any product with consumable refills (razor blades, electric toothbrush heads, air/water filter replacements, etc.) would also work as an example.

Let's say you want to buy a printer from a retailer. The retailer also sells replacement ink cartridges, and so does the printer manufacturer. The manufacturer prefers that you buy the ink cartridges directly from them, because their margins are higher when they don't have to pay the retailer a cut.

To encourage customers to buy the cartridges directly from them, the manufacturer provides a link or QR code to their online ink cartridge store on the product box, printer manual, and another paper insert inside the box. The manufacturer might offer more competitive pricing than the retailer or some other enticement, like a coupon.

However, the retailer implements an anti-steering rule, preventing the printer manufacturer from providing a link or QR code to their online ink cartridge store on the product packaging, printer manual, or anything inside the box, as a requirement for the printer to appear on the retailer's shelves. (As a result of corporate consolidation, there is only one other retailer in the entire country.) This is the equivalent of what Apple is doing to apps in their App Store: preventing developers from disclosing that users can purchase subscriptions or other app-related digital goods on the developer's website.

Dell used to have pointing sticks (branded TrackStick or Dual Point) in some of their business laptops, but they removed them all in 2021. Lenovo is the last major laptop producer to use pointing sticks. Maybe System76 will come through?

PeerTube has a variety of third-party applications for Android, desktop, and a few other platforms.

The closest thing to Librewolf on Android is Mull. Keep in mind that some of the settings are different.

Here's the feature request for a TrackPoint on a Framework. Hope they change their mind, because a pointing stick is the most obvious use case for Framework 16's input modules.

This ThinkPad keyboard project for the Framework Laptop is worth keeping an eye on.

I still prefer Bitwarden because the server is source-available and most of the code is free and open source. There's also the FOSS Vaultwarden server fork that I can switch to at any time.

Proton Pass also using end-to-end encryption with FOSS clients is nice, but the server code is completely closed source.

I don't think that's the case. The v0.19.0 release notes say:

Instance Blocks for Users

Users can now block instances. Similar to community blocks, it means that any posts from communities which are hosted on that instance are hidden. However the block doesn’t affect users from the blocked instance, their posts and comments can still be seen normally in other communities.

Avast should not be recommended.

In late 2019, Avast browser extensions were found to collect user data, including browsing behavior and history, and send it to a remote server. The discovery led to the extensions of the Avast and AVG brands being temporarily removed from the Google Chrome, Firefox and Opera extension stores, however, they returned a short time later as there was no concrete evidence that demonstrated a breach of private data of the users.

In January 2020, a joint investigation by Motherboard and PCMag found that the Avast Antivirus and AVG AntiVirus Free version were collecting user data, which was being resold to personalize advertising through a subsidiary, Jumpshot. The leaked documents showed that Jumpshot offered to provide its customers with "Every search. Every click. On every site." from more than 100 million compromised devices. In response, Avast announced on January 30, 2020, that it would immediately shut down Jumpshot and cease all operations due to the backlash of its users' data privacy.

On the basis of the information revealed, on 11 February 2020 the Czech Office for Personal Data Protection announced that it had initiated a preliminary investigation.

In February 2024, the Federal Trade Commission fined Avast $16.5 million for collecting user data and reselling that data. The collection was done under their program to ensure that such collection of user data was not happening.

According to Vivaldi's blog post "Why isn't Vivaldi's browser open-source?", all of Vivaldi's UI is closed source and not source-available:

Note that, of the three layers above, only the UI layer is closed-source. Roughly 92% of the browser’s code is open source coming from Chromium, 3% is open source coming from us, which leaves only 5% for our UI closed-source code.

Keeping Vivaldi’s UI layer closed-source and obfuscated allows us to set these worries aside, so we can focus on the job at hand. It may not be a perfect solution, but as a business, we have to make decisions that minimize uncertainty, if only for our self respect as employees – and employee-owners.

The UI is the main thing that differentiates Vivaldi from Chromium, and Vivaldi chose to keep it closed source and obfuscated for business reasons. That's a negative compared to Firefox and Ungoogled Chromium.

If Vivaldi were free and open source, it would make an interesting alternative to Ungoogled Chromium. But it's not, so I'll stick with extensions on Firefox (and Ungoogled Chromium as a backup).