Deutsch   English   Français   Italiano  
<v577ng$2q13$1@nnrp.usenet.blueworldhosting.com>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!weretis.net!feeder9.news.weretis.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: Andrew <andrew@spam.net>
Newsgroups: comp.mobile.android
Subject: Re: Android keyboard: your choice.
Date: Sat, 22 Jun 2024 19:12:48 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <v577ng$2q13$1@nnrp.usenet.blueworldhosting.com>
References: <20240617114559.a2970ac2923facc44a2ec355@gmail.com> <v4ov83$j5oj$1@dont-email.me> <v4sojj$1gqik$1@dont-email.me> <lde8tqF9a76U1@mid.individual.net> <v4tkrl$1bpq$1@nnrp.usenet.blueworldhosting.com> <ldfbtsFe5o7U2@mid.individual.net> <v4u0gv$1rom7$4@dont-email.me> <ldia0iFrps7U6@mid.individual.net> <v51gft$2kg3e$1@dont-email.me> <ldj1v5Fs5uU1@mid.individual.net> <v54msb$2s6v$1@nnrp.usenet.blueworldhosting.com> <v54ob8$3b4pm$1@dont-email.me> <v555ma$fqm$1@nnrp.usenet.blueworldhosting.com> <v55tsm$3la2e$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Injection-Date: Sat, 22 Jun 2024 19:12:48 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
	logging-data="92195"; mail-complaints-to="usenet@blueworldhosting.com"
Cancel-Lock: sha1:lYWqI3/dMwm4FNkDwCJ4nbqiJCg= sha256:TQWho3SossGUCSaTkM2aF8uTKsa5z22HrZIGZdvccsc=
	sha1:n12kQdRjjO9UH5+C9jwdJzpn9BQ= sha256:L5CLIAQJX8FU3r4culEkvsqAQC/URjpk9XYyeLpF830=
X-Newsreader: PiaoHong.Usenet.Client.Free:1.65
Bytes: 3829
Lines: 41

R.Wieser wrote on Sat, 22 Jun 2024 08:39:14 +0200 :

> Oh yes, there seems to be a difference : the first being the back-end and 
> second the front-end.  At least, if I maye take Googles own word for it :
> 
> https://firebase.google.com/firebase-and-gcp

Thank you for noticing that there's a difference between "Google Firebase"
and "Google Services Firebase App Indexing", where I read what you quoted
and that seems to be the former but not the latter.

While I will freely admit to not knowing what either one truly is, I don't
think one is just the back end of the other - simply because the whole
purpose of "Google Services Firebase App Indexing" is for the app to get
its data in the users' search results ON THE PHONE (as far as I can tell), 
while the whole purpose of "Google Firebase" is for the app to link in
access to Google's cloud.

As far as I can tell, those are two completely different endeavors.

The fact that they're likely completely different things with similar names
is why I've said that anyone talking about one without mentioning the other
almost certainly doesn't know what either does.

The issue at hand, as I see it, is that the "Google Services Firebase App
Indexing" saves extremely personal data ON THE PHONE which then Google
clearly says they will sample intermittently for statistics.
 <https://medium.com/android-news/firebase-app-indexing-for-personal-content-getting-personal-content-into-search-c52bfe45b3ac>
   "A note about privacy: The personal content index only exists
    on the user's device. None of the user's personal content is 
    uploaded to Google servers and it only remains on the device
    while the app is installed. However, aggregated statistics
    about apps' usage of App Indexing and other system health 
    information may be uploaded to Google servers."

Notice that means it doesn't matter one bit if an application has no
Internet access... Because Google does.

Anyway, we're far from the topic of the Helium keyboard so I opened a
separate thread with your links and mine to help understand it better.
 *Why do so many people confuse Firebase & Firebase App Indexing?*
 <https://www.novabbs.com/computers/article-flat.php?id=53667&group=comp.mobile.android#53667>