@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

@gael so basically not only apps are preinstalled but they also fork various services and slap their own branding on top of it as well while using an outdated base

@noodleman @hellpie

@gael @succfemboi @noodleman

#/e/ is a fork. It looks to me like #Ubuntu forking #Debian to push forward useability for beginners while heavily relying on Debian work underneath.

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 😠

@tuxicoman but Ubuntu is never that out of date as compared to /e/ . Canonical doesn't rebrand apt, deja-dup or their other preinstalled apps while keeping those versions fairly recent on Ubuntu @noodleman @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!