Lemmy v0.19.0 is introducing some breaking changes that, if I add support for in Photon, will break compatibility with instances before v0.19.0. If I don’t add support for v0.19.0, instances with that version or higher will break. How should I proceed?

A: Keep an old version of photon available for people who need to use a pre-0.19.0 instance (medium difficulty)

B: Add a message to login saying the instance must be v0.19.0 or higher, nuke all backwards compatibility (easiest solution)

C: wait until most instances are on v0.19.0 to proceed with B

D: Add code to handle different versions (hardest solution)

I’d prefer that people be able to rely on Photon, and anything that prevents them from doing stuff on photon I see as a catastrophic issue. A looks the most appealing right now.

  • Krafting@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 year ago

    “A” seems okey, just have an unsupported version with no more updates and just focus on the compatibility with Lemmy 1.19.

    • ramble81@lemm.ee
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      1 year ago

      no more updates

      I see you like to live dangerously with a publicly exposed website that no longer receives security updates

      • Krafting@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Lemmy is a fast-moving piece of software and you should keep it updated anyway. It doesn’t get security update either

  • Shadow@lemmy.ca
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    I would just do B.

    I have photon set to auto update on lemmy.ca so it would break ours until I upgrade lemmy, but that still seems reasonable.

    Edit: I lied, I guess I never set that up after all. Still seems reasonable.

  • OsrsNeedsF2P@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    What is Photon? I found this linked from somewhere else in the fediverse, but there’s no sticky

  • FooBarrington@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I’d guess that this kind of thing will keep happening. Is D so hard because you don’t have any infrastructure in place for supporting different versions? Or because this change will be particularly hard?

    If it’s missing infrastructure, it will probably be worth it to spend the time once and implement it.

      • FooBarrington@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Then you should consider your long-term plans. If you will stay with option A long-term it’s no issue. If you ever decide to switch to option D, it will be easier the earlier you do it.