As it is now, Mlem also supports the ancient v1 of the API. Pretty much the only instance that still uses this version is Hexbear. All other instances use v3.

Dropping support for v1 would mean much less maintenance on my part, and would mean that updates would come out faster and would be less buggy.

On the other hand, Hexbear is probably the largest single instance.

Even now, Mlem doesn’t have the same level of support for both API versions; in v1, for example, Mlem doesn’t show user avatars (or any avatars for that matter). So overall, v1 of the API is much more limited, and not properly tested.

Is there anyone who uses Hexbear? Should Mlem have so much more code to support just one instance? Please share your thoughts!

  • nki@feddit.ch
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    Has v1 gone out of development for years? I’m down for dropping it, maintenance is a burden

  • Tyler Wolf@lemmy.ml
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I agree that v1 should be dropped, even if some instances haven’t upgraded, they should try and stay current with the standard, and dropping v1 does provide an incentive. I agree with the other comment that an alert about how your server doesn’t support v3 is good.

  • lFenix@lemmy.mlOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Thank everyone for your ideas! I dropped support for v1 in the latest version and you now get this alert if you try to add a v1 instance:

    v1 error

    • Jeff@beehaw.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Perfect! The message is simply what all other devs try to juggle which is the most support for the people while also not killing themselves. Put a tip jar link in there too, I’ll be happy to throw money your way.

  • Jeff@beehaw.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Drop v1 but leave a single alert that says sorry but the server you’re on hasn’t updated to v3 yet.