News
join-lemmy.org

Its been a long time coming 🥳 .

Excerpt from the link:

Major Changes

Language Tags

Content can now be tagged to indicate the language it is written in. These tags can be used to filter content, so that you only see posts in languages which you actually understand. Instances and communities can also specify which languages are allowed, and prevent posting in other languages.

In the future this will also allow for integrated translation tools.

Comment trees

Lemmy has changed the way it stores comments, in order to be able to properly limit the comments shown to a maximum depth.

Included are proper comment links (/comment/id), where you can see its children, a count of its hidden children, and a context button to view its parents, or the post.

Featured posts

Admins and mods can now “feature” (this used to be called “sticky” ala reddit) posts to the top of either a community, or the top of the front page. This makes possible announcement and bulletin-type posts.

Special thanks to @makotech for adding this feature.

Federation

Lemmy users can now be followed. Just visit a user profile from another platform like Mastodon, and click the follow button, then you will receive new posts and comments in the timeline.

Votes are now federated as private. This prevents other platforms from showing who voted on a given post, and it also means that Lemmy now counts votes from Mastodon.

This release also improves compatibility with Pleroma. If you previously had trouble interacting between Pleroma and Lemmy, give it another try.

We’ve extracted the main federation logic into its own library, activitypub-federation-rust. It is open source and can be used by other projects to implement Activitypub federation, without having to reinvent the wheel. The library helps with handling HTTP signatures, sending and receiving activities, fetching remote objects and more.

Other changes

  • Admins can now purge content and pictures from the database.
  • Mods can distinguish a comment, “stickying” it to the top of a post. Useful for mod messages and announcements.
  • Number of new / unread comments are now shown for each post.
  • Lemmy now automatically embeds videos from Peertube, Youtube and other sites which provide an embed link via Opengraph attribute.
  • You can give your site “taglines”, short markdown messages, which are shown at the top of your front page. Thanks to @makotech for adding this.
  • You can now report private messages.
  • Most settings have been moved from the config file into the database. This means they can be updated much easier, and apply immediately without a restart.
  • When setting up a new Lemmy instance, it doesn’t create a default community anymore. Instead this needs to be done manually.
  • Admins can choose to receive emails for new registration applications.
  • An upgrade of diesel to v2.0, our rust -> postgres layer.
  • Salamander@mander.xyz
    16·
    2 years ago

    Thank you for the great work that you are doing!

    This update has a lot of very neat features that I’m excited to play with!

  • Dessalines@lemmy.mlOPM
    14·
    2 years ago

    Also I apologize that the upgrade here took longer than expected. It was a massive conversion of comments to a different form, that had to work for several hundred thousand historical comments.

  • nachtigall@feddit.de
    10·
    2 years ago

    Great update again. I’m most excited about the embedded videos!

    Will these language tags eventually be extended for custom tags (ala Reddit flairs)?

  • seahorse [Ohio]AEnglish
    5·
    2 years ago

    You can give your site “taglines”, short markdown messages, which are shown at the top of your front page.

    What is considered the Front Page?

  • Jakob :lemmy:@lemmy.schuerz.atDeutsch
    5·
    2 years ago

    And i tested federation with pleroma. This is a Posting in Pleroma in my lemmys testcommunity

    and this comes in lemmy

    It works, but not very good. “TEST von pleroma” is set as “Subject” in Pleroma, but it ist not recognized in Lemmy. Pleroma has a Subject. Mastodon not.

  • Arthur Besse@lemmy.ml
    5·
    2 years ago

    🎉 thanks to the developers and everyone who helped!

    one bug i noticed after the upgrade: my notifications page shows unread notifications for (what i guess is) every reply i’ve ever received which was later deleted. the count in the bell icon only reflected the actual new unread notifications I had received since I last looked, but when i click to view my unread notifications then all of these old ones about deleted messages appear to be unread now.

  • Jakob :lemmy:@lemmy.schuerz.atDeutsch
    5·
    2 years ago

    I faced another thing…

    Almost all of my joined communities are now not following, just pending…

    I have to cancel the following-request and follow again. This happens after upgrade to 0.17.0

    • Jakob :lemmy:@lemmy.schuerz.atDeutsch
      4·
      2 years ago

      First i see this and click to “Subscribe pending”

      then i have to click “Subscribe”

      and then, the subscription was successful.

      but i was subscribed at all these communities before the upgrade.

    • Dessalines@lemmy.mlOPMDeutsch
      2·
      2 years ago

      There’s an open issue for that in Lemmy, we’re deciding the best way to solve it.

          • Jakob :lemmy:@lemmy.schuerz.atEnglish
            2·
            2 years ago

            @nutomic@lemmy.ml Here is the WARN-Message from lemmy-Container

            lemmy_1     | 2023-02-03T15:14:29.914510Z  WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Fetched remote object https://pawoo.net/users/DarakuNakare which was deleted
lemmy_1     |    0: lemmy_server::root_span_builder::HTTP request
lemmy_1     |            with http.method=POST http.scheme="http" http.host=lemmy.schuerz.at http.target=/inbox otel.kind="server" request_id=e2e6c977-464f-43b3-8a3c-0816683afe74 http.status_code=400 otel.status_code="OK"
lemmy_1     |              at src/root_span_builder.rs:16
lemmy_1     | LemmyError { message: None, inner: Fetched remote object https://pawoo.net/users/DarakuNakare which was deleted, context: "SpanTrace" }
lemmy_1     | 2023-02-03T15:14:52.544795Z ERROR lemmy_server::api_routes_websocket: Error during message handling language_not_allowed: language_not_allowed
lemmy_1     |    0: lemmy_api_crud::comment::create::perform
lemmy_1     |            with self=CreateComment { content: "test", post_id: PostId(132386), parent_id: Some(CommentId(59678)), language_id: Some(LanguageId(0)), form_id: Some("comment-form-guVDE01R3JluZvHiaBhL"), auth: Sensitive }
lemmy_1     |              at crates/api_crud/src/comment/create.rs:41

            This appeared exactly when i got the error-message in lemmi UI.

            I’ve set “English” and “German” as Languages in Admin-Panel.

            • nutomic@lemmy.mlMEnglish
              1·
              2 years ago

              The problem is that languages on your instance’s version of /c/announcements are also limited to English and German for some reason. I thought this might be a bug in that the site languages would also apply to remote communities, but I cant reproduce that. One thing you can check is go into the db, and make sure that select * from local_site; returns exactly one column. Then take the value of site_id and run select * from site where id = **site_id**;. This should show the domain and other data of your instance.

              Anyway you should be able to solve it by refetching the community to your instance (by pasting the community url in the search field). If it worked then curl "https://lemmy.schuerz.at/api/v3/community?id=46" | jq.discussion_languages should output an empty array.