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.

The only reason Firefox still has any market share is probably because it is old enough. I highly doubt this browser will ever stop google forcing a new web standard. We need to educate the general users to make better tech decisions if we want change. We can stay hopeful about this engine. Still would have liked it if servo was getting more development.

Firefox and chromium are open source. You can just remove mozilla and google telemetry during compile, or disable in the settings.

Fingerprint is 100% still useful even with telemetry. This is not a privacy browser and is still in early stages, volatile and easy to fingerprint (not even counting it is a different web engine and so has an even smaller userbase than Firefox). Also, a content blocker is good for cyber security, so regardless of fingerprinting, this is not ready for privacy-conscious people.

I made my original comment to add context about why this browser shouldnt be used if you care about privacy. If OP had said “this is a promising new independent player in the browser world, look forward to seeing what they do in the future when its more stable” I wouldnt have said anything.

Lol, but also JS being volatile in the current browser makes it easier to fingerprint.

It is just disappointing. But people forget that there are many FOSS projects that we widely use where the developers have shitty ignorant opinions. Maybe peoples uproar is directly related to the refusal to merge a simple grammar change, which seems very anti-open source. Or maybe that the Dev has a code of conduct that speaks about inclusivity which they weaponized to justify not merging, as to be “politically-inclusive” (aka some people dont believe that “they” can be used for one person lmao). It just feels like they are choosing a weird hill to die on and also being a hypocrite by being so intentional obtuse, and of course the devs abrasive and accusatory method of responding on multiple occasions.

I think it is harder to separate the Dev from their creation when it relates to open source. It really is a passion of the heart a lot of the time. But that doesn’t make the tech any less interesting.

That doesn’t make it private. Privacy on the modern web requires anti-fingerprinting, otherwise any website with tracking scripts can easily start creating a shadow profile for you.

Edit:
What I mean is it isn’t a browser anyone who cares about their privacy should use (yet or every depending on development). Not close to ready yet. OP didnt put any context either for why they posted it.

Is this browser private? Does it implement proper sandboxing and have any methods of anti-fingerprinting? I hope it eventually see the implementation of a robust content blocker. What makes this related to privacy and not instead just open source. While it is nice to see an independent web engine, if there is no method of anti-fingerprinting, the privacy of this browser is severely limited.

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.

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.

DivestOS is the most thoroughly degoogled of the android ROMs (it removes the most proprietary binary blobs). DivestOS is also decently security hardened, better security hardening than any other Android ROM other than GrapheneOS. But since it removes more of these proprietary blobs, it further reduces the attack surface of the ROM. Both GOS and DivestOS are good options. As commented by another user, /e/OS falls behind on security updates often, which is quite bad for a security or privacy focused OS.

I assume they mean proprietary code blobs.

If they want proper anonymity, the user needs to protect against fingerprinting from the duckduckgo website (Tor or Mullvad). If by anonymity you are meaning from OpenAI, then duckduckgo needs to be running user’s text prompts through a paraphrasing LLM to normalize text and avoid deanonimization using writing-style Fingerprinting.

Unofficial MCPE launcher is the only way to run bedrock on Linux

Many mechanics, and bugs, and features. Redstone is very different because the bug/exploit parity doesn’t exist and even obvious features are different (Redstone attaches to pistons). When they add a new mechanic, the bugs are different and unique to each game. Like because cauldrons can hold potions in bedrock, you can (idk if its changed) use the newish block dripstone to increment the potion fullness, duplicating it.

I assume it has documentation, otherwise you can look at the Flatpak docs to see the equivalent terminal commands that are available in the GUI. Flatseal is pretty intuitive in my experience.