nutomic

Its now running on a dedicated server with 6 cores/12 threads and 32 gb ram. I hope this will be enough for the near future. Nevertheless, new users should still prefer to signup on other instances.

This server is financed from donations to the Lemmy project. If you want to support it, please consider donating.

Some of you may have noticed that federated actions are slow to synchronize between Lemmy instances. This is most likely because of the setting "Federation worker count" under /admin. It determines how many federation activities can be sent out at once. The default value is 64 which is enough for small or medium sized instances. But for large instances it needs to be increased.

Grep the server logs for "Maximum number of activitypub workers reached" and "Activity queue stats" to confirm that this affects you. For lemmy.ml I just changed the value to 512, you have to experiment what is sufficient. The new value is only applied after restarting Lemmy. In my case changing the value through the website didnt work (maybe because its overloaded). Instead I had to update local_site.federation_worker_count directly in the database.

Edit: I had to increase the value to 160k for lemmy.ml. Now the stats arent getting logged anymore, so Im not sure if the pending queue is still building up or not.

I saw the impressive setup used by the sh.itjust.works instance with 24 CPUs and 64 GB RAM. This inspired me to reconfigure join-lemmy.org so that it can quickly update the instance list, and point users to sites which are actually reachable. This will be an immense help if a lot of Reddit users decide to join Lemmy at once (e.g. during the blackout on Monday). Individual instances will likely go down at that time, but others will stay available and users can easily join them.

Additionally, changes to the site, documentation and translations are also updated automatically. If you see anything that can be improved, consider making a contribution to help new users.

The instance list has a couple of recommended sites at the top. They are defined in this file and seperated by language. For most languages there is only one recommendation or none at all, so you can simply add yours by making a pull request.

In case of English, the situation is a bit different. The current recommended instances (beehaw.org and sopuli.xyz) are already quite large and would be shown near the top of the list anyway. So it makes sense to recommend smaller instances instead.

To be recommended, an instance should meet these requirements:

• It should be a general purpose instance
• At least one member of the admin team needs to be in the Instance admin chat to coordinate with other admins
• The admin team needs to be prepared for a large influx of users, both in terms of hardware and moderation

We can use this thread to discuss which instances should be recommended. There is no maximum number of recommendations, but it should be an even number to work with the desktop layout.

On a side note, the instance list itself could use many improvements such as showing more details about instances or using different sorting methods. If you are a programmer or web designer, you can contribute to improve the website.

Edit: If you are a Lemmy admin and want your instance to be recommended, go ahead and open a pull request for this file. Developers can also contribute in the same repo to improve join-lemmy.org.

This site is currently struggling to handle the amount of new users. I have already upgraded the server, but it will go down regardless if half of Reddit tries to join.

However Lemmy is federated software, meaning you can interact seamlessly with communities on other instances like beehaw.org or lemmy.one. The documentation explains in more detail how this works. Use the instance list to find one where you can register. Then use the Community Browser to find interesting communities. Paste the community url into the search field to follow it.

You can help other Reddit refugees by inviting them to the same Lemmy instance where you joined. This way we can spread the load across many different servers. And users with similar interests will end up together on the same instances. Others on the same instance can also automatically see posts from all the communities that you follow.

Edit: If you moderate a large subreddit, do not link your users directly to lemmy.ml in your announcements. That way the server will only go down sooner.

We are happy to see that many of you are exploring Lemmy after Reddit announced changes to its API policy. I maintain this project alongside @[email protected].

Lemmy is similar to Reddit in many ways, but there is also a major difference: Its not only a single website, but consists of many different websites which are interconnected through federation. This is achieved with the ActivityPub protocol which is also used by Mastodon. It means that you can sign up on any Lemmy instance to interact with users and communities on other instances. The project website has a list of instances which all have their own rules and administrators. We recommend that you sign up on one of them, to avoid overt centralization on lemmy.ml.

Another difference compared to Reddit is that Lemmy is open source, and not funded by any company. For this reason it relies on volunteer work to make the project better, whether it's programming, design, documentation, translating, reporting issues or others. See the contributing guide to get started. You can also donate to support development.

We also recommend that you read the documentation. It explains how Lemmy works and how to setup your own Lemmy instance. Running an instance gives you full control over the rules and moderation, and prevents us developers from having any influence. Especially large communities that want to use Lemmy should host their own instance, because existing Lemmy instances would easily be overwhelmed by a large number of new users.

Enjoy your time here! If you have any questions, feel free to ask below or in the Matrix chat.

My current task is to improve the Lemmy documentation, particularly to explain things better for people who are new to Lemmy and the Fediverse. For this I would like to know if there are any things that were unclear when you first joined (or even still unclear now).

To give you some idea, these are the pages which I plan to write for the first section, with average users in mind:

• Getting started (choose an instance, register, follow, setup profile, start posting)
• What is federation
• Moderation
• Censorship resistance
• Votes and ranking
• Media (Markdown, images, links)
• Other features (theming, language tags, ...)

Besides this I also plan to improve other parts of the documentation, to add things like documentation for the HTTP API (currently only exists for websocket), a guide to run Lemmy with TOR, and explanation of community/site options. Is there anything else where documentation is missing or requires clarification?

By the way, just like other parts of Lemmy the documentation is open source, and you are welcome to open pull requests with improvements.

I want to announce a new version of the activitypub-federation crate. Over the last weeks I worked on major improvements to the usability and documentation. It now includes an extensive guide on getting started to implement federation from scratch, and also an example project which can directly be deployed to a server and federate with projects like Mastodon.

The library takes care of basic functionality like HTTP Signatures, activity sending, and fetching data from other servers. Application developers can focus on the main logic, and treat federation as another form of API. There is no restriction to the content being federated: you can implement a microblogging platform, link aggregator, video hosting site or any other type of social media. The goal is to encapsulate all basic functionality, so that developers can easily implement federation without any prior knowledge.

Using this library can help to share core Activitypub logic between different projects, so that the same code doesn’t have to be implemented and maintained separately by each project. This way improvements can benefit everyone. It also encourages the use of effective patterns to make Rust and Activitypub work together. All of this has been proven to work in Lemmy which uses this library and is the biggest Activitypub project written in Rust.

https://docs.rs/activitypub_federation

I want to announce a new version of the activitypub-federation crate. Over the last weeks I worked on major improvements to the usability and documentation. It now includes an extensive guide on getting started to implement federation from scratch, and also an example project which can directly be deployed to a server and federate with projects like Mastodon.

The library takes care of basic functionality like HTTP Signatures, activity sending, and fetching data from other servers. Application developers can focus on the main logic, and treat federation as another form of API. There is no restriction to the content being federated: you can implement a microblogging platform, link aggregator, video hosting site or any other type of social media. The goal is to encapsulate all basic functionality, so that developers can easily implement federation without any prior knowledge.

Using this library can help to share core Activitypub logic between different projects, so that the same code doesn’t have to be implemented and maintained separately by each project. This way improvements can benefit everyone. It also encourages the use of effective patterns to make Rust and Activitypub work together. All of this has been proven to work in Lemmy which uses this library and is the biggest Activitypub project written in Rust.

https://docs.rs/activitypub_federation