Except that it is in fact relevant. It's not the only answer there, but it's quite relevant not only to the particular case that the article is about, but even in other aspects of it all that other posters have been brining up as part of the discussion.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Small Number of SwiftKey Users Discover App Leaked Private Data to Strangers
- Thread starter MacRumors
- Start date
- Sort by reaction score
I liked the old stock keyboard better. The new one lags and can't keep up with my typing, and not once have I found the suggestions useful.
Don't know the suggestions, they make for hilarious conversations.
Too bad they usually circle around a narrow selection of words, so you have to "seed" a lot to generate new fun messages.
Glassed Silver:mac
It's no more relevant than if the discussion was about electricity, which is required to charge the battery in order to turn on "Full Access" in the first place.
Blaming Full Access for this issue Swiftkey has is just using it as a scapegoat. How did Android users using Swiftkey that are affected by this turn on Full Access?
How about not blaming it but simply taking about it as an option that would avoid this particular issue as well as other potentially similar ones that third party keyboards bring up in people's minds, given that the discussion in the thread includes that more general aspect of it all.
It's no more relevant than if the discussion was about electricity, which is required to charge the battery in order to turn on "Full Access" in the first place.
Blaming Full Access for this issue Swiftkey has is just using it as a scapegoat. How did Android users using Swiftkey that are affected by this turn on Full Access?
Whether or not this applies to Android in a similar manner is moot as the full access discussion is in relation to iOS. Reading the thread and the context of it all and not just the article would actually help. Faceplam, indeed.
I suggest you take the time and actually read the source article and find out what the problem is Swiftkey have encountered. Full Access is irrelevant.
You know what would also be an option to avoid the Swiftkey issue? Not using the sync feature, but I don't see anyone suggesting that...
And that's because this thread is not about avoiding the problem at all, it's about the blame game.
Not granting full access avoids the problem. Not enabling sync also avoids the problem. As part of this discussion people have brought up other more general concerns of potential data going somewhere when using a third party keyboard, thus not granting full access would address that, as it would also address the particular issue that the article is about (even though there's another more specialized option relating to it as well).
A number of generalizations are being made as far as what all of the full access discussion is all about and what apparently what this thread is about, when plenty of it doesn't do any of that at all.
No, because the assumption from most of the posts in this thread is: Enable Full Access and Swiftkey will leak your data to strangers. Which is completely wrong, hence my first post.
It's about as accurate as saying filling your car with petrol will lead to a car accident.
Doesn't seem like that's the assumption from most posts, and definitely isn't for a number of ones that I can personally speak for. On the other hand it does seem like there is an assumption in play: the assumption you've made about most posts that refer to full access.
Yeah, and I'M the one who's making assumptions. /s
Get a clue C DM.
I'm out. The story is accurate, but this thread is full of misinformation. It's funny that out of many other sites reporting on this, none of the comments sections have even mentioned Full Access at all.
Last edited:
I was specifically talking about keyboards that NEED full access to function.
Never did I grant it, but when a keyboard wouldn't work without it, it got binned.
That's all.
Why? Not because a leak like this may occur, but because I don't know if I can trust the developer with my data.
All it takes is one screwed update or one nosey government agency.
Sorry, but for what I'm looking for in a keyboard it doesn't have to connect to jack all, so if it asks for more than I'm comfortable granting it's gone.
Glassed Silver:mac
Last edited:
Doesn't seem like most of those are saying SwiftKey will leak data to strangers. Simply talking about a full access and privacy in general. Again, seems like reading-in more than what's there in quite a few of them. Not to mention that there are other discussions about full access that you decided not to include since they didn't quite match up with the assumption and generalization you were making.
In any case, what started this was your statement that people talking about full access didn't even read the article and that full access had nothing to do with it. And yet the simple truth that has been pointed out a few times already is that while there is a separate option relating to specifically what is behind what the article talks about, the full access option also addresses it and other potential concerns that have been brought up by various people in the thread. Nothing incorrect or misinformed about any of that.
It sounds like it all has been hitting a nerve though, right from the very first accusatory generalization, so it does seem like it's best left at that.
Last edited: