• 117 Posts
  • 1.14K Comments
Joined duela 3 urte
cake
Cake day: api. 17, 2019

help-circle
rss

We don’t have any data exporting yet, but there is an open issue on the github. In the meantime you can just use the API: https://join-lemmy.org/api/classes/LemmyHttp.html#getPosts


I think its a 60 character limit for jerboa as well.


This is what they tell you. Since signal isn’t self-hostable or federated, you can’t verify that.



Tauri just looks like it uses your OS’s web renderer. So even if its not using electron ( a giant chrome wrapper), its still a web renderer wrapper so not really native. Someone could package lemmy-ui in some wrapper and and make it a faux-desktop app I spose.

The whole point of Tauri seems to be that you get the benefits of writing the front end in rust, whereas lemmy-ui is already written in typescript, so you wouldn’t be able to use it.

There’d be no point in porting it either, because at that point, you might as well just write a native rust app that doesn’t use a web renderer, like iced.


We wouldn’t have time to work on it (nutomic and I are already juggling 3 different UIs), but anyone else could. Building a lemmy UI isn’t a gargantuan task, but it does take a lot of work for a single developer, probably about a month or so, judging by how long it took me to create jerboa.

If I had infinite time, I’d probably make a native desktop client in rust using iced, not tauri, which seems to be web and not native.


How does one “enforce correct usage” of a like button? Why do you get to dictate how ppl use that button?


There is no guidelines for the vote / preference buttons. Use it however you see fit, in whatever way you like!

Lemmy’s sorting algorithm is here: https://join-lemmy.org/docs/en/about/ranking.html


By having a metric that shows how well written and thought through an argument is. You don’t have to “like” what is written or said, but you can acknowledge the quality of the argument.

How would you implement this? Because if its by user preference, then you’re back to step one, except you’re dictating how a user should use their preference button. And if its by something strange like comment length, AI’s reading comments, then all of those can be easily gamed


How do you dictate how people use preference buttons? They’re going to use them however they see fit, and that’s a good thing.

And how do you find good content without some sort of collective preference? Any site should be able to answer this question: you have a thread with 10k comments, what’s the best way to sort them so that users don’t have to read every comment?


For the most part. If you have a thread of 10k comments, would you rather read through each of them individually, or have them be sorted by collective preference?


All three I suppose? Here’s an example from xdadevelopers of what dealing with old-school forums is like. A 17-page thread of people trying to discover the best practices / things to do for battery life. Without any scoring or voting, you have to read through hundreds of replies.

Some threads have thousands of comments, going through each of them to find what’s good might take days.


Please report the uncivil comments, and we’ll continue to remove them.

w/ respect to that 3-day temp-ban, you can check the modlog, its completely transparent, which is really helpful in this case in particular. The person claimed :

“its clear the admins of lemmy are manufacturing communist mobs”, and linked to a post where @AgreeableLandscape@lemmy.ml supported people debunking anti-communist / mccarthyite propaganda. This is supposedly “evidence of manufacturing mobs.”

Obviously someone who attacks the entire mod team with no evidence would be better suited to a specifically anti-communist site like wolfballs or reddit.


But then you’ve just taken away a method for people to express their dislike of something.


So sorting by total reactions, regardless of if they’re negative or not? That sounds like a way to bring some disliked things to the top.


Then you’d have to assign numbers for the different reactions (otherwise how would you compare a heart to a poo emoji ) and we’re back to where we started.


The votes are really more about helping sort popular / unpopular content more that anything, so emojis wouldn’t help with that.

Without scores or voting, its back to the days of forums where you have to scroll through hundreds of pages to find something decent.


I doubt we’ll add a no calls for violence in the same way reddit does, but we might need to add a no calls for assassinations rule since it seems that’s not common sense for some people.


Most big tech platforms have gotten rid of the downvote as well. They only want you to express liking, not disliking.


Stand behind this post 100%.

It’s completely okay to have political disagreements here, but please be respectful when doing so. We want to make this site an enjoyable experience, and its extremely alienating for others to see people rudely insulting each other. People aren’t going to want to interact with you online or IRL if you do your best to offend everyone you interact with.

Also about downvotes: we’re aware that not just downvotes, but also upvotes can be psychologically harmful for many. If that’s the case for you, there’s a setting where you can hide vote scores, yet still be able to vote on things and get all the benefits of sorting by popularity. I think its still a good idea to be transparent and show them by default tho.


I have no idea where you are getting that from, but it doesn’t match lemmy-ansible, or the PR I linked.

Also please do not screenshot text, just copy-paste the entire file so I can see what’s wrong with it.


Lemmy Release v0.16.6 - A few bug fixes
Sry for not announcing sooner.
fedilink


## What is Lemmy? Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top. ## Major Changes A full list of fixes is below, but this patch release includes federation compatibility and bug fixes, as well as fixing vulnerabilities in our websocket rate limiting. ## Upgrade notes Besides the addition of a [search rate limit to the lemmy.hjson](https://github.com/LemmyNet/lemmy/blob/main/config/defaults.hjson#L39), there are no config or API changes. Follow the [Docker or Ansible upgrade instructions here.](https://join-lemmy.org/docs/en/administration/administration.html) ## Support development We (@dessalines and @nutomic) have been working full-time on Lemmy for almost two years. This is largely thanks to support from [NLnet foundation](https://nlnet.nl/). If you would like to support our efforts, please consider [donating](https://join-lemmy.org/donate). If you'd like to support development, and make sure that we will always be available to work full time on Lemmy, consider [donating to support its development](https://join-lemmy.org/donate). We've spent hundreds of hours on Lemmy, and would like to be able to add more developers to our little open-source co-op as time goes on. ## Changes ### Lemmy Server - Federate user account deletion (fixes [#1284](https://github.com/LemmyNet/lemmy/issues/1284)) ([#2199](https://github.com/LemmyNet/lemmy/issues/2199)) - Dont federate initial upvote ([#2196](https://github.com/LemmyNet/lemmy/issues/2196)) - Add missing mod log entries for federated actions (fixes [#1489](https://github.com/LemmyNet/lemmy/issues/1489)) ([#2198](https://github.com/LemmyNet/lemmy/issues/2198)) - Make sure application questionaire is required. Fixes [#2189](https://github.com/LemmyNet/lemmy/issues/2189) - Fix verify_mod_action check for remote admin actions ([#2190](https://github.com/LemmyNet/lemmy/issues/2190)) - Run cargo upgrade ([#2176](https://github.com/LemmyNet/lemmy/issues/2176)) - Migrate towards using page.attachment field for url (ref [#2144](https://github.com/LemmyNet/lemmy/issues/2144)) ([#2182](https://github.com/LemmyNet/lemmy/issues/2182)) - Exclude removed/deleted posts from community outbox ([#2184](https://github.com/LemmyNet/lemmy/issues/2184)) - Fetch community outbox in parallel (fixes [#2180](https://github.com/LemmyNet/lemmy/issues/2180)) ([#2181](https://github.com/LemmyNet/lemmy/issues/2181)) - Adding a ban expires update job. Fixes [#2177](https://github.com/LemmyNet/lemmy/issues/2177) - Add email translations ([#2175](https://github.com/LemmyNet/lemmy/issues/2175)) - Add test files for Friendica federation (fixes [#2144](https://github.com/LemmyNet/lemmy/issues/2144)) ([#2167](https://github.com/LemmyNet/lemmy/issues/2167)) - Lowering search rate limit. Fixes [#2153](https://github.com/LemmyNet/lemmy/issues/2153) ([#2154](https://github.com/LemmyNet/lemmy/issues/2154)) - Rate limit ws joins ([#2171](https://github.com/LemmyNet/lemmy/issues/2171)) - Delete unused diesel.toml file ([#2166](https://github.com/LemmyNet/lemmy/issues/2166)) - Rate limit websocket joins. ([#2165](https://github.com/LemmyNet/lemmy/issues/2165)) - Doing tests in sequential order. Fixes [#2158](https://github.com/LemmyNet/lemmy/issues/2158) ([#2163](https://github.com/LemmyNet/lemmy/issues/2163)) - Dont log errors when rate limit is hit (fixes [#2157](https://github.com/LemmyNet/lemmy/issues/2157)) ([#2161](https://github.com/LemmyNet/lemmy/issues/2161)) - Fix rate limit check for register. Fixes [#2159](https://github.com/LemmyNet/lemmy/issues/2159) - GNU social compatibility ([#2100](https://github.com/LemmyNet/lemmy/issues/2100)) - Consolidate and lower reqwest timeouts. Fixes [#2150](https://github.com/LemmyNet/lemmy/issues/2150) ([#2151](https://github.com/LemmyNet/lemmy/issues/2151)) - Check that config is valid before saving ([#2152](https://github.com/LemmyNet/lemmy/issues/2152)) - Dont log error if duplicate activity is received (fixes [#2146](https://github.com/LemmyNet/lemmy/issues/2146)) ([#2148](https://github.com/LemmyNet/lemmy/issues/2148)) - WIP: Email localization (fixes [#500](https://github.com/LemmyNet/lemmy/issues/500)) ([#2053](https://github.com/LemmyNet/lemmy/issues/2053)) - If viewed actor isnt in db, fetch it from other instance ([#2145](https://github.com/LemmyNet/lemmy/issues/2145)) - Show rate limit algorithm. Fixes [#2136](https://github.com/LemmyNet/lemmy/issues/2136) - Adjust retry interval for sending activities ([#2141](https://github.com/LemmyNet/lemmy/issues/2141)) - Add jerboa link to readme. Fixes [#2137](https://github.com/LemmyNet/lemmy/issues/2137) - Forbid remote URLs for avatars/banners (fixes [#1618](https://github.com/LemmyNet/lemmy/issues/1618)) ([#2132](https://github.com/LemmyNet/lemmy/issues/2132)) - Remove docker/prod unused files (fixes [#2086](https://github.com/LemmyNet/lemmy/issues/2086)) ([#2133](https://github.com/LemmyNet/lemmy/issues/2133)) - Rework error handling (fixes [#1714](https://github.com/LemmyNet/lemmy/issues/1714)) ([#2135](https://github.com/LemmyNet/lemmy/issues/2135)) - Dont allow admin to add mod to remote community ([#2129](https://github.com/LemmyNet/lemmy/issues/2129)) - Reject federated downvotes if downvotes are disabled (fixes [#2124](https://github.com/LemmyNet/lemmy/issues/2124)) ([#2128](https://github.com/LemmyNet/lemmy/issues/2128)) ### Lemmy UI - Dont allow community urls like /c/{id} (fixes [#611](https://github.com/LemmyNet/lemmy-ui/issues/611)) ([#612](https://github.com/LemmyNet/lemmy-ui/issues/612)) - Fix loading indicator on search page (fixes [#443](https://github.com/LemmyNet/lemmy-ui/issues/443)) ([#606](https://github.com/LemmyNet/lemmy-ui/issues/606)) - Upgrade deps ([#604](https://github.com/LemmyNet/lemmy-ui/issues/604)) - Remove auth token from error message. Fixes [#600](https://github.com/LemmyNet/lemmy-ui/issues/600) ([#601](https://github.com/LemmyNet/lemmy-ui/issues/601)) - Fix error during new site setup ([#596](https://github.com/LemmyNet/lemmy-ui/issues/596)) - Differentiate between mods and admins in mod log ([#597](https://github.com/LemmyNet/lemmy-ui/issues/597)) - Fix comment fedilink (fixes [#594](https://github.com/LemmyNet/lemmy-ui/issues/594)) ([#595](https://github.com/LemmyNet/lemmy-ui/issues/595))
fedilink

A few bug fixes: ## Lemmy - Revert "Add logging to debug federation issues (ref [#2096](https://github.com/LemmyNet/lemmy/issues/2096)) ([#2099](https://github.com/LemmyNet/lemmy/issues/2099))" ([#2130](https://github.com/LemmyNet/lemmy/issues/2130)) - Dont allow admin to add mod to remote community ([#2129](https://github.com/LemmyNet/lemmy/issues/2129)) - Reject federated downvotes if downvotes are disabled (fixes [#2124](https://github.com/LemmyNet/lemmy/issues/2124)) ([#2128](https://github.com/LemmyNet/lemmy/issues/2128)) ## Lemmy-ui - Fix error during new site setup ([#596](https://github.com/LemmyNet/lemmy-ui/issues/596)) - Differentiate between mods and admins in mod log ([#597](https://github.com/LemmyNet/lemmy-ui/issues/597)) - Fix comment fedilink (fixes [#594](https://github.com/LemmyNet/lemmy-ui/issues/594)) ([#595](https://github.com/LemmyNet/lemmy-ui/issues/595))
fedilink

## What is Lemmy? Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top. ## Major Changes ### Theming Customizing Lemmy is now much easier than before. Instance admins can select a default instance theme under `/admin` which applies to all users who are not logged in, and those who haven't explicitly picked a theme. It is also possible now to add custom themes to an instance, without having to recompile lemmy-ui. When running with Docker, make sure that [these lines](https://github.com/LemmyNet/lemmy-ansible/pull/24/files) are present in docker-compose.yml (Ansible will add them automatically if you updated the repo). Then put your .css file into `./volumes/lemmy-ui/extra_themes`. The new theme can then be selected by users, or set as instance default. For native installation (without Docker), themes are loaded by lemmy-ui from `./extra_themes` folder. A different path can be specified with `LEMMY_UI_EXTRA_THEMES_FOLDER` environment variable. For instructions how to create a new theme, have a look at the [documentation](https://join-lemmy.org/docs/en/client_development/theming.html). ### Federation @nutomic made many changes to federation to increase compatibility with other software. Lemmy can now receive deletions from [Pleroma], comments from [Friendica] and communities from [lotide](https://sr.ht/~vpzom/lotide/). Other actions were already compatible before. Mastodon can now display communities even when a user with identical name exists (but the user can't be viewed in that case). There were no breaking changes necessary, so federation is fully compatible with 0.15. If you notice something in another project that doesn't federate but should, please open an issue. Multiple users have pointed out that posts, comments and votes don't federate reliably. We first attempted to fix this in [Lemmy 0.15.4](https://lemmy.ml/post/184152) a few days ago, but that didn't help much. Later @nutomic noticed that Lemmy was only sending out activities with 4 worker threads, which is not enough for a big instance like lemmy.ml. At the same time, many of those workers were taken up by sending to broken instances, trying to connect for a minute or more. This version adds a timeout and increases the number of workers. ### Federated bans Until now, only community bans were federated, and the "Remove content" option didn't work over federation. The new version fixes this behaviour, so that both site bans and community bans federate, including "Remove content" option and expiry. Note that this change only affects new bans, those which were issued before upgrading to 0.16 will not be federated. ### Hide communities @dayinjing implemented a funcionality for instance admins to hide controversial communities. A hidden community is only visible to those users who subscribe to it. This represents a milder alternative to removing a community. This functionality is not implemented in lemmy-ui yet, but admins can hide a community like this via command line: ``` curl -X PUT https://example.com/api/v3/community/hide \ -H "Content-Type: application/json" \ -d \ '{"community_id":3,"hidden":true,"reason":"*reason for mod log*","auth":"*admin jwt token*"}' ``` ### Jerboa: a new android app To help adoption, and since most people use social media through their smartphones nowadays, @dessalines has been working on a native android app for Lemmy called [Jerboa](https://github.com/dessalines/jerboa), which is now on [F-Droid](https://f-droid.org/packages/com.jerboa) and [Google Play](https://play.google.com/store/apps/details?id=com.jerboa). It is still at an alpha level, but is very usable. We'd love to have experienced android developers contribute to it. This now makes three smartphone apps for Lemmy: [Lemmur and Jerboa for Android, and Remmel for iOS](https://join-lemmy.org/apps). ## Upgrade notes Follow the [Docker or Ansible upgrade instructions here.](https://join-lemmy.org/docs/en/administration/administration.html) There are three lemmy.hjson config changes. See [defaults.hjson](https://github.com/LemmyNet/lemmy/blob/main/config/defaults.hjson) for comments and default values. - changed boolean `email.use_tls` to `email.tls_type` - added `setup.default_theme` - added `federation.worker_count` ## Support development We (@dessalines and @nutomic) have been working full-time on Lemmy for almost two years. This is largely thanks to support from [NLnet foundation](https://nlnet.nl/). If you would like to support our efforts, please consider [donating](https://join-lemmy.org/donate). If you'd like to support development, and make sure that we will always be available to work full time on Lemmy, consider [donating to support its development](https://join-lemmy.org/donate). We've spent hundreds of hours on Lemmy, and would like to be able to add more developers to our little open-source co-op as time goes on. ## Changes ### API - A full list of the API changes can be seen on this diff of [lemmy-js-client: 0.15.0 -> 0.16.0](https://github.com/LemmyNet/lemmy-js-client/compare/0.15.0-rc.34...0.16.0-rc.1) . ### Config - The config changes are [here.](https://github.com/LemmyNet/lemmy/compare/0.15.2...main#diff-bcc84ad7bb4d0687c679cb6b3711052d8eba74a8188578c7516a8fdb5584d01a)
fedilink



toki pona guide / resources
My toki pona guide: ## Learning the language - [jan Lentan's lessons](https://devurandom.xyz/tokipona/). By far the best guide for learning the language. - [jan Misali's 12 days of toki pona](https://www.youtube.com/watch?v=4L-dvvng4Zc). Not as good as jan Lentan's lessons, but serves as a speedy introduction to the vocab. ## Vocabulary - Download a client for the spaced-repetition software, [Anki](https://apps.ankiweb.net/). - [AnkiDroid for Android](https://play.google.com/store/apps/details?id=com.ichi2.anki) - [Shared Deck of all the current popular words](https://ankiweb.net/shared/info/1075479788) (~137 words as of 2022, known as *pu + nimi ku suli*). - [Shared Deck of all the phrases from jan Lentan's lessons.](https://ankiweb.net/shared/info/204928497) - You can find other shared decks [here](https://ankiweb.net/shared/decks/toki%20pona). ## Listening / Fluency - [Youtube channel - ma pi toki pona](https://www.youtube.com/channel/UCQTppoxw6lJTtvr9ZRIjmgg) . Has lots of fluent speakers having conversations about different topics. ## Other resources - [ku - the toki pona dictionary](https://www.amazon.com/dp/0978292367/) - [pu - toki pona: the language of good (first book)](http://www.amazon.com/gp/product/0978292308)
fedilink





To combat the anti-Semitic brigades over the last few days, we've made it so that new users have to fill out a registration application before they can join here.
This should help us cut down on the trolls. We recommend other instances do the same, because they will likely be targeted also. I apologize for all their gore-posts as well, no one should have to see that. We'll try to look for more admins from different time-zones as well to get them faster. The two other possibilities we have currently as options, are turning on required email verification, and as a last resort, closing signups. I personally would rather not do either, but they are options. Many thanks to [@k_o_t@lemmy.ml](https://lemmy.ml/u/k_o_t) and [@AgreeableLandscape@lemmy.ml](https://lemmy.ml/u/AgreeableLandscape) for banning those trolls.
fedilink



fedilink

Lemmy now has private instances, optional registration applications, optional email verification, and temporary bans! These are described in detail below. Special thanks to @asonix for adding [tokio-console](https://github.com/LemmyNet/Lemmy/issues/2003) and [Jaeger + opentelemetry](https://github.com/LemmyNet/Lemmy/issues/1992) to our dev setups, so we can better identify performance bottlenecks. ## What is Lemmy? [Lemmy](https://join-lemmy.org/) is similar to sites like Reddit, Lobste.rs, or Hacker News: you subscribe to communities you're interested in, post links and discussions, then vote and comment on them. Lemmy isn't just a reddit alternative; its a network of interconnected communities ran by different people and organizations, all combining to create a single, personalized front page of your favorite news, articles, and memes. ## Major Changes ### Required email verification Admins can turn this on, and new users will need to verify their emails. Current users will not have to do this. ### Registration applications Admins can now optionally make new users fill out an application to join your server. There is a new panel in their top bar where they can approve or deny pending applications. This works in conjunction with the *require_email* field. If that is also turned on, the application will only be shown after their email has been verified. The user will receive an email when they have been accepted. ### Closed / Private instances The instance settings now includes a *private instance* option, which if turned on, will only let logged in users view your site. Private instances was one of our first issues, and it was a large effort, so its great to finally have this completed. ### Temporary Bans When banning users from your site or community, moderators can now optionally give a number of days for the ban to last. ### Allow comment replies from blocked users It used to be that if a user blocked you, you couldn't respond to their public posts and comments. This is now fixed. They won't see your content, but others can. ## Upgrade notes Follow the [Docker or Ansible upgrade instructions here.](https://join-lemmy.org/docs/en/administration/administration.html) ## Support development If you'd like to support development, and make sure that we will always be available to work full time on Lemmy, consider [donating to support its development](https://join-lemmy.org/donate). We've spent hundreds of hours on Lemmy, and would like to be able to add more developers to our little open-source co-op as time goes on. ## Changes ### API We've removed a list of banned users from `GetSite`, added a few endpoints related to registration applications, made a few changes allowing temporary bans, site settings, made a few changes to the login response. These are non-destructive and current clients should work with this release. - A full list of the API changes can be seen on this diff of [lemmy-js-client: 0.14.0 -> 0.15.0](https://github.com/LemmyNet/lemmy-js-client/compare/0.14.0-rc.1...0.15.0-rc.34) . ### Config There is a new rate limit for creating new comments in the [config.hjson](https://github.com/LemmyNet/lemmy/blob/main/config/defaults.hjson#L36). ### Lemmy Server - Adding temporary bans. Fixes [#1423](https://github.com/LemmyNet/Lemmy/issues/1423) ([#1999](https://github.com/LemmyNet/Lemmy/issues/1999)) - Add console-subscriber ([#2003](https://github.com/LemmyNet/Lemmy/issues/2003)) - Opentelemetry ([#1992](https://github.com/LemmyNet/Lemmy/issues/1992)) - Use correct encoding when fetching non-UTF-8 site metadata ([#2015](https://github.com/LemmyNet/Lemmy/issues/2015)) - Adding a banned endpoint for admins. Removing it from GetSite. Fixes [#1806](https://github.com/LemmyNet/Lemmy/issues/1806) - Prevent panic on InboxRequestGuard - Case-insensitive webfinger response. Fixes [#1955](https://github.com/LemmyNet/Lemmy/issues/1955) & [#1986](https://github.com/LemmyNet/Lemmy/issues/1986) ([#2005](https://github.com/LemmyNet/Lemmy/issues/2005)) - First pass at invite-only migration. ([#1949](https://github.com/LemmyNet/Lemmy/issues/1949)) - Upgrading pictrs. ([#1996](https://github.com/LemmyNet/Lemmy/issues/1996)) - Trying out an upgraded version of html5ever. [#1964](https://github.com/LemmyNet/Lemmy/issues/1964) ([#1991](https://github.com/LemmyNet/Lemmy/issues/1991)) - Adding min setup password length to the docs. Fixes [#1989](https://github.com/LemmyNet/Lemmy/issues/1989) ([#1990](https://github.com/LemmyNet/Lemmy/issues/1990)) - Test pleroma follow ([#1988](https://github.com/LemmyNet/Lemmy/issues/1988)) - Remove awc ([#1979](https://github.com/LemmyNet/Lemmy/issues/1979)) - Consolidate reqwest clients, use reqwest-middleware for tracing - Don't drop error context when adding a message to errors ([#1958](https://github.com/LemmyNet/Lemmy/issues/1958)) - Change lemmur repo links ([#1977](https://github.com/LemmyNet/Lemmy/issues/1977)) - added deps - git and ca-certificates (for federation to work) and changed adduser to useradd so that user can be added non-interactively ([#1976](https://github.com/LemmyNet/Lemmy/issues/1976)) - Allow comment replies from blocked users. Fixes [#1793](https://github.com/LemmyNet/Lemmy/issues/1793) ([#1969](https://github.com/LemmyNet/Lemmy/issues/1969)) - Fix retry infinite loops. Fixes [#1964](https://github.com/LemmyNet/Lemmy/issues/1964) ([#1967](https://github.com/LemmyNet/Lemmy/issues/1967)) - Add lotide activities to tests - Allow single item for to, cc, and @context - Adding a captcha rate limit. Fixes [#1755](https://github.com/LemmyNet/Lemmy/issues/1755) ([#1941](https://github.com/LemmyNet/Lemmy/issues/1941)) - Dont send email notifications for edited comments (fixes [#1925](https://github.com/LemmyNet/Lemmy/issues/1925)) - Fix API dupes query. [#1878](https://github.com/LemmyNet/Lemmy/issues/1878) - Fixing duped report view for admins. Fixes [#1933](https://github.com/LemmyNet/Lemmy/issues/1933) ([#1945](https://github.com/LemmyNet/Lemmy/issues/1945)) - Adding a GetComment endpoint. Fixes [#1919](https://github.com/LemmyNet/Lemmy/issues/1919) ([#1944](https://github.com/LemmyNet/Lemmy/issues/1944)) - Fix min title char count for post titles. Fixes [#1854](https://github.com/LemmyNet/Lemmy/issues/1854) ([#1940](https://github.com/LemmyNet/Lemmy/issues/1940)) - Adding MarkPostAsRead to API. Fixes [#1784](https://github.com/LemmyNet/Lemmy/issues/1784) ([#1946](https://github.com/LemmyNet/Lemmy/issues/1946)) - background-jobs 0.11 ([#1943](https://github.com/LemmyNet/Lemmy/issues/1943)) - Add tracing ([#1942](https://github.com/LemmyNet/Lemmy/issues/1942)) - Remove pointless community follower sort. ([#1939](https://github.com/LemmyNet/Lemmy/issues/1939)) - Use once_cell instead of lazy_static - Adding unique constraint for activity ap_id. Fixes [#1878](https://github.com/LemmyNet/Lemmy/issues/1878) ([#1935](https://github.com/LemmyNet/Lemmy/issues/1935)) - Making public key required. Fixes [#1934](https://github.com/LemmyNet/Lemmy/issues/1934) - Change NodeInfo `links` to an array - Fixing fuzzy_search to escape like chars. - Fix build error in [#1914](https://github.com/LemmyNet/Lemmy/issues/1914) - Fix login ilike bug. Fixes [#1920](https://github.com/LemmyNet/Lemmy/issues/1920) - Fix Smithereen webfinger, remove duplicate webfinger impl (fixes [#1916](https://github.com/LemmyNet/Lemmy/issues/1916)) - Dont announce comments, edited posts to Pleroma/Mastodon followers - Community outbox should only contain activities sent by community (fixes [#1916](https://github.com/LemmyNet/Lemmy/issues/1916)) - Remove HTTP signature compatibility mode (its not necessary) - Implement rate limits on comments ### Lemmy UI - Fixed an issue with post embeds not being pushed to a new line [#544](https://github.com/LemmyNet/lemmy-ui/issues/544) - Adding as and lt languages, Updating translations. - Temp bans ([#524](https://github.com/LemmyNet/lemmy-ui/issues/524)) - Fix banner. Fixes [#466](https://github.com/LemmyNet/lemmy-ui/issues/466) ([#534](https://github.com/LemmyNet/lemmy-ui/issues/534)) - Making the modlog badge stand out more. Fixes [#531](https://github.com/LemmyNet/lemmy-ui/issues/531) ([#539](https://github.com/LemmyNet/lemmy-ui/issues/539)) - Add some fallback properties for display in older browsers ([#535](https://github.com/LemmyNet/lemmy-ui/issues/535)) - Private instances ([#523](https://github.com/LemmyNet/lemmy-ui/issues/523)) - Add nord theme. Fixes [#520](https://github.com/LemmyNet/lemmy-ui/issues/520) ([#527](https://github.com/LemmyNet/lemmy-ui/issues/527)) - Dont receive post room comments from blocked users. ([#516](https://github.com/LemmyNet/lemmy-ui/issues/516)) - Using console.error for error logs. ([#517](https://github.com/LemmyNet/lemmy-ui/issues/517)) - Fix issue with websocket buffer. - Switching to websocket-ts. [#247](https://github.com/LemmyNet/lemmy-ui/issues/247) ([#515](https://github.com/LemmyNet/lemmy-ui/issues/515)) - Fix native language issue. (zh_Hant) ([#513](https://github.com/LemmyNet/lemmy-ui/issues/513)) - Fix tippy on component mount. Fixes [#509](https://github.com/LemmyNet/lemmy-ui/issues/509) ([#511](https://github.com/LemmyNet/lemmy-ui/issues/511)) - Fix docker latest ([#510](https://github.com/LemmyNet/lemmy-ui/issues/510)) - Enabling html tags in markdown. Fixes [#498](https://github.com/LemmyNet/lemmy-ui/issues/498) - Fix comment scroll bug. Fixes [#492](https://github.com/LemmyNet/lemmy-ui/issues/492) - Fixing error for null person_block. Fixes [#491](https://github.com/LemmyNet/lemmy-ui/issues/491) - Trying to catch promise and json parse errors. [#489](https://github.com/LemmyNet/lemmy-ui/issues/489) ([#490](https://github.com/LemmyNet/lemmy-ui/issues/490))
fedilink

!!!
fedilink
10