Yes, I have a Twitter account here. Until August 31st I was using a "direct method" using a username and password pair, the code of which was directly embedded into the application I used to post new stores to the Free Fire Zone, which went through the application programming interface (API).

It was quick, easy and worry free. But now, a little more than a year later, Twitter is implementing security measures to make it a little harder to crack their security. As a result, none of the updates from new stories posted after August 31st were posted to Twitter. Plus, and as an added bonus, any new updates will have to be done manually until I can rewrite the embedded code using the new oath implementation.

Fun, huh?

I spent a good deal of last night reading the application programming interface, how it will work and how to fit applications into the oauth security scheme.

I can see all kinds of cool methods of locking down Twitter updates including rotating HMAC, MD5 and SHA encryption. The problem is that Twitter expects a server to receive their reply upon authentication, and that is where security can potentially get dicey.

My decision is whether I should program a script to receive the reply, or to program a net application to listen to a specific non-privileged port.

Being lazy, I like the idea of just pounding out a perl script to receive the reply over http, however, the script would have to tied to a single URL, and it would have to have a signed SSL certificate to work securely.

The net application, then, would be a good alternative. You post a story and as a result, it starts up a server daemon which waits for the reply from Twitter, then on reception, dies until the next story is posted.

Secure, to be sure and I like that, except I have zero experience programming net applications and daemons.

So until I can make a decision, I guess I will posting to Twitter manually, not updating until I get sick and tired of posting manually, as well as have the time to do the actual programming.


It has been 4968 days since this story was posted.
Discussion threads close after five days.
Sorry...
Return to the Free Fire Zone

See the full, archived discussion