If you trust the client that is encrypting and uploading the file - which runs on your computer and thus can be audited, modified, or even entirely replaced by you. You do not need to trust that the server (which ideally is also free software, but in practice is a black box you don’t have any visibility into) is sending you trustworthy code.

Not at all, really. Forking is fine and building a business off of it is fine (I don’t personally see the value in it but apparently Y Combinator saw fit to invest in this so what do I know). Where they fucked up was replacing the existing free software license with some “AI” generated mumbo jumbo, because they were “too busy building” to “bother with legal.”

You didn’t have to “bother” with creating a license, because there already was one. No one in free software should be rolling their own custom license (GPT generation aside) because there exist perfectly good ones already.

I’ll be “that guy”:

F-Droid is a software repository, not an app store. The distinction is subtle but important. A software repository offers a community-curated collection of software packages whereas an app store is just a marketplace for software developers to offer products to end-users. A software repository serves the interests of its community first, whereas an app store is merely a means for developers to sell products to end-users.

There are those who believe that F-Droid’s role as a “middle man” vetting and building packages from source instead of blindly shipping builds provided by upstream makes it a security risk, because you’re trusting F-Droid in addition to (some say instead of) the upstream developer. Perhaps telling is that none of these critics can offer an alternative solution.

Before anyone mentions Obtainium and Accrescent, these are not alternatives to F-Droid, they solve completely different problems.

This is why the marketing around flatpak bothers me. It’s touted as some kind of “universal Linux package manager” but Linux is just a kernel - all the stuff that apps depend on comes with the distro. So, in order for flatpaks to be “distro independent” they basically have to supply all the stuff that normally comes from the distro - effectively building a second distro on top of your existing one.

Nix and Guix are the same but at least I think they’re more up front that they are effectively distros that can run on top of your existing distro or as a standalone operating system directly on top of Linux.

FUTO changing the definition of open source to suit their business model is like that time US Congress decided that pizza was a vegetable because it has tomato sauce.

FUTO’s EULA may superficially resemble a true free software license (and may be good enough for you, personally) but it fundamentally undermines core tenets of the free software movement in order to preserve their business interests. All pseudo-FOSS licenses (whether of the “ethical” or the “business” variety) do this, because they prioritize the interests of the rightsholder above those of the community and the user. If important free software projects like Linux and Firefox were released under this license the free software world as we know it would not be possible.

As proprietary licenses go, it’s certainly far from the worst.

Free software is a matter of liberty, not price. It is perfectly legal and ethical to sell free software. Keep in mind if you’re using third party code (whether it’s libraries or external contributions to your application) you must abide by the terms of whatever license it is under, this is whether it’s paid or gratis.

It’s even perfectly legal to fork an existing free software project and sell it on the play store, although whether that is ethical or not is up for debate - depending on what efforts you put into your fork before selling it, an orthodox Stallmanist might have no problem with it but the original developer(s) of that code may perceive this as “theft.” Keep in mind you must abide by the terms of whatever license the project is under, so if it is a copyleft license like the GNU GPL you must either provide corresponding source code or an offer for such.

Assuming they own the copyright (which I believe they do, since they were able to relicense it to begin with) they can absolutely offer it under a dual licensing arrangement even if the licenses are incompatible. It would only be an issue if other peoples’ AGPLv3 licensed code was in there, but as it is not the only copyright they would theoretically be violating is their own, which is literally not possible.

Dual licensing under a free software license and proprietary EULA is a common business model, especially when the free software license is a strong copyleft like the AGPL, since the proprietary licensors do not have to abide by certain conditions that free license users have to.

When one asks if something is free software (a.k.a. FOSS) the concern isn’t so much trust but rather can one view, modify, and share the program. Sandboxes solve a different problem.

In the case of a javascript bundle, in order for a user to exercise the Four Freedoms they must at minimum be provided with corresponding source code for each component in the bundle, and preferably some way in the browser for the user to inspect and modify it. In other words, it must be treated like any other compiled binary program. A lock file with specific versions probably isn’t necessary (and server configuration and source code definitely isn’t).

You are right in that this would require cooperation from the service provider to provide this metadata, and most definitely would not do this. Therefore, such an extension as OP suggests would have the effect of blocking the vast majority of javascript on the web today. LibreJS tries to some extent but I don’t know how well it can handle bundled javascript files.

No opinion on OSMand but Magic Earth is proprietary which is a deal breaker for me.

Aseprite is proprietary, but so is this. There is LibreSprite though.

Unfortunately a lot of this seems in reponse to Midori, a seemingly hostile fork with a pretty suspcious website.

To some people all forks are hostile. This appears to be such a case. He just seems to be sour over people exercising the same freedoms he got from Mozilla upstream. Rules for thee but not for me. The free software community doesn’t need his obscure fork.