Yes.

Yep, and Google own employees are forbidden to protest of that project, if they wish to keep their job.

Excuse me, what. What is your reasoning behind that question ?

Exactly that. Each instances has it's own rules and as such, you can make your own on your own instance. Just don't be surprised that some instances block you for not abliging to their standards, as they also control their own federation, like each individual instances.

First. Let me explain some bits about the Play Store. You are using the Google Play store, so of course, it stores the list of installed apps on your Google account. That's fairly obvious. However, the relation with the apps generally end there. Some apps might have Google account integration (Google Games for example, or just as a login method) but not more than that. There's also potential Google ads and Crashalytics, but it ain't "directly" connected to your Google account (It link your device through an unique ID, which Google could correlate with your logged Google account on this device)

That out of the way :

• ProtonMail android app doesn't use any of those Google stuff in it.
• You can download their app separately of the Google Play Store. Throught their website, source-code release or F-Droid (Depending of their project. Proton isn't consistency with those)
• ProtonMail don't care about your Google account, outside of importing your emails into your new Protonnail account if you choose to do so.

Also, there is still a privacy gain, from using an email address from Protonmail, but only when you use it. It is just a better and more private e-mail provider. If you keep using a Gmail and Outlook email, than you will still issues with those emails addresses be used and read, for ads and analytics.

Do note you can use your protonmail address on your Google and Microsoft account. Those services just tend to automatically create an email account on their respectice services by default (Gmail & Outlook) but they aren't required.

Have you looked at the community you are referring to? Ain't FOSS. Instead, I would suggest https://removerized.tech/ (Locally in your browser AND hostable, under GPL-3) https://github.com/yossTheDev/removerized Or rembg https://github.com/danielgatis/rembg

Maybe you would be interested into maintaining Gradience instead of making a new LibAdwaita theming app from scratch ? Just thinking, haven't tested it but I don't see any straight reasons for one over the other outside the maintainership. https://github.com/GradienceTeam/Gradience

They don't. They rely entirely on donations (and sponsorship donations). It also mean, they have less resources to maintain and develop their software, ESPECIALLY Conqueror since it's not as much well-maintained compared to other parts of the KDE software suite. Plus, Firefox do maintain their own web-engine, while KDE just use the WebKit one, so even more reasons that Firefox can't substain with the resources KDE currently has.

Sure do confirm that hard-coded sudo requirements are kinda dumb. But this proove systemd point. BSD mainly use doas. Linux mainly use sudo. Why not have an universal method for true cross-platform compatibility ? (Yes, I know plenty prefer or explicitly are against the usage of systemd suite of software, was pointing out systemd main reason of planning to propose an another standard, regardless if it will be popular or not)

When was the last time you had to edit sudo configuration file ? Same goes for doas. It's has nothing going for, for the majority of desktop Linux users (from what I got as an answer)

Speaking of doas, is there any advantage of using it when… sudo is still available to be used? I agree that most of the stuff we require to use doesn't need all the options sudo as, but if it is for the sake of security, maintenance, and stability… is there any reason to use doas ON TOP of the already setup sudo or su? In the past, I even tried to just apply a simple alias to replace sudo with doas, but numerous scripts and programs when trying to request explicit super-user permissions, just didn't know what to do with doas as expected, so this ain't it.

Okay, so it wasn't VNC, it was ssh stuff instead.