I'm trying to re-integrate comments back into my app but have come up
against a couple of issues with the 2.0 API.
Firstly calls to story.getComments seem to return duplicate comments.
For example if 20 comments are returned for a story, there will be 10
comments repeated twice. Is this an error with the API?
Also, in the 1.0 API, you would get a list of comments with
story.getComments and replies for each would be fetched with a call to
comment.getReplies passing the comment ID. In 2.0, it looks like some
of the replies are supplied in the call to story.getComments, tied
together by a thread ID. Does that mean the comment.getReplies method
is redundant? Will all replies be returned in this call?
> I'm trying to re-integrate comments back into my app but have come up
> against a couple of issues with the 2.0 API.
> Firstly calls to story.getComments seem to return duplicate comments.
> For example if 20 comments are returned for a story, there will be 10
> comments repeated twice. Is this an error with the API?
> Also, in the 1.0 API, you would get a list of comments with
> story.getComments and replies for each would be fetched with a call to
> comment.getReplies passing the comment ID. In 2.0, it looks like some
> of the replies are supplied in the call to story.getComments, tied
> together by a thread ID. Does that mean the comment.getReplies method
> is redundant? Will all replies be returned in this call?
> On Jan 3, 9:25 am, Pete Callaway <pete.calla...@gmail.com> wrote: >> Hi and happy new year all.
>> I'm trying to re-integrate comments back into my app but have come up >> against a couple of issues with the 2.0 API.
>> Firstly calls to story.getComments seem to return duplicate comments. >> For example if 20 comments are returned for a story, there will be 10 >> comments repeated twice. Is this an error with the API?
>> Also, in the 1.0 API, you would get a list of comments with >> story.getComments and replies for each would be fetched with a call to >> comment.getReplies passing the comment ID. In 2.0, it looks like some >> of the replies are supplied in the call to story.getComments, tied >> together by a thread ID. Does that mean the comment.getReplies method >> is redundant? Will all replies be returned in this call?
>> Cheers >> Pete
> -- > You received this message because you are subscribed to the Google Groups "Digg API" group. > To post to this group, send email to diggapi@googlegroups.com. > To unsubscribe from this group, send email to diggapi+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/diggapi?hl=en.
> > On Jan 3, 9:25 am, Pete Callaway <pete.calla...@gmail.com> wrote:
> >> Hi and happy new year all.
> >> I'm trying to re-integrate comments back into my app but have come up
> >> against a couple of issues with the 2.0 API.
> >> Firstly calls to story.getComments seem to return duplicate comments.
> >> For example if 20 comments are returned for a story, there will be 10
> >> comments repeated twice. Is this an error with the API?
> >> Also, in the 1.0 API, you would get a list of comments with
> >> story.getComments and replies for each would be fetched with a call to
> >> comment.getReplies passing the comment ID. In 2.0, it looks like some
> >> of the replies are supplied in the call to story.getComments, tied
> >> together by a thread ID. Does that mean the comment.getReplies method
> >> is redundant? Will all replies be returned in this call?
> >> Cheers
> >> Pete
> > --
> > You received this message because you are subscribed to the Google Groups "Digg API" group.
> > To post to this group, send email to diggapi@googlegroups.com.
> > To unsubscribe from this group, send email to diggapi+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/diggapi?hl=en.
Any updates on the issue with getting a story's comments? While it
looks like the duplicates issue has been resolved, I can't get any
more than the first result set. Including a cursor in the request
returns an empty results set.
> On Wed, Feb 2, 2011 at 12:59 PM, Pete Callaway <pete.calla...@gmail.com> wrote:
> Hi Will
> Any thoughts on this or my other questions?
> Cheers
> Pete
>On Feb 2, 9:03 pm, Will Larson <wlar...@digg.com> wrote:
>>That's bewildering. I'll take a look and get back to you shortly!
>>Thanks,
>>Will
>>On Wed, Feb 2, 2011 at 12:59 PM, Pete Callaway <pete.calla...@gmail.com> wrote:
>>> Hi
>>> Is there anyone from Digg who could respond to this one? Even just to
>>> say "it's broke"?
>>> If it helps, an example request that shows doubled comments is
>>>http://services.digg.com/2.0/story.getComments?story_id=2011020118502...
>>> Cheers
>>> Pete
>>> On Jan 3, 9:25 am, Pete Callaway <pete.calla...@gmail.com> wrote:
>>>> Hi and happy new year all.
>>>> I'm trying to re-integrate comments back into my app but have come up
>>>> against a couple of issues with the 2.0 API.
>>>> Firstly calls to story.getComments seem to return duplicate comments.
>>>> For example if 20 comments are returned for a story, there will be 10
>>>> comments repeated twice. Is this an error with the API?
>>>> Also, in the 1.0 API, you would get a list of comments with
>>>> story.getComments and replies for each would be fetched with a call to
>>>> comment.getReplies passing the comment ID. In 2.0, it looks like some
>>>> of the replies are supplied in the call to story.getComments, tied
>>>> together by a thread ID. Does that mean the comment.getReplies method
>>>> is redundant? Will all replies be returned in this call?
>>>> Cheers
>>>> Pete
