forked from tweetledee/tweetledee
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathFAQ.txt
38 lines (23 loc) · 1.92 KB
/
FAQ.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
Frequently Asked Questions:
// INSTALL
--- What version of PHP do I need to use Tweetledee?
Version 5.3 or above for the RSS feed and standard JSON files. Version 5.4 or above for pretty printed JSON.
--- How do I get my Twitter OAuth tokens/keys?
You need to make a Twitter application
--- I don't make applications. Does that mean that I can't use Tweetledee?
Tweetledee acts as your application and allows you to access Twitter data through the Twitter API. You can designate the domain where you install and use Tweetledee as the application URL.
--- How do I make a Twitter application?
Please see the detailed guide on the home page of this documentation site
--- What is the URL for the new application page on the Twitter developers site?
https://dev.twitter.com/apps/new
// USE
--- I get the error "verify_credentials connection failure error". What is that?
It generally means that you exceeded the Twitter API rate limits. Please see this page for the Twitter limits. As of version 0.2.8 of Tweetledee, the error message that is displayed when you exceed the Twitter rate limits was changed to "Exceeded Twitter API rate limit".
--- What does the Twitter API limit of "15" mean?
You can access the Twitter API 15 times every 15 minutes for these API resources.
--- What does the Twitter API limit of "180" mean?
You can access the Twitter API 180 times every 15 minutes for these API resources.
--- What happens if I exceed the API limit for my account?
Twitter blocks your access to their API data until the remainder of that 15 minute block of time has elapsed. You will receive an error message if you continue to attempt to retrieve new data during this period.
--- How do I avoid exceeding my limit when I use Tweetledee?
Try caching your Twitter data and polling for new data every X seconds so that you do not exceed the limit that is in place for the API resource that you are using. Serve the cached data to your site's users.