Twitter API 1.1 lists

[Daniel Kreuter]

Ok just had a quick look at both returned JSON objects, they look
quite similar so I will have a quick test later and see if it works.

So before release of 1.4 I will have a look at it.

On Thu, Aug 1, 2013 at 9:14 AM, Daniel Kreuter
<daniel.kreuter85 at gmail.com> wrote:
> Hi Mehrdad,
>
> sorry for not hearing anything from me so far, I've been quite busy
> over the last weeks.
>
> From my pov releasing without working lists would be fine, I don't
> know how many people use this feature at all (I didn't know that lists
> existed until the bug report)
>
> If someone wants to step up and fix it before the release here's what
> I remember:
> As already mentioned on this thread the api call has changed. The new
> call needs different parameters than the old one (which is the easy
> part).
> I don't know if the returning JSON is the same as used for the
> timelines, this needs to be checked. If they are the same, than this
> would be easy to do.
> Currently the jobs are queued in a list and when the timelines are
> updated, each queued job will be worked on. When the returned JSON are
> the same for lists and the other timelines, no change needed here.
> If they differ, we would need something different for the lists.
>
> I will see if I find the time this weekend to have a deeper look at this.
>
> Greetings
>
> Daniel
>
> On Thu, Aug 1, 2013 at 4:26 AM, Mehrdad Momeny <mehrdad.momeny at gmail.com> wrote:
>> Any update Daniel?
>> How about releasing current version without Lists for now. it at least works
>> for other things!
>>
>> Regards,
>> Mehrdad
>>
>>
>> On Thu, Jul 11, 2013 at 12:07 AM, Mehrdad Momeny <mehrdad.momeny at gmail.com>
>> wrote:
>>>
>>> How can I help you? I can't get it from your message :/
>>>
>>>
>>> On Tue, Jul 9, 2013 at 8:44 PM, Daniel Kreuter
>>> <daniel.kreuter85 at gmail.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> thanks for the information.
>>>> Yeah the authorizationHeader method was actually in there, what I
>>>> didn't know was that the OAuth tool didn't like GET parameters.
>>>>
>>>> I had a look at the GET lists/statuses this morning and this piece
>>>> needs some more work than I thought since the API is totally different
>>>> from the one used by the other timeline api calls.
>>>> I will do it in a new method. I just don't know how to do the actual
>>>> call yet, since we want to update the list timelines when we start the
>>>> application or manually want to update the timelines.
>>>>
>>>> Cheers
>>>>
>>>> On Sun, Jul 7, 2013 at 5:50 AM, Mehrdad Momeny <mehrdad.momeny at gmail.com>
>>>> wrote:
>>>> > Hi Daniel,
>>>> > It fixed, as you already seen the commit ;)
>>>> > But for next step, it seems that the method to fetch a list timeline is
>>>> > changed, please fix this one :)
>>>> > https://dev.twitter.com/docs/api/1.1/get/lists/statuses
>>>> >
>>>> > And one note: we have a function(authorizationHeader()) in
>>>> > TwitterApiMicroBlog class which get account, url and params, and create
>>>> > the
>>>> > authorization header string. so we don't need to do OAuth stuff
>>>> > everywhere,
>>>> > just use it.
>>>> >
>>>> > Cheers,
>>>> > Mehrdad
>>>> >
>>>> >
>>>> > On Thu, Jul 4, 2013 at 5:01 PM, Mehrdad Momeny
>>>> > <mehrdad.momeny at gmail.com>
>>>> > wrote:
>>>> >>
>>>> >> I will check this method on weekend :)
>>>> >>
>>>> >> Regards,
>>>> >> Mehrdad
>>>> >>
>>>> >>
>>>> >> On Thu, Jul 4, 2013 at 4:50 PM, Daniel Kreuter
>>>> >> <daniel.kreuter85 at gmail.com> wrote:
>>>> >>>
>>>> >>> Hi,
>>>> >>>
>>>> >>> Mehrdad, can you check with the OAuth Tool what could be the problem
>>>> >>> in microblogs/twitter/twittermicroblog.cpp and the method
>>>> >>> fetchUserLists? I changed the url to the appropriate one used by the
>>>> >>> twitter api but get the above error and I don't know why, the OAuth
>>>> >>> signature looks ok for me.
>>>> >>>
>>>> >>> Cheers
>>>> >>>
>>>> >>> On Mon, Jul 1, 2013 at 6:18 PM, Daniel Kreuter
>>>> >>> <daniel.kreuter85 at gmail.com> wrote:
>>>> >>> > Hi,
>>>> >>> >
>>>> >>> > I'm currently working on the not working lists for the twitter api
>>>> >>> > change and
>>>> >>> > get an error from twitter from which I don't understand why I get
>>>> >>> > it.
>>>> >>> > If I lookup a user's lists (in this case xardas008 which is me) I
>>>> >>> > get
>>>> >>> > the
>>>> >>> > following JSON object:
>>>> >>> > {"errors":[{"message":"Could not authenticate you","code":32}]}
>>>> >>> >
>>>> >>> > So it seems that something with the OAuth token may be wrong at
>>>> >>> > this
>>>> >>> > place. I
>>>> >>> > checked the code but it seems to look right.
>>>> >>> >
>>>> >>> > Any ideas?
>>>> >>> >
>>>> >>> > Cheers
>>>> >>> >
>>>> >>> > Daniel
>>>> >>> _______________________________________________
>>>> >>> Choqok-devel mailing list
>>>> >>> Choqok-devel at kde.org
>>>> >>> https://mail.kde.org/mailman/listinfo/choqok-devel
>>>> >>
>>>> >>
>>>> >
>>>
>>>
>>