Spaz Spaz Desktop → Version 0.10

Comments and changes to this ticket

• 

  Matthew Turland July 10th, 2010 @ 10:10 AM

  • Milestone order changed from “0” to “0”

  A bit more exposition on this...

  The Twitter client API methods for this already exist in the codebase. The only thing that really needs to be done is to expose the functionality in the UI.

  Some people prefer the old style of retweeting, as that allows further commentary within the same tweet. When implementing this new method, continuation of support for the old one should be considered - some people prefer one over the other, some people vary in their preference. In that event, there may need to be a new UI element per tweet to allow either to be chosen or a new preferences setting to set which is used.

• 

  Josh Roesslein July 10th, 2010 @ 11:49 AM

  I think switching between old and new styles of re-tweeting should be automatic for the user.
  The new re-tweet API method should be used if the user re-tweets the status w/o any modification of the text.
  If the user should modify the text, then we would have to use old style re-tweeting.

• 

  Matthew Turland July 10th, 2010 @ 11:52 AM

  @Josh That would work, but how would you undo a retweet done through the API? Would you have to go to web for that?

• 

  Josh Roesslein July 10th, 2010 @ 11:58 AM

  I am pretty sure re-tweets can be treated like any other status. You just use the same
  destroy endpoint you would for a regular status.

• 

  Josh Roesslein July 10th, 2010 @ 12:03 PM

  Also we must make sure we switch to the home timeline resource instead of the friends timeline.
  This one includes re-tweets from the user's friends. Must also display re-tweets properly that
  we find in the timeline. User should be able to tell what is a re-tweet and who was the original author.

• 

  Ed Finkler July 10th, 2010 @ 12:25 PM

  Here's what I'd like to see for now:

  • Add a preference for kind of RT to use – either API supported, or "manual"/old-skool. If API type are selected, there's no user interaction other than just clicking the retweet action button. If old skool is selected, they work like they do now.

  • Having the method of RT-ing change seems to open up more code and more complexity. I'd rather avoid that atm. Maybe think about it in the future though, as an option for "power users".

  • There is no "undo RT" method in the API from what I can tell. Correct me if I'm wrong or it changes.

  We are already using the home_timeline for stuff now, btw.

• 

  Matthew Turland July 10th, 2010 @ 12:27 PM

  @Ed: Josh pointed out to me that retweets are assigned their own tweet identifiers, so the same API method for deleting a regular tweet should also work for a retweet.

• 

  Josh Roesslein July 10th, 2010 @ 12:30 PM

  Well I still think the automatic re-tweeting between old and new is the best route
  and isn't that complex. I think only power users will understand the difference while newer
  users will find it confusing and unsure why they can't edit their retweets.
  If we want to start out simple and just do it with an option for now, that's fine.
  We can automate the switching later on.

  Removal of re-tweets is done with the statuses/destroy endpoint. Re-tweets are like
  any other status, you can perform any statuses/ method on them AFAIK.

• 

  Ed Finkler July 10th, 2010 @ 12:59 PM

  I think you just agreed to do it, Josh!

  I think the default should be API RTs, done via single click. Potentially we could also have a menu pop-up when you click on the RT button to give you the option to RT, "Quote", or the like, to offer more sharing options. We can build a menu using the SpazMenu stuff we're working with in master right now.

• 

  Ed Finkler December 4th, 2010 @ 07:48 PM

  • State changed from “new” to “resolved”
  • Milestone set to “Version 0.10”

  super done.