this post was submitted on 19 Jul 2023
1030 points (91.7% liked)
Technology
59593 readers
3030 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I know a software developer that worked for Ally when they were adding this. They all said it was a terrible idea, but were ignored. The reason they claim it’s needed is to track app installs that originate from an ad on Facebook. Since the App Store sits in between the ad click and App launch, there isn’t an easy way to track it without that. But, it shouldn’t be blocking you from logging in.
I'd bet you bottom dollar Ally is selling their customers' financial information to Meta, and this is a manifestation of that.
I wouldn’t doubt it.
Might not even be selling it, could just be an arrangement to use some sort of "sign in with facebook" service or even advertise on facebook marketplace/adverts
So you see, Your Honour, we didn't sell Facebook any data - we just sold Facebook the ability to harvest our users data directly.
I remember we had to build an obj-c wrapper for FB's calls like these because of these crashes, that basically ignored the stall and continued the user's session regardless
How does that work exactly? Does the App Store pass along some information to newly installed apps or something? My company's app, which I worked on for some time, also uses an external service to track installs (not Facebook or any social media), but I didn't work on the implementation of it and never really got to grips on how it works.
App store doesn't, the app itself does, that's why this thing is included in it.
You click an ad on FB = you're ID'd by a cookie or login or account on the device or fingerprint or whatever (probably all of the above)
You install the app from app store. Neither the bank or FB knows this.
You launch the app. The integrated FB library reads the cookie or FB account on the device or whatever it can, and pings FB. FB compares this ID to the entries and finds that it was you who clicked the ad.
FB bills bank for an ad click
Another option is there to be a specific FB variant of the app with its own app store entry, but they probably wouldn't do that for something this trivial.
That’s a good question and I’m not entirely sure. I am just saying what they told me. Sorry!