Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

same ping_time now #141

Closed
hmpws opened this issue Mar 29, 2017 · 7 comments
Closed

same ping_time now #141

hmpws opened this issue Mar 29, 2017 · 7 comments

Comments

@hmpws
Copy link

hmpws commented Mar 29, 2017

Seems like they changed the API and it always return the same ping_time now? Maybe it is worth noting.

Edit: Maybe it is to do with this Tinder Online that they are launching. Tidying up the API.

@hmpws
Copy link
Author

hmpws commented Mar 30, 2017

I see a "last_fetch_time" from the /user/recs but nothing if you just request /user/id. Where did you see "last_activity_date"?

@sof123
Copy link

sof123 commented Mar 30, 2017

last_activity_date is at /updates. it was actually there before and it does not seem to be related to just being online so it's not as useful as ping_time. it appears to update every time there's a message, liked message, when you match aka visible activity

@Jonovono
Copy link

So did Tinder they remove the last active date from the api now? I figured they would eventually since they don't show it in the app anymore.

@DylanVanAssche
Copy link

To avoid tracking users I guess...

@hmpws
Copy link
Author

hmpws commented Apr 12, 2017

I used it to track bots mainly, because they were usually inactive profiles :(.

@DylanVanAssche
Copy link

Nowadays, bots almost send first a message containing the same text (which I have encountered). Maybe you can filter on that?

@charliewolf
Copy link
Owner

Tinder likely deprecated this feature but kept the field in for old clients.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants