Nutomic

That was a temporary measure very early in development, when moderation tooling was still very incomplete. This was to avoid ending up like Voat. Once mod tools were implemented, the slur filter became optional. Simple as that.

That comment is deleted, did you actually read it? If you check the modlog you will see that I didnt defend CSAM at all, but was only defending another user. Just to make it clear for you, I am against pedophilia. Its honestly impressive, you dont know me at all you try to paint me as some kind of evil supervillain over a few misinterpreted comments.

That feature was part of the development version, and never meant to be included in any official release.

Defederations and bans essentially work like a shared blocklist for all users on that instance. Plus you get a local feed with other users who have similar interests, and blocked users/instances don’t use local server resources.

Subscribing to a blocklist seems risky, because it’s likely that many users would subscribe to a single, popular blocklist. Then it would become a centralised point of control which can silence people across much of the Lemmyverse.

You can export your settings, remove everything unrelated to blocks, and share it. Then other users can import the json file and it will be added to their existing blocklist.

If login fails due to missing email verification, it should automatically show a link to resend the verification email.

You can ask an admin to ban the user, or remove the community. Then those comments wont federate anymore.

The frontend part for tags is currently being implemented: https://github.com/LemmyNet/lemmy-ui/pull/3795

Once that is merged it will automatically be deployed to voyager.lemmy.ml where you can test the development version.

This isnt really a matter of the API. Its up to developers of apps or frontends to show a badge for moderators on each comment, and this could also easily be hidden. This has come up before, but it seems no one really cares enough to push such a change through.

This is an unreleased feature to federate some popular communities when a new Lemmy instance is created. It was hardcoded to lemmy.ml for a while, but I already changed this and made it configurable. Obviously the entire development code for Lemmy is not ready for production now, and needs a lot of fine-tuning. Its not an argument against the stable release version of Lemmy.

deleted by creator

This would make instance creation too complicated.

Its intentionally in this order because Mastodon prioritizes the last item (ie the community). If the order was changed, it would be impossible for Mastodon users to interact with a community where a user with the same name exists.

That is true. I made a post just now to gather suggestions for improving the website, please have a look and comment if you have any ideas: https://lemmyverse.link/lemmy.ml/post/41719890

There is nothing preventing apps from providing a registration flow. For example Voyager has it. I suppose the problem is again which instance to choose for signup. You can discuss this in https://lemmy.world/c/boostforlemmy or https://lemmy.world/c/lemmyapps.

As for multiple Lemmy apps being available: Most of the current Lemmy users came here in 2023 when Reddit locked down the API and killed third-party apps. Thats why a lot of apps are now available, and everyone can decide for himself which one he prefers.

Good point, I made a PR to use biased random sort again that we had in the past, so larger instances are always shown near the top.

https://github.com/LemmyNet/joinlemmy-site/pull/508

The logic it uses is to hide any instances with more than 30% of all active users to prevent centralization, just like you say. There are also some other filters like requiring at least 5 active users.

There is a “Join” button which goes directly to the registration page of the respective instance. Would it be clearer to rename this? Other than that I’m also happy to make improvements if you have concrete suggestions.

Edit: Made a PR to rename Join to Sign Up: https://github.com/LemmyNet/joinlemmy-site/pull/509

The onboarding is way too complicated for the average user. A huge part of this is that there are 100 ways to do it. Before you even can start to do anything you have to investigate and then decide on what and how to do it. And even then there is no guidance at all, you are given options and then you can either go and do some research again or try them one by one. You lose at least 90% of the users here already. It doesn’t help that fediverse users try to downplay this issue.

The solution to this is that people should not recommend Lemmy, but a specific instance such as programming.dev (depending on the audience). The Lemmy software and join-lemmy.org are mainly targeted at potential instance admins, or those who are already familiar with the Fediverse.

After that you are told that your registration needs to be approved manually and that there is no notification about that so you have to manually check from time to time whether your are able to login or not.

This is wrong or outdated, Lemmy definitely sends an email once your registration is approved or denied (if you provided an email during registration). Worth contacting the programming.dev admins to change this line.