[twitter-dev] Re: Can the Twitter API call me?
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 to parse the message body. Bob On Sep 12, 1:24 am, Duncan dun...@therecoveryplace.net wrote: Does Twitter have something in place where i can build a litener app that Twitter can HTTP/POST to when a new follower follows me or someone sends me a direct message, etc? Duncan
[twitter-dev] Re: Changes to Twitter TOS/Rules.
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 plan B which is to go all OAuth, and post the tags periodically to users' feeds so they're spread around all the different feeds. Not actually as socially useful, and it means we'll have to post the aggregated hashtags off-Twitter, but better than nothing... Nigel @ncannings http://tweet.linkky.com http://tweet.linkky.com/yourtwitteridhere Joseph Cheek wrote: out of curiosity, how can you tell if your account is flagged as spammy, and what can you do about it? Joseph Cheek jos...@cheek.com, www.cheek.com twitter: http://twitter.com/cheekdotcom John Kalucki wrote: This is taken from the Twitter Rules, not the TOS, so this isn't expressly against the TOS. Rather, this is one guideline of many that Twitter may use to determine if an account is spammy. If job postings are otherwise good and useful, I wouldn't fret too much. But, I'd also expect that you just might, on rare occasion, may have to deal with getting your accounts unflagged as spammy. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Sep 15, 7:58 am, HardipSingh mr.hardip.si...@gmail.com wrote: I am curious how the following rule impact those that are auto- tweeting job links to #jobs and the other twitter job boards. * If your updates consist mainly of links, and not personal updates; Does this mean that we are in violation of this rule if I have an account that is primarily responsible for tweeting job links? Thanks in advance for your time. ~ H
[twitter-dev] Re: how are the ten trends born?
@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 (http://getfiregpg.org) Get my key from: http://keyserver.pgp.com/ == On Thu, Oct 1, 2009 at 4:20 PM, Martin Dudek goosegoesgro...@gmail.com wrote: Good morning wonder if somebody knows how twitter determines the ten trends it declares every five minutes? Is this a pure word/phrase frequency algorithm or some more complexity behind. Thanks martin
[twitter-dev] AutoHashTags
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 your feed, and using hashtags, let others know too. There's also a little trending graph that can be adjusted by time and sensitivity (and which will probably break if it is put to too much use!) http://tags.linkky.com - If it breaks, let me know, and I'll try to fix it...
[twitter-dev] Re: basic help needed on connect to TWITTER and send a tweet with PERL
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 script\ http://twitter.com/statuses/update.xml`;
print $response;
Naturally, if you want to start doing more complex stuff, especially
OAuth, then the CPAN libraries are an enormous help.
Nigel
http://tags.linkky.com
@secretbear
apfelmaennchen wrote:
I really find it difficult to understand documentation how to code a
TWITTER-API in perl. But with a bit start-help, I think I'll be able
to proceed.
Can somebody help me with a sample PERL-code:
From within a PERL script ( which has two variables filled with
strings. names of those VARS are $VAR1, $VAR2) I want to
a) connect to twitter (lets assume username = test, password =
water)
b) send a tweet Hello world $VAR1 {space} $VAR2. This is my first
test tweet automatically posted from a perl script.
c) disconnect from twitter
Maybe you also can give a command-reference, something like perl
TWITTER API in a nutshell.
Very many thanks for your help, Alex
[twitter-dev] Perl OAuth - updated example
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 up, so fairly quickly, the token becomes stale, and then no-one can sign up. My fault for having an app no-one wants to use, perhaps... It's possible it was just me, but in case anyone else has the same issue, I've posted an updated example at http://tags.linkky.com/oauth_webapp.pl It exists only to authenticate (I've taken out the last tweet subroutine as the cookies are now gone), and to add the access tokens to a MySQL DB - Obviously, it can be updated to include any storage method Nigel http://tags.linkky.com
[twitter-dev] Re: Perl OAuth - updated example
Sorry, I should have said that it is the authorization url that remains the same until a user actually accepts your application. It is the authorization url that becomes stale if reused, or unused for a period of time. Access tokens, as you quite rightly say, don't expire unless revoked. I experimented by signing up from one PC, then neither accepting nor denying the application, moving to another PC and signing up again. I got the same authorization url on both PCs, so it's not a local cookie issue. Hope that is a better explanation, and might I say on behalf of all the Perl hackers 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 like to update the sample included with the distribution to fix the problem you encountered, but I don't completely understand your explanation. 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 up, so fairly quickly, the token becomes stale, and then no-one can sign up. My fault for having an app no-one wants to use, perhaps... Can you explain in more detail what you mean by the token quickly becoming stale? If I'm not mistaken, access tokens remain valid until the user explicitly revokes them. -Marc -- == 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 (http://getfiregpg.org) Get my key from: http://keyserver.pgp.com/ ==
[twitter-dev] The testing that never was
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 wishing to clog up the list with my woes, I would be grateful to you, or anyone else who fancies a try, to pop over to the site, and give it a whirl. You can just go straight to http://tags.linkky.com:2908 to sign up, but you probably want to know what you're signing up to first... Thanks Nigel
[twitter-dev] Net::Twitter::Stream - Sudden JSON issues
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?
