Specific blocklists are designed to block fingerprinting scripts. This can help, but it is better when done by the browser.

Ublock doesn’t stop (all/most) fingerprinting. A hosted frontend or instance can help protect against this vector of attack.

VSCode (or the base app used by it) is open source (see: VSCodium). It has a similar relationship to Chrome and its base Chromium, where assets and tweaks are added to brand the product. You may have been trying to say “a great open source, VSCode alternative” and I misunderstood. Just commenting to remove ambiguity.

Unrelated from the prompt:
This may effect the sandboxing of Firefox and change the fingerprint of your browser.

AGPL for the WIN!!! Sadly licensing only works if we have competent laws to protect small developers. The enemy doesn’t play by their own rules.

This is true. I agree that developers should use more inclusive language in their documentation. I mostly just thought people saw the other post already.

“Singular they” has been common in english since somewhere in the 1300s. Idk how it is confusing, and even if it is, do those individual’s opinion outweigh like grammar? If people are confused they can learn, lest they be confused forever. “They” in this instance would be replacing “he”, so I think the benefit is clear. Or avoid ambiguity by just saying “the developer” (cus I think it was Dev documentation iirc).

Edit:
Maybe it was referring to the browser itself? Therefore “it” would make things much less confusing.

I was only commenting that this post has been posted already twice, once in a closely related community. I have already had to argue with people supporting the Dev’s choice to be bigoted. I will just scroll past, just not excited to see more transphobes crawl out of the woodwork.

It think the discussion of this issue has been thoroughly explored in your other post on the “free and open source” community. People know about this now. Is there anything else to cover? All that will be talked about is either “wow, that was an overreaction from the Dev, they seem close-minded” or “you should separate the tech from the developer” or people (bigots) just saying they think he made the right choice.

The discussion is stale.

Another app with mentioning, Simple Time Tracker

Snap is closed-source backend and is hardcoded to use Canonical’s repo (therefore centralized). Kinda ironic I think. I can’t find it through flathub sadly.

Thanks.

How do I compile from source? I would like to see that in the readme

Sorry, misunderstood. Proxmox Free broke my containers on updating a while ago.

Now I use Docker-style application containerizing, but I think LXC (the base technology powering Incus/LXD) is useful in a number of situations and perfectly viable for use. I think Incus-containerized applications are easier to upgrade individually (like software updates of your apps, no need to recreate the container image) and gives a closer to native experience of managing. You do lose out on automated deployment of applications from widely available image sources like docker.io, but the convenience-loss is minimal.

If incus works for yoy, use it. Proxmox locks you out of the option to choose your base server distros.

I remember updating (maybe a year ago now) and it making all my containers unaccessable.

How recently. I tested with Mullvad and it gave me a notice.

They block VPN users.

I just read through the unofficial Flathub Flatpak for Signal and it is very simple. It fetches the .deb from Signal’s website, installs it in the sandbox, and uses a launcher script to tell the OS some basic toggles like should it start minimized or should it display a tray icon. In the script it makes use of zypak, which to my understanding is to tell electron (chromium) to allow sandboxing to be handled by Flatpak. Here is the repo and the build instructions is the .yaml file.

Microsoft Activation Scripts (MAS)

Alternatively to upgrading edition check out these apps:

• KDE Connect
• Syncthing