RemoteTweet: A secure and easy way to integrate Twitter using PHP

I have just released my RemoteTweet class on my website www.remotetweet.com

I don't think I have much to say on here as the website says it all really. This is my first class I have released, so maybe you could give me some tips on how to advertise?

Thanks,
Sam.

 

You can submit it to phpclasses.org.

 

Thanks for the advice, I've just submitted it. Hopefully this will get it recognized.

 

Also submit to hotscripts.com php.resourceindex.com etc.

 

Thanks for the tip guys, my submissions are all pending at the suggested websites!

Any comments on the script itself?

 

The only questionable thing is the ob_start() and session_start() on top of your class...

 

Why is that questionable? The class uses sessions to store the oAuth tokens, and ob_start() is to stop header cache errors.

 

I just think it's doing too much this way, why would it try fixing header cache errors? Does it write anything using echo etc.?

 

Why on earth is it doing too much? Do you have a problem with it stopping errors?

 

That's fine, I didn't mean to offend you, you asked and I thought you wanted to hear what I thought, so that's what I think...

I think the main script that is calling the class should do all these things.

Good Luck

 

It's personal preference really, it means for easier installation and usage if the class can do as much as possible. That's what I really want from RemoteTweet. Ease for others and myself to program twitter applications.

 

You call ob_start() where is ob_end_clean()?

 

I never knew ob_end_clean() was necessary?

 

Ok, no offense I just want to help you but...

Most of the people who want to use something like your class develop communities and want to give their users these abilities and your class doesn't do the job right because I'm not going to make a config.php for every single user. User and pass must be determined at run-time.

If you think someone is going to use your class to use twitter for herself/himself, that's wrong because people will simply use Twitter itself.

Also including your class means that you mess up my output buffering by calling ob_start and not releasing it and also calling session_start() which I have probably done already.

With all that said, I don't think anyone serious is going to use your class because it has fundamental design issues and they start with config.php which then are followed by session_start and ob_start naturally.

You are a good programmer though but architecture is tricky and takes time to master. I'm not a master either...

 

You obviously don't understand the config.php part of the class. That's for the application itself, that does not include usernames or passwords; in that file are the keys which allows the application to use Twitter's API for login.

I see what you're saying about session_start(), are you suggesting I should put it in the usage guide? Also, I'm sure if someone wanted to use my class enough, they'd make their own modifications to suit their style.

However, next time, please review my code before you start making assumptions...