Hey Jodler, your version of the app is too old (Version 4.28.1)

Issue #23 closed
Tombone created an issue

Hey,

even when using your newest commit for version 4.28.1, thinks do not work out... If I simply try:

connection = OJOC.Connection.Connection(citycc='Berlin, DE')
recent = connection.recent_posts()
print recent['posts'][0]['message']

I only get: Hey Jodler, your version of the app is too old and won't be supported anymore👴🏼 Please update to the new and shiny Jodel and have fun✌️

Any idea what goes wrong?

Version 4.27.1 worked perfect...

Thanks!

Comments (12)

  1. Christian Fibich repo owner

    I could reproduce getting that sticky post, but I get it with 4.27.0 too. Are you able to post/comment/vote?

    Maybe some API requests changed slightly? Must be something like location update... I'll look into it but it'll take some time

  2. Benedetto Nespoli

    4.28.1 uses v.0.3 api also for /posts/*

    Examples:

    /api/v3/posts/location/combo
    
    /api/v3/user/config
    

    EDIT: actually /posts/:post_id/* is not using v.0.3 api, but v.0.2

  3. Benedetto Nespoli

    What I personally experimented with a proxy:

    Posts are initially retrieved with /api/v3/posts/location/combo , then they are updated using /api/v2/posts/location with the GET parameter 'after'.

    Calls to /api/v2/posts/location without the "after" parameter are marked as outdated.

  4. Tombone reporter

    So, Benedetto Nespoli, what are the explicit edits you suggest to make in the code?

    Thanks a lot.

  5. Benedetto Nespoli

    I suppose that something like this should work

    connection = OJOC.Connection.Connection(citycc='Berlin, DE')
    recent = connection.combo_posts()
    print recent['recent'][0]['message']
    
  6. Christian Fibich repo owner

    Thanks for figuring out @bennes.

    I now marked OJOC.connection.recent_posts() as deprecated and modified ojoc.py and nojoc.py to use combo instead

  7. Benedetto Nespoli

    @cfib90 I want to underline that the method it's not fully deprecated, as the app itself uses it.

    Actually the calls to that method without the after parameter are deprecated

  8. Log in to comment