Alex,
I finally figured this out. As you probably guessed, was not an issue
with the Twitter API.
In case someone else winds up on this thread, here's what the issue
ended up being:
When using PHP CURL and doing a POST (vs. a GET), there are two ways
to pass in the POST parameters. One is as
Good suggestions. The fastest connection to mysql (if you're using
mysql, of course) will likely be via the mysqli extension API, and
with the mysqlnd driver. PDO is quite lightweight, though, so it
probably isn't a big slowdown point for you. It will use the mysqlnd
driver if you have it installe
It's possible that the cache of that URL hasn't expired since it was updated.
On Fri, Nov 14, 2008 at 08:35, Kevin Watters <[EMAIL PROTECTED]> wrote:
>
> In my friends_timeline.json for tweet 1005190499 I'm getting a
> profile_image_url value of
>
> http://s3.amazonaws.com/twitter_production/prof
Could you please provide an example of the failing request and response?
On Fri, Nov 14, 2008 at 23:56, Dharmesh <[EMAIL PROTECTED]> wrote:
>
> I'm having an issue posting status updates that start with an
> @someone.
>
> Posting updates that are not @someone replies seem to work just fine.
>
> T
any @replies
On Nov 15, 3:37 am, "Alex Payne" <[EMAIL PROTECTED]> wrote:
> Do you mean any @replies or just @replies to a specific username?
>
> On Fri, Nov 14, 2008 at 12:23, drupalot <[EMAIL PROTECTED]> wrote:
>
> > I've been using advanced search to create feeds from the public
> > timeline on
Thanks, hadn't thought of that. I'd actually be willing to lose those
few tweets with emails if it meant I could filter out all the
@replies. The project we're working on involves pulling in all tweets
that look like questions-- have a question mark in them, contain any
of the words "who what when
Make sure that you don't strip out @[texthere] when there is leading text a
like an email: [EMAIL PROTECTED]
On Sat, Nov 15, 2008 at 07:05, fastest963 <[EMAIL PROTECTED]> wrote:
>
> No, what you would have to do is run a REGEX or similar search for @
> [username] and if it returns false then proc
PHP Optimizations
PDO (http://www.php.net/pdo) is a must! Speeds up database
transactions
1) Store as much data as possible into database
2) Store data as arrays for each updating and fetching (see serialize)
3) Always use an index field in mysql
4) Limit echos/prints
Most Important: If connect
PHP Optimizations
PDO (http://www.php.net/pdo) is a must! Speeds up database
transactions
1) Store as much data as possible into database
2) Store data as arrays for each updating and fetching (see serialize)
3) Always use an index field in mysql
4) Limit echos/prints
Most Important: If connect
I'm having an issue posting status updates that start with an
@someone.
Posting updates that are not @someone replies seem to work just fine.
The error occurs when updating with an @reply to users that are
followers and not followers.
Let me get this out of my head - I will never implement it and raise
my kids at the same time...
The way I would like this to work if for one to generate a key/
password for the application and specify what things it can do (can
read my followers but cannot change them, cannot read my email, etc)
Did you maybe copy something wrong...
the first link is 64498715 and the second is 64499571 (notice the last
3 digits).
Can you provide that account name that you are using to login? It may
be removed or suspended? If not then alex or someone will have to take
a look because it would be a server problem. In the past however, I
got this message when I tried to use an account that was suspended.
No, what you would have to do is run a REGEX or similar search for @
[username] and if it returns false then process the data.
There is no way to omit results from the API standpoint.
Do you mean any @replies or just @replies to a specific username?
On Fri, Nov 14, 2008 at 12:23, drupalot <[EMAIL PROTECTED]> wrote:
>
> I've been using advanced search to create feeds from the public
> timeline on specific keywords and so forth. One thing I'd like to do
> is not pull tweets that
I've not changed that limit. Email me off-list with your username and
I'll investigate.
Search API requests are not subject to the 100 request per hour limit, no.
On Fri, Nov 14, 2008 at 09:55, Waitman Gobble <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> It seems like the follow limit changed. It used
16 matches
Mail list logo
