Algorithms are definitely needed to discover good content. There are some good videos on Peertube, but its very difficult to find them due to all the low effort spam. Lemmy also had different algorithms from the beginning and no one ever complained about them.

The problem with algorithms used by Reddit, Facebook etc is that they are completely intransparent, and include factors which dont benefit the user, such as “engagement” or advertising. As long as Fediverse algorithms are focused on benefitting the user and are transparent there is nothing wrong with them.

Lemmy dev here. Making the same post to multiple communities is not possible, so you need to post multiple times tagging a different community each time. Links are taken from Activitypub attachment, but Mastodon only seems to support image attachments. So it is not possible to add other types of links unless Mastodon adds an option for that. Markdown would also have to be supported by Mastodon.

There are various other microblogging platforms on the Fediverse which may support these features and may be better suited to your purpose. For example Mbin, Hometown, Pleroma, Misskey or Mitra to name just a few.

Thanks, good to know.

It could be backported, but there are now significant changes between the 0.19 and development branches, so it would take some work.

Fair enough, its just a bit strange that this particular critique comes up regularly.

Keyword filtering is about to be merged into Lemmy. Other features will also be added over time.

We are working on new moderation features all the time, for example 1.0 will correctly federate instance bans which is quite complicated to get right. There will also be a plugin system which allows for much more flexible mod tools. Its just that our time is very limited for all the work that needs to be done on a project with over 50k active users.

These performance results are only from the browser side, but dont cover server performance. The database for lemmy.ml is 60 GB, and that is with 6 years of history. Not sure where your 10x claim comes from. The lemmy.ml server costs 70 Euros per month and doesnt have much loa, with almost 10 times as many active users.

There is an API so you could write a script to import any kind of data.

Its similar to Lemmy in many ways, so like Lemmy posts are redundantly mirrored across instances, the same is true for Ibis articles.

Getting Wikipedia federated would be great, but it will take a long time for Ibis to be ready for that scale.

For now my focus is to make it federate with Lemmy and the rest of the Fediverse. But you’re welcome to open an issue for that kind of feature.

Lemmy’s AGPL license doesnt allow forking the code into a proprietary server. All changes need to be open source as well, otherwise the operator can get sued. So a proprietary Lemmy software would have to be developed from scratch which would take a long time.

Thanks for linking my project. Im happy to answer questions about it. Also here you can find the git repo.

Ah right in the past new users always had all languages enabled. But the way languages work after being enabled/disabled hasnt changed.

That wasnt changed, to see all languages you have to enable everything (Ctrl+A).

I made a pull request for this.

https://github.com/LemmyNet/lemmy/pull/5485

That is true, but Im not sure what would be a better solution. Show a language selector on the registration page? That would make registration even more complicated, and someone needs to implement it. Or prompt the user to change languages after signup? Again someone needs to implement it. Enable English by default for all new users? That would be easy, but there are also people who dont understand English.

I tested the code locally.

The accept-language header is sent automatically by the browser. You can configure it in the settings, eg in Firefox “Choose your preferred language for displaying pages”.

You mean this one? It is included, but only has an effect if the instance has site languages configured. lemm.ee has all languages enabled, so new users should also have all languages enabled by default. I tested this just now and it works fine.

The other thing is that Lemmy uses languages from Accept-Language HTTP header combined with site languages. If the instance has all languages enabled and the user has an Accept header with German, he will only see German posts.

deleted by creator