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

    I just want to be clear that I’ve paid for Sync in various ways I think 3 or 4 times now and I’ll gladly pay for it again. Jerboa has been at least functional (10x better than when I first started using it a few months ago).

    But it’s Sync I want.

    • Toribor@corndog.uk
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 year ago

      Honestly I feel like I should donate to Lemmy apps I don’t even use. Sync will likely become my primary vehicle to the fediverse but the fact that I have a choice is the most important aspect. A healthy competitive app ecosystem is essential.

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

        I ended up buying pro of several reddit apps during my time there just to support the up and coming devs of those apps. Sync will most likely be my daily driver here, but I’d be happy to kick a few bucks towards each of the other Lemmy app devs and buy a pro version. It’s the least I could do to show support for the work they’ve put in so far.

  • lem_dart@lemm.ee
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    Enjoyed sync for reddit for basically the entire time I used it. Excited about sync for lemmy.

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

    Sync was the only Reddit client I could use. Tried all the others but man Sync hit the spot for me. Liftoff is decent but can’t wait for Sync!!

  • Neuron@lemm.ee
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    They should change the logo so blue is up and orange is down now

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

    I can’t wait, pre caching comments for offline use please!

  • Disgustoid@startrek.website
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Me: “Man, why is someone tempting us with a screenshot like this.”

    sees who posted this

    Also me: “We’re not worthy! We’re not worthy!”

    Day 1 purchase when it comes out. I can’t wait!

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

    v23.07.08-00.34 already? This dev really gets to business.

    • Orvanis@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      In all seriousness, is the Dev using the build date as the version number…? July 8th, 2023 at 12:34am - vYY.MM.DD-HH.mm

      Unusual approach for sure as you have no clue if it is a major version change or minor bug fixes.

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

        Using the date as a version number for an application that gets frequent updates is very standard. Most users will be expected to be on the latest version always.

        There’s even a website for it https://calver.org

        • Orvanis@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Thank you for the web link, TIL it is much more common than I was aware!

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

            Generally speaking, I find it easier and more intuitive to use. We use calver at work bc it seems pointless to identify if every week’s release is major / minor / patch etc. My thought is the latest is the greatest - if something goes wrong, it’ll be fixed in a later version ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

        • schnex@reddthat.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Interesting, I always found semantic versioning pretty useless, except for knowing that a new major release breaks existing APIs

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

            It’s great to get a quick context of the size of the change expected. That does require the developer numbering the release to appropriately version it though.