2025-02-03 - Breaking Changes in Lemmy 1.0
join-lemmy.org
  • davel@lemmy.mlEnglish
    161·
    3 months ago

    A lot of these should not be called breaking changes. A new API is not a breaking change if the old API remains.

  • sabreW4K3@lazysoci.alEnglish
    9·
    3 months ago

    This is epic. I really hope Laurence can find some time to make Sync for Lemmy support it.

    • Dessalines@lemmy.mlMEnglish
      7·
      3 months ago

      Can’t give an ETA yet. I’ve got a few more back-end things to finish up, then @sleeplessone1917 and I will work on lemmy-ui.

      Then I also gotta work on getting jerboa updated also. So much work and so few developers.

  • toastal@lemmy.mlEnglish
    41·
    3 months ago

    1.0 would be the perfect time to have the code, bug tracker, etc. migrated off of Microsoft GitHub

      • toastal@lemmy.mlEnglish
        1·
        3 months ago

        Visibility to who? Normies? Search engines favoring corpo slop? You could make a readonly mirror if felt it necessary (it isn’t). If you have a modus operandi for you product or service, you would be better off choosing tools that align with those ideals. This instead says collaborator privacy/freedom is not our priority & we don’t actually follow our values.

        • OsrsNeedsF2P@lemmy.mlEnglish
          2·
          3 months ago

          I ran a large open source project, and when we switched to Gitlab the number of contributors dropped like a rock. Despite linking to our Gitlab repo everywhere, people weren’t finding it on Google or GitHub search, and those who did weren’t interested in creating a second account.

          We went from probably getting a new contributor every month to maybe getting a couple a year. It significantly slowed down progress.