Freelancer
Twitter posting app
Twitter posting app is project number 428000
posted at Freelancer.com. Click here to post your own project.
Status: Cancelled
Selected Providers: -
Budget: $750-1500
Created: 05/01/2009 at 17:51 EDT
Bid Count: 25
Average Bid:
$ 1213
06/30/2009 at 17:51 EDT
Project Creator:
SamsonJr2
Employer Rating: 
(2 reviews)
Description
I am looking to build an application that interfaces directly with twitter.com. This application will send post to twitter in care of the user. A few features will include: sms and email posting. No picture handling, strictly text based.This will require:
- knowledge of twitter api
a) finding followers by user
b) then by date range
c) etc...
- membership database
a) email address as username
b) password
c) twitter username
d) twitter password
e) device (mobile phone, etc..)
f) track post history
- website design and development
a) home page/about (with login fields)
b) account page
c) post page
d) administration page (no visible on front end)
e) ad space placement
f) clean web and simple 2.0 look
g) CSS
- Details
a) posting will follow a default schedule
b) the default schedule can be overwritten by the user via UI, email or SMS.
c) posting logic must adhere to 140 char rule
- sms/email
a) all devices will require authorization via email notification
b) email post will use the subject line
c) sms post will use the message of course
- schedule override
a) UI "Post Now button"
b) email and sms keyword: "now"
- end result twitter post
a)
"message will be displayed on twitter"
less than 5 seconds ago from "application name"
- hosting will be by godaddy.com
Additional information submitted:
05/01/2009 at 20:27 EDT:
Please provide examples (links to sites are fine as well as some screen shots) of your work also touch base on some of the interface projects you may have worked on in respects to twitter.com.
There will be two candid messages one for the standard schedule and another for the override which will need to be subtracted from the 140 char count. In addition having a third for custom messages will be a plus.
The message are essentially for calling out other users.
Scheduled post
"blah blah blah @person1 @person2 @person3 @person4 #hastag"
less than 5 seconds ago from "application name"
Override post
"blah blah blah @person1 @person2 @person3 @person4 early #hastag"
less than 5 seconds ago from "application name"
Custom post
"custom message @person1 @person2 @person3 @person4 #hastag"
less than 5 seconds ago from "application name"
Say for example if the @person4 causes the limit to be exceeded then the application logic should remove it and then reuse it on the following post and so-on and so forth until all of the posting is completed.
So if the user was planning on sending out a mass message then the application would need to queue up the post accordingly then post the messages one after another.
All while conforming to the 140 char.
05/07/2009 at 6:43 EDT:
This application is not intended for Advertisement submissions. This is intended for current users of twitter to help automate processes. As far as the email and SMS goes the site will not broadcast emails or SMS. The purpose is for the site to accept emails and SMS on behalf of the user. Essentially giving the users different posting options.
For example joeuser@domain.com will send an email to the site. The site will need to be able to 1) accept the email and associate it to the appropriate user account 2) read the subject line 3) process the request 4) post on behalf of the user.
The SMS should work similarly the user would send a text to the site and the will need to 1) accept the message and associate it to the appropriate user account 2) read the message 3) process the message 4) post on behalf of the user.
05/07/2009 at 6:44 EDT:
This application is not intended for Advertisement submissions. This is intended for current users of twitter to help automate processes. As far as the email and SMS goes the site will not broadcast emails or SMS. The purpose is for the site to accept emails and SMS on behalf of the user. Essentially giving the users different posting options.
For example joeuser@domain.com will send an email to the site. The site will need to be able to 1) accept the email and associate it to the appropriate user account 2) read the subject line 3) process the request 4) post on behalf of the user.
The SMS should work similarly the user would send a text to the site and the will need to 1) accept the message and associate it to the appropriate user account 2) read the message 3) process the message 4) post on behalf of the user.
Provider Rating
