Not really "deGoogled"? Connection to mtalk.google.com

[waterfall]

I was suprised to see a connection to mtalk.google.com after getting /e/ os.

The /e/ os overview page starts with this header:

/e/OS is a complete, fully “deGoogled”, mobile ecosystem

But… it’s not?

While there is surely a technical reason, it smells a little bit like false advertising to me? Maybe add an asterisk?

[andrelam]

There is more… Calls home when connected to private DNS (#1422) · Issues · e / Backlog · GitLab in my opinion this can never be in v1. If i see the forum i sometimes wonder if v1 is tested at all I love /e/ but sometimes i almost

[AnotherElk]

@waterfall

But… it’s not?

It wants to be. And considerable effort is put into this.

@andrelam

my opinion this can never be in v1.

It’s just a label someone decides to assign afterall.
New things were added, issues were dealt with, issues persisted, issues emerged. On to 1.1 and 1.2 … https://gitlab.e.foundation/groups/e/-/milestones?sort=due_date_desc&state=all

[petefoth]

@AnotherElk

It’s just a label someone decides to assign afterall.
New things were added, issues were dealt with, issues persisted, issues emerged. On to 1.1 and 1.2 …

Butt adding a major new feature - Advanced Privacy - in v1.0 without testing it in v0.nn betas? Who thought that was a good idea? Seems like marketing (“We want/need to be able to say we have this, for the big launch announcement”) won, over technical (“We really should test this functionality properly before we include it in a major release”). It caused the overall quality - and the appearance of quality - of v1.0 to be significantly worse than v0.23: location “doesn’t work”, issues with accessing the network, battery draining, etc.

Really disappointing for users, and if I were a developer, I would be really angry

[Raffael]

I think the sweet spot would have been to ship advanced privacy in eOS 1.0 but turn all its features off by default (at lest for me, it was active after installing eOS 1.0). So it is there and everyone who wants to can use it, but it would not impact the user experience in cases where the users are not even aware that this thing exists.

@petefoth

Butt adding a major new feature - Advanced Privacy - in v1.0 without testing it in v0.nn betas?

In my experience so far, advanced privacy does exactly what it should do, but choosing to use it makes some apps not work anymore, and this cannot be resolved by more testing. Instead, everyone needs to learn or be taught what it is and when to use it.

[petefoth]

@Raffael

I think the sweet spot would have been to ship advanced privacy in eOS 1.0 but turn all its features off by default (at lest for me, it was active after installing eOS 1.0). So it is there and everyone who wants to can use it, but it would not impact the user experience in cases where the users are not even aware that this thing exists.

Yes - that would have worked, and would have been a sensible approach. But unfortunately they enabled it, and as a result, they shipped an OTA update which appears to have effectively broken many users’ installations. Unforgiveable IMHO

[Taurus]

See also:

App Lounge: Data Privacy from Google?

Apps has now been replaced with App Lounge, which, like Aurora, connects directly to Google servers. Observing these multiple connections occurring in the background upon opening App Lounge is quite disturbing. In light of this, can someone from e.foundation explain how this choice fits in with e’s stated mission, and what it means for users who actively avoid Google’s data exploitation? (I understand why you’re transitioning away from cleanapk.org, so no need to explain that again.) Thank yo…

[dubious]

Use decloudus alpha.dns no more google.But you cant reach app lounge.Fdroid ok.

[rainwalker]

/e/ removes unnecessary calls to google and anonymizes those which are necessary using microg. Also /e/ cant stop 3rd party apps making calls to google, or web pages. You need an adblocker for that.