I'm not sure if this is a problem with my code, the libraries I'm
using (perl Net::Twitter::Role::OAuth) or something else entirely.
My program gets a request token, shows the user the website URL, and
waits for the pin.
If they enter the pin correctly, all it well, I get an access token.
If the
I thought it might be by design, but couldn't find that mentioned
anywhere. I guess it is necessary to prevent apps guessing the pin,
though it may be annoying for users.
I'm almost ready to release a desktop app using OAuth. It's written
in Perl, so anyone can read the source.
Should I remove my consumer token and secret and make people get their
own? Or is it safe to distribute?
.google.com/group/twitter-development-talk/browse_thread...
>
>
>
> - h
>
> On Fri, Jul 10, 2009 at 10:05, Grant Emsley wrote:
>
> > I'm almost ready to release a desktop app using OAuth. It's written
> > in Perl, so anyone can read the source.
>
> > Should
It's a cool little program.
With the rate limiting - the requests should come from the viewer's IP
address, so rate limiting shouldn't be a problem. At worst,
individual users viewing it 20,000 or whatever time an hour would see
an error, everyone else would be fine.
http://apiwiki.twitter.com/Libraries
The very first category is for flash...
On Jul 13, 2:56 am, nite21 wrote:
> hi all
> i want to send data from flash to twitter
> is that possible
>
> thanks
I think the limit is only on the API. I suppose there are/were
conditions where duplicates would get posted, and this prevents that
from happening.
Easiest thing to do: Have your program put a timestamp in the
message, so instead of "You have a new update", put "11:57:01 You have
a new update"
So you want to encode text as an image...then translate the image to
text, send through twitter, translate the text to an image...and then
decode the QR code back to text?
I have no idea why you would want to do that. There must be an easier
way. Convert the QR code back to text and send via twi
It will improve the security of your account since it won't be sending
username/password in plaintext anymore.
It's not that much more complicated to do. In fact, if you are just
doing it for one account, you can run the sample code for oauth, write
down the access token and secret, and just har
On Jul 26, 10:06 pm, Francis Shanahan
wrote:
> I realise there are limits on the number of times an application can
> call into Twitter in a given time period.
>
> In the course of my testing though I tend to fire off a lot of
> requests, nothing crazy just probably 1 per minute as I'm clicking
Require people to follow you before they can use the service?
On Jul 27, 10:10 am, Andres B wrote:
> Hi, I'm having some trouble sending messages to the group, so I'll
> break it down in a couple different messages.
>
> I developed muuter.com and my users can send mute commands through DM
> i.e.
OAuth isn't perfect yet. However, it is better from one stand point:
If I sign up for a website or program with my twitter password, and it
does bad things, I have to change my password in EVERY twitter program
I use. With OAuth, I can just block your app.
On Jul 28, 9:08 am, Duane Roelands wr
Locked out of authenticated resources for that account, or will that
IP not be able to login to any account?
On Jul 29, 1:14 pm, Doug Williams wrote:
> Ray,For clarity, we will roll back the current restriction of 15 calls per
> user per hour to account/verify_credentials, and implement the prop
Perhaps a better approach to the lockout:
Lock the account for x minutes after 15 *unique* bad passwords. So if
the user changes their password, and another program keeps trying with
their old password, that only counts as 1 attempt.
It still only gives them 15 guesses, but would cause fewer loc
14 matches
Mail list logo
