u/RichIbizaSport

Image 1 — I built a Feeld likes scanner - They're definitely hiding likes for non majestic users
Image 2 — I built a Feeld likes scanner - They're definitely hiding likes for non majestic users
Image 3 — I built a Feeld likes scanner - They're definitely hiding likes for non majestic users
Image 4 — I built a Feeld likes scanner - They're definitely hiding likes for non majestic users
Image 5 — I built a Feeld likes scanner - They're definitely hiding likes for non majestic users
▲ 101 r/feeld

I built a Feeld likes scanner - They're definitely hiding likes for non majestic users

As someone with a background in tech/coding, I figured I'd have a crack at the feeld API. What else should I be using my enterprise codex license for? 😅

I think we all had the suspicion that Feeld hides likes from your discovery feed. Though my code doesn't 100% prove it, it's as near as dammit confirmed it.

Massive kudos to the niewiemczego repo on github, which allowed me to get started on this. There was also a reddit user called ghost something or other, who was on the subreddit for a short while before disappearing - he made a web gui with some extra features that gave me some ideas.

Unfortunately, Feeld have locked down the API since then, so it's very difficult to get anything useful. I wouldn't really advise doing this as you'll probably get your account banned. I won't be running it again. I've done this purely for fun, I just like the challenge and building something cool. I'm not looking for weaknesses, vulnerabilities and I'm not making any money or gain.

Background:

  • Male, ~40 years old, London. Looking for women, MF, FF. Between the ages 28-42
  • Non majestic. I have 66 likes, obviously hidden.

Of those 66, the Feeld API will report back 20 profile IDs. I got one like whilst testing this tool, so I now have 21 profile IDs stored.

I built a scanner which moves my location to 47x 2km radiuses around London, so roughly within zone 3/4 ish. All overlap, so there are no location gaps. At each location, it will change the discovery age range to 1-2 years, load all the profiles, then move onto the next age ranges. Then finally moves location. I'm using 18-50 as I want to make sure as many profiles are scanned as possible.

The Loop:

  1. Set location to first 2km radius
  2. Set age range 18–19
  3. Load profiles
  4. Check for matched profile ID
  5. Set age range 19–20
  6. Load profiles
  7. Check for matched profile ID
  8. ...[repeat for all age brackets up to 50]
  9. Set location to next 2km radius
  10. ...[repeat for all locations]

I had to keep my search as specific as possible so I didn't go above the limit of 200 profiles the API will return given a unique search.

It's true that of those 21 likes that have profile IDs, they could have been in London temporarily, but I doubt all of them would be. They could also be over 50 - which also seems unlikely.

So of ~13.5k profiles scanned, using ~2k web requests..

Do you want to know how many of the profiles, that already liked me, appeared in discovery?.... Zero.

u/RichIbizaSport — 13 hours ago