Should /e/OS drop @telegram and @signalapp as preinstalled apps in favor of the universal and E2E-encrypted Instant Messaging application @delta_chat?
Join the debate!
@succfemboi @firstname.lastname@example.org You should really do this if you are not interested in what we are doing which is described at: https://gitlab.e.foundation/e/wiki/en/wikis/e-product-description-pro-privacy-Android-ROM-and-online-services
You know, this is really simple: we are building something, then people choose to use it or not. That's freedom and I'm super confortable with this.
@succfemboi Ah you are THE guy ^^ At some stage I wish you can unlock from your deadly logic.
@succfemboi That's call freedom
@succfemboi It's very clear on our website that we're forking LineageOS and probably we will eventually fork AOSP directly as we go bigger.
However, please look at what we are doing. We have a consistent description of the /e/OS online. If you keep thinking it's just LOS+microG, I cannot do more for you.
/e/ is not for most LOS users, we have different goals.
Hi. I would like to second Gael on his points. I'm a Lineage + MicroG user and I think it's great if the project gets more accessible to non technical people. I had to dig into the MicroG framework to set it up correctly. I will be sticking to this setup for now but will keep an eye on e.
@succfemboi @noodleman @email@example.com
You keep on forgetting all the details of the /e/ product at https://gitlab.e.foundation/e/wiki/en/wikis/e-product-description-pro-privacy-Android-ROM-and-online-services
Whether fork is good or not is debatable (/e/ provides a lot of integration with its services that would not fit in LineageOS) for innovation.
The re-branding of existing projects is more problematic to me.
#Librem does this too 😠
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!