2024-06-07 - Lemmy Release v0.19.4 - Image Proxying and Federation improvements
join-lemmy.org
  • iso@lemy.lolEnglish
    34·
    24 days ago

    Good to hear it’s out 🎉 I’m so hyped for the image proxy. Storing images permanently was costly.

  • db0@lemmy.dbzer0.comEnglish
    25·
    24 days ago

    Great stuff peeps! Looks like my future is very busy with having to do a complex pictrs upgrade and then a postgres and finally lemmy. Oof! 😅

    • Dessalines@lemmy.mlOPMEnglish
      141·
      24 days ago

      Thx! Let me know if the postgres upgrade helper script I provided has any issues.

        • Tiff@reddthat.comEnglish
          4·
          24 days ago

          The script will be useless to you, besides for referencing what to do.

          Export, remove pg15, install pg16, import. I think you can streamline with both installed at once as they correctly version. You could also use the in place upgrade. Aptly named: pg_upgradeclusters

          But updating to 0.19.4, you do not need to go to pg16… but… you should, because of the benefits!

  • Die4Ever@programming.devEnglish
    221·
    24 days ago

    In order to improve interoperability with Mastodon and other microblogging platforms, Lemmy now automatically includes a hashtag with new posts. The hashtag is based on the community name, so posts to /c/lemmy will automatically have the hashtag #lemmy. This makes Lemmy posts much easier to discover.

    this should be interesting

    for reference, this is what it looks like on Mastodon, the post to !announcements@lemmy.ml it gets the hashtag for announcements

    https://mastodon.social/@dessalines@lemmy.ml/112576601493225058

    it’s not really part of the message text, it’s separate

    image proxying also sounds good

    • Microw@lemm.eeEnglish
      6·
      24 days ago

      I’m pretty sure thats due to how mastodon renders hashtags at the end of a post. Not due to how Lemmy sends it.

  • Ben Matthews@sopuli.xyzEnglish
    17·
    24 days ago

    That’s great progress, thanks for all the work!
    Glad to see enhanced federation with rest of fediverse - a small detail : the link for ‘Automatically includes a hashtag with new posts’ should point to pull #4533 (not #4398 ) - should help discoverability from mastodon, especially if community tags become customisable.

  • davel@lemmy.mlEnglish
    131·
    24 days ago

    Mr. Dessalines and Principal Nutomic were in the closet making 19.4 and I used one of the pre-releases and the pre-release gave me Havana Syndrome and made me into a Manchurian Candidate!

  • jjjalljs@ttrpg.networkEnglish
    12·
    24 days ago

    I know pre 1.x.x is kind of a wild west for versioning but uh is there any logic to the version numbers here? I’d think a new feature would be a minor version bump, not patch

    • SorteKanin@feddit.dkEnglish
      26·
      24 days ago

      The convention in many Rust projects is usually that before 1.0, the patch version behaves like the minor version and the minor version behaves like a major version. So once there are breaking changes, they go to 0.20.0.

      • dan@upvote.auEnglish
        7·
        24 days ago

        This is the case with a lot of apps that follow SemVer, even though it’s not an official part of the spec. It’s not specific to Rust.

        The other common thing I see is that if it’s been at 0.x for a long time, the minor version number eventually gets “promoted” to a major version number once the app is stable. For example, React went from 0.14.x to 15.0.0.

    • Dessalines@lemmy.mlOPMEnglish
      161·
      24 days ago

      That’s my bad really. Currently we’re using the patch semver to denote non-breaking changes, and the minor for breaking.

      We’re holding off on a major release until the API reaches stable, which like all open source projects we’re reticent to do because then it puts a lot of pressure on us to match the standard of enterprise-level software developed by a large corporation.

      Even though lemmy has many thousands of monthly active users, we’re still really an beta-level software developed by a handful of people.

      • mke@lemmy.worldEnglish
        8·
        24 days ago

        Honestly, that strategy feels like the most sensible one, since the real world often does not (or can not afford to) care to wait for v1.0.0 before using software. It’s no wonder so many programming ecosystems have adopted it.

        I find it a bit of a shame it’s not part of the semver specification itself, which only states:

        1. (paraphrased) do whatever you want haha

        My point is, I don’t think that’s “your bad.” It’s just how it is, and the best there currently is. Unless you think there’s something that could’ve been done better, in which case I’m curious as to what, if you’re willing to share.