-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
About /e/ #55
Comments
About Wikipedia: https://ewwlo.xyz/wikipedia.html |
I feel this can be closed for now, however any input is still appreciated, as always. |
If you quote LineageOS you must quote /e/. Indeed /e/ is based on LineageOS and takes out the last pieces of Google that are left from it. /e/ is therefore much better degoogleized than LineageOS. LineageOS teams explain that they are not against Google and that they use some of their services, such as DNS or connectivitycheck. You can read this to learn more about LineageOS and Google: https://www.reddit.com/r/privacy/comments/cldrym/how_to_degoogle_lineageos_in_2019/ |
/e/ is not going to be added. If there are concerns about LineageOS, please open a new Issue. |
(For reference, read Issues #6 and #27)
/e/ is an Android alternative. There seems to be a bit of controversy over whether or not it is truly privacy friendly. Read the above issues or this link for privacytools.io.
The founder of e.foundation reached out to me over email and provided me with a number of links:
Other relevant links:
Based on the above links, it is difficult to be certain that /e/ is totally Degoogled. I do think they have privacy in their best interests. It is clear based on forum posts that transparency between the company and users is an ongoing issue. I recommend each user read through the links to determine if it is the proper solution for them.
Consider this pinned issue as a place for open discussion. Avoid starting flamewars! This is also not the place for personal opinions.
The text was updated successfully, but these errors were encountered: