Andy Burns wrote:
> Expecting new eyeballs to jump into the middle of a 1150+ page forum thread and
> understand what has been going on seems somewhat unlikely
>
> About half the groups I read these days seem to have been taken over by oauth2
> threads, I'd rather see it confined to fewer groups, than spread to more :-(
Hi Andy,
I agree the XDA thread is over a thousand pages, which you and I have kept
up with perhaps, but the average Android user isn't going to keep up with.
<
https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/page-1152>
The short is if you want a privacy based MUA, you'd better get it now.
<
https://github.com/M66B/FairEmail/releases>
<
https://github.com/M66B/FairEmail/releases/download/1.1945/FairEmail-v1.1945a-github-release.apk>
As development, AFAIK, has currently _stopped_ due to Google's unilateral
attack on email privacy for 3rd-party MUAs (presumably including K-9 Mail).
To Andy's point, I've removed the UK telecom folks from the followup as the
main goal of this thread was to post a PSA/FYI to be purposefully helpful
to the team, at large, in order to let people around the world on Android
know that if they want a privacy oriented MUA, they'd better get it now
(whether that's Thunderbird/K-9 or Fair Mail or some other 3rd-party MUA).
For those in this main Android newsgroup, basically what's happening is
Google had grossly deprecated mail privacy as of May 30th, 2022, and at the
same time (unbeknownst to us until recently), Google has also unilaterally
prevented third-party MUAs from accessing Google mail servers.
What Google has been doing is throwing out there autocratic arbitrary rules
against privacy/competition, and waiting to see what sticks - and then when
the uproar has been sufficient, slowly Google relaxes the rules that people
fought... (but only when people fought back!)... which has been the case
with OAUth2 inside 3rd-party MUAs for accessing Google mail servers.
At first, back in March, Google, without warning to developers, disallowed
OAUth2 over the web by erecting an artificial anti-competitive stone wall
to the tune of 15K dollars to $75K dollars yearly (which free apps just
can't afford).
Then in May, the uproar started as Android users found they couldn't use a
3rd-party MUA without adding a Google mothership tracking account to their
Android phone!
Then, in the early summer, after Google allowed OAUth2 over the web for
Android 3rd-party MUAs, Google then erected an artificially low (I think it
started at 30K tokens) OAUth2 token limit (which Google successively raised
to 40K and then 60K) as far as I can recall - but it's _still_ far too low
of a token limit.
Month by month, as the uproar grew, Google slowly relaxed some of these
arbitrary autocratic purposefully anti-competitive anti-privacy limits.
But they're still there!
(Just at a slightly lower MUA developer pain threshold!)
That pain threshold has been reached for some 3rd-party MUA developers
such as Marcel Bokhorst who feels this is anti-competitive behavior and who
plans on filing a complaint to the EU on Google's autocratic behavior.
Therefore, Marcel has pulled his privacy based Mail User Agent from the
Google Play Store repository (along with the only good free firewall).
Because Google has restricted privacy-based MUAs to an artificially low
OAUth2 token limit.
What happens after the app reaches that limit is _all_ subsequent users of
that app will NOT be able to authenticate their Google mail account!
Period.
The user won't know _why_ and the user will blame the 3rd-party MUA.
Especially given the Google GMail MUA is not subject to any token limit.
Therefore, the developer was forced to yank his products from the Google
Play Store repository, as it's unfair to users that third-party MUAs all of
a sudden, for no reason that they can determine, stop working with Google
mail servers. Just like that.
It's clear _why_ Google is doing this, as the last thing Google wants is
for people to have a modicum of privacy; but what's worse is that Google
seems to be breaking the laws on anti-competitive behavior, in addition to
breaking EU laws on privacy.
Bear in mind that Google is essentially forcing millions (maybe billions?)
of people to give them their privacy (via the "second something", and bear
in mind how utterly devious Google is (much like Apple is) in _how_ they
present your "choices" for email authorization.
For example, if you look at all the "choices" Google pretends to give you
to authorize on a 3rd-party MUA, you might not realize that _all_ but one
require that "second something" loss of your privacy (e.g., app passwords,
while they "sound" good, require 2FV/2SV, as do _all_ the other choices).
NOTE: The choices that Google pretends to supply are in the sig, but they
all boil down to trading with Google for your privacy to use their mail
servers by giving Google an extra "second something" that all this is
designed to garner from you by Google.
It _looks_ like you have choices, right?
But Google is lying to you as you see when you attempt each of them.
There's just 2SV/2FV (via about a half dozen "choices") & then there's
OAUth2 (via only two choices, one of which _requires_ a Google Account set
up on the device, which nobody who cares about privacy would ever accept) -
but luckily the other OAUth2 method is via the web (which Google only very
recently allowed for 3rd-party MUAs on Android).
Hence Google (much like Apple) is lying to us (taking us to be fools).
There aren't a half dozen choices; there are two.
a. A "second something" (via 2SV/2FA or via an on-device account), or,
b. OAUth2 (via the web).
What Google is doing to the 3rd-party MUA developers is basically causing
their 3rd-party mail clients to stop working with Google mail servers for
any individual user after Google's arbitrarily puny limit on OAUth2 tokens
has been exceeded. Without telling the individual use a single thing!
This is much like how Apple operates, and is clearly (IMHO and in the eyes
of others) a gross violation of anti-competitive & privacy laws in Europe.
The sole purpose of this thread is to kindly let people know this is
happening, precisely because they haven't been reading the thousand page
thread like I have been doing (and presumably Andy Burns has been keeping
up on).
f'up set to
comp.mobile.android only
--
Together we are vastly more powerful knowing what we know collectively.
1. OAuth2 (using an on-device Google Account or web OAuth2), or,
2. Autoforward Google mail to a non-Google account, or,
3. 2FA/2SV/MSV/MFA via a variety of authenticators, such as...
a. app passwords
<
https://support.google.com/mail/answer/185833>
b. Some kind of "2FA/2SV/MSV/MFA authenticator" app
<
https://support.google.com/accounts/answer/1066447>
such as...
FreeOTP Authenticator
<
https://play.google.com/store/apps/details?id=org.fedorahosted.freeotp>
Google Authenticator
<
https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator>
Authy
<
https://play.google.com/store/apps/details?id=com.authy.authy>
FreeOTP+
<
https://play.google.com/store/apps/details?id=org.liberty.android.freeotpplus>
etc.
c. USB tokens
d. Time-based one-time passwords (TOTP)
e. SMS 2FA
f. Use the phone's built-in security key
<
https://support.google.com/accounts/answer/9289445>
g. Use a physical "security key"
<
https://support.google.com/accounts/answer/6103523>
h. Get a one-time security code from another device
<
https://support.google.com/accounts/answer/2917834>
i. Enter one of your 8-digit backup codes
<
https://support.google.com/accounts/answer/1187538>
j. Sign in using QR codes
<
https://support.google.com/accounts/answer/9283368>
k. Set up a "trusted computer" for sign in
<
https://support.google.com/accounts/answer/2544838>
l. Sign in with "google prompts"
<
https://support.google.com/accounts/answer/7026266>
m. Any others?