in particular:
X-Twittersenderid:
X-Twittersenderscreenname:
Nigel
http://tweet.linkky.com
bob.hitching wrote:
some events like 'new follower' generate an email message - you can
build a listener to react to those emails. there's even some useful
twitter headers included so you don't have
You'll know, trust me, having just got done for posting too many
hashtags We've been automatically tagging users' feeds, and posting
the resulting hashtags centrally on @linkkytags - Until the middle of
last night!
So, unless begging works (which it hasn't so far), we'll be pursuing
@secretbear did it first in the halcyon days of the PubSub Firehose...
I'd ask him
==
Why not encrypt the mail you send me? You never know who's looking.
If you use Firefox, why not use the FireGPG plugin to make it easy
Some testing help required for anyone interested. The theory is
automatic tagging of your Twitter feed via a series of hash tags placed
into your feed about every 20 tweets. The service takes literal tags
and non-literal themes into account to try to give a more rounded feel
of what's in
If you are looking to do something basic like that, then curl works
well. As a perl script:
#!/usr/bin/perl
my $VAR1=hello;
my $VAR2=bye bye;
my $response=`curl --basic --user test:water --data status=\aHello
world $VAR1 $VAR2. This is my first test tweet automatically posted from
a perl
I found an issue using the server example included in Net::Twitter
(oauth_webapp.pl).
Every time someone connected with the server, it re-used the same OAuth
token, until they actually signed up with the app. Well, not everyone,
once they've gone to the authorization URL, actually signs
on the list, keep the good work up!
On 10/21/09, Marc Mims marc.m...@gmail.com wrote:
On Oct 20, 4:28 am, Nigel Cannings nigelcanni...@googlemail.com
wrote:
I found an issue using the server example included in Net::Twitter
(oauth_webapp.pl).
Hi, Nigel. I'm the author of Net::Twitter. I'd
Thanks for those of you signed up (or tried to sign up) to test
http://tags.linkky.com
Well, if you saw my previous post on my Perl OAuth issues, you may have
realised that I managed to get no-one signed up (there were a few minor
problems entirely of my devising as well!)
Anyhow, without
About 4 hours ago, I started getting bizarre JSON errors from
Net::Twitter::Stream - Does anyone know if there has been a change at
the stream end?