@BlendahTom unfortunately yes because we retrieve favorites every 5 minutes so there's nothing left to IFTTT but we are working on integrating read it later like services
I would love using this but the limitations of Twitter’s APIs only allow third-parties to query *the most recent* 3,000-ish favorites. Have these limits been lifted for FavGuard, or are you only able to query + store the most recent 3,000 favorites?
@mkais yes, see: Things Every Developer Should Know[1], or just make the query and you'll see. try to retrieive anyone's 4,000th favorite — it will fail. The 3,200 limit has been in place since the API was launched years ago, it's pretty annoying. So even tho I have 24k favorites, your service will only work for the first 3,200.
[1] https://dev.twitter.com/docs/thi...
This is a great concept, but unfortunately I suspect that this service does not comply with Twitter's API Terms.
You must:
A. use the Twitter API as provided by Twitter for functionalities in your Service that are substantially similar to a feature of the Twitter service and present this to your users as the default option.
D. not frame or otherwise reproduce significant portions of the Twitter service.
F. not use Twitter Content or other data collected from end users to create or maintain a separate status update or social network database or service.
https://dev.twitter.com/terms/ap...
@zemaj Thanks, James. Twitter's API terms can be interpreted in different ways so we took the risk because there's a real privacy problem with favorites
/ syndicate
FavGuard
FavGuard
FavGuard
Chargedesk
FavGuard