Avatar

N.E.P.T.R

Neptr@lemmy.blahaj.zone
Joined
0 posts • 28 comments
Direct message

It removes more proprietary binary blobs and I dont care about gapps.

permalink
report
parent
reply

I heard that he was a scammer or pseudo privacy expert from other comments. I wouldn’t recommend that phone. If you care about the privacy or security of your device, use DivestOS with a supported Pixel/OnePlus, or GrapheneOS with a Pixel. Only buy the phone new if you are super paranoid of some zero-day vulnerability being used on you. I recommend swappa.com because they have quality control, returns, and good prices for used devices (you can even get mint quality devices).

Comparison of Android ROMs: https://eylenburg.github.io/android_comparison.htm

iodeOS has been behind on security updates often (still better security against unsophisticated attacks than Ubuntu but not a good ROM): https://divestos.org/pages/patch_history

permalink
report
reply

I already was corrected by another comment.

permalink
report
parent
reply

No VoIP, spaces, or threads support yet. Promising because it is written in rust and works well with Desktop portals.

permalink
report
parent
reply

My mistake.

permalink
report
parent
reply

Typo in your function definition according to your IDE. Guess that means no women are getting paid. Alternative interpretation is that the function will cause the program to error out resulting in a destabilizing of the power structures or something idk.

permalink
report
reply

I honestly dont care about my browser using a lot of resources (processes, RAM, etc) because it may be helpful to the isolation security model of the browser. Each and every website is a possible malicious app.

permalink
report
reply

My recommendation is GOS if you care about out of box experience and using gapps, DivestOS if you care about degoogling and removal of proprietary code. Both are hardened.

permalink
report
reply

Some made a pull request with all the changes made already. The issue that the PR addressed was the excessive use of he/him in the docs when referring to developers (aka the person reading the docs). Contributors expressed that they didnt think using male only pronouns in the docs made much sense when referring to any developer reading the docs. This wasn’t some entitled person trying to force the ladybird dev to rewrite the docs, all they needed to do was merge the changes.

permalink
report
parent
reply

Thought so. Thanks for the reply.

permalink
report
parent
reply