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!

community.e.foundation/t/defau

@gael should be drop /e/OS entirely for simply being LineageOS for MicroG but with deceptive marketing and a different branding slapped on top?

cc @hellpie

@succfemboi @hellpie@weeaboo.space You should really do this if you are not interested in what we are doing which is described at: gitlab.e.foundation/e/wiki/en/
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.

@gael You're just raising money by selling an already existing project which is already usable as your own brand. It's not building, it's more of leeching

@succfemboi Ah you are THE guy ^^ At some stage I wish you can unlock from your deadly logic.

@gael @hellpie@weaboo.space

why not just contribute to LineageOS for MicroG directly?
That pointless fork only fragments development
@gael freedom to decieve people in thinking /e/ has developed it from the ground up?

@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.

@gael
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 However they seem to already struggle with regularly syncing their fork with upstream LineageOS, which provides /e/-users a build that is sometimes months out of date. I wonder how that will develop when they fork from AOSP directly.

However I do see that /e/ is different from LOS+MicroG by claiming it to be Google-free (even though it does connect to Google with microG) and bundling it with questionable apps that either use an a selfmade and insecure protocol for encryption like Telegram or requires Google Services to properly function like Signal for example.

@gael @hellpie

Follow

@succfemboi
There a still in the building phase so it would not be a surprise if the codebase is not the latest.

From my experience, getting rid of the Firebase Cloud Messaging service has been the hardest so far.

@gael @hellpie@weeaboo.space

@succfemboi @gael
I still have this handful of application that relies on it (Signal being of of them). Therefor not integrating such solution would mean to create an alternative and hope for the app devs to use it. It still relies on Google, yes, but it seems necessary to me in order to ease the transition.

@noodleman but MicroG already provides support for Google Services. Why switch to an outdated fork that does not develop these features but only bundles them toghether. Doesn't Signal already work for you on LOS?

@gael

@succfemboi
So far, my apps without MicroG do not receive push notifications.
@gael

@noodleman but didn't you say you have microG? You can easily flash MicroG by itself when you already have LOS
@gael
Sign in to participate in the conversation
Mastodon

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!