Timeline for feature complete v2 API

[Steven Pears]

I'm currently holding off releasing a new version of my app because I
want to be able to use the v2 API - but there are some large gaps in
terms of functionality (like/unlike as well as like info being the
most obvious from my users point of view)

Is there a rough schedule for when v2 will be feature complete
compared to v1? I think maintaining two API implementations would lead
to a risky release to a mobile device.

[Mahesh Asolkar]

+1

[HoLin]

+1

On Aug 3, 10:15 pm, Mahesh Asolkar <asol...@gmail.com> wrote:
> +1

[Steven Pears]

I received a personal response to this concerning the ability to still
use v1 API calls for the missing functionality. And that I was making
this seem like a big deal when in fact it isn't because Tumblr have
not marked v1 as obselete.

If I were maintaining a website I'd have no problem with this as I
would have immediate access to the raw code should I require any
changes. To maintain two API codebase for a deplplyed app requres I
maintain, support and debug two request/response mechanisms, two
serialization/deserialization mechanisms, two error handling
mechanisms and two sets of tests. With the kind of speed available to
mobile app developers at the moment in terms of version release
through an app store it's also a problem that every time the API does
get closer to feature complete I'm going to be releasing new updates
with no perceivable difference to the end user, but vastly improved
stablity. Plus the more code that is in one API allows any performance
increase or robustness in that codebase to be applied quickly across
the board.

Doubling the risk of failure to the app, or possibly worst, making the
app to appear at fault because some of the api calls are working and
some not, is a risk for an app maker, and not one I'm happy having to
make due to a new API release not being feature complete.

If being freature complete is not expected, this should not have been
marked as new in the engineering blog and it certainly shouldn't have
been marked as the de facto API in the documentation. Developers
expect like for like functionality with full backwards compatibility
or at least a list of breaking changes. I don't believe that's
unacceptable. I don't allow the code I release to do this in my
professional or personal endevours and I hold others to the same
level.

If I'm seen as overly vocal or critical it's because as a user and a
developer I want Tumblr to be the harness for a lot of great
functionality and I really think the new API solves a lot of problems
I've had so far. I just think the risk is too great at the moment.

[Derek Gottfrid]

Other than like/unlike what other features do you feel are missing?  Our goal is not to completely replicate functionality on the site but to provide a subset of core features. 

Also for those desperate for like/unlike it is available but the docs haven't been updated yet

api.tumblr.com/v2/user/like

api.tumblr.com/v2/user/unlike

It requires OAuth signed POST with "id" (post id) and "reblog_key"  

thanks, 

d

-- 

api lead // tumblr

[AJ]

On 8/4/11 9:11 PM, Derek Gottfrid wrote:
> Other than like/unlike what other features do you feel are missing?
> Our goal is not to completely replicate functionality on the site but
> to provide a subset of core features.

Hi Derek,

This is related to my e-mail to the group last night. Any chance we
could get authenticate api along with the authorize similar to what
Twitter supports?

Thanks,
AJ

[Joe Workman]

Has the timezone field been added back in?

I sent a mail about possibly having access to total tag counts. Do you think this is possible?

--
Cheers,
Joe

Joe Workman Developing cool things for the Mac... joeworkman joeworkman.net j...@workmanmail.com About.me

Get my vCard Sent from my 

[Derek Gottfrid]

This is not on the immediate roadmap.  If a different thread it would be interesting to hear the use case where this would be helpful. 

[Derek Gottfrid]

TZ info is not available in the /v2/user/info call currently but should return shortly

Generating a tag list for users is not on the roadmap.

[Joe Workman]

I created a thread on the tags yesterday with a use case…

So did you mean that the timezone field was not on the roadmap? I thought that it was planned on being added in the near future… 

--
Cheers,
Joe

Joe Workman Developing cool things for the Mac... joeworkman joeworkman.net j...@workmanmail.com About.me

Get my vCard Sent from my 

[Joe Workman]

Cool thanks… Here is my idea for tags… 

I would love to be able to query a user's account and get a response of every tag used in that User's posts and the counts for each of those tags. This would be awesome to allow us to create a tag cloud. 

--
Cheers,
Joe

Joe Workman Developing cool things for the Mac... joeworkman joeworkman.net j...@workmanmail.com About.me

Get my vCard Sent from my 

[Jay]

I would love this, too.

I use tags a lot, and it would be awesome to get all the tags used for a tumblr in order to filter posts by them.

[HoLin]

Hi Derek, thanks for your post.

I use the like/unlike api, it responses OK. the responsed body like:

{"meta":{"status":200,"msg":"OK"},"response":[]}

but i am not really "like" the post successfully. the post i "liked" not apear in my liked posts list.

any idea? 

--
Regards
HoLin

[Steven Pears]

Derek

That's fantastic news about the like/unlike API.

I think the only functionality that's missing now is like information
in the dashboard.

It's great to see such a fast response from the Tumblr team, thank you!

[Derek Gottfrid]

If you a users likes - 

api.tumblr.com/v2/user/likes Check the documentation to see if that covers what you need.

[Steven Pears]

Previously we could add a likes glad to the dashboard call to see if the posts had been liked or not - rather than a filter of just liked posts, that's the key difference.

Sent from my Windows Phone

---

From: Derek Gottfrid
Sent: 05/08/2011 12:44
To: tumbl...@googlegroups.com
Subject: Re: Timeline for feature complete v2 API

[HoLin]

I try like again, it works. Use v2 api & OAuth signed POST.

On Aug 5, 10:50 am, HoLin <holin...@gmail.com> wrote:
> Hi Derek, thanks for your post.
>
> I use the like/unlike api, it responses OK. the responsed body like:
>

> *{"meta":{"status":200,"msg":"OK"},"response":[]}*