Nutomic

#5601 fixes https://github.com/LemmyNet/lemmy/issues/5340 which allows instance admins to specify a suggested multi-community (`local_site.suggested_communities`) which will be shown on the homepage next to Subscribed / Local / All tabs. However this...

Yes that makes sense. I would suggest the following communities: - [email protected] - [email protected] (or [email protected], they are both similar) - [email protected] where new users can get help - [email protected],...

We are going to run beta versions on lemmy.ml for a while before the final release.

This is not necessary anymore as https://github.com/LemmyNet/lemmy/pull/6077 solves it in a slighty different way. When a new instance is created, it fetches the top 100 communities from lemmyverse.net, and creates...

The same thing was mentioned in the [mlem repo](https://github.com/mlemgroup/mlem/issues/1962). As mentioned in my last comment it may work via OpenCollective. I also opened an issue regarding [instance donations](https://github.com/LemmyNet/lemmy/issues/5613).

Yes. And to be clear this is a problem on the main branch.

Making SETTINGS private isnt possible because its defined in lemmy_utils, but context is in lemmy_api_common. So to allow access from the other crate it must be public, and then it...

@dessalines Like I said in my previous comment this is not possible because they are defined in different crates. For LemmyContext to access Settings it needs to be public, which...

Then we need to move `LemmyContext` into lemmy_utils https://github.com/LemmyNet/lemmy/issues/5200

This makes sense and it shouldnt be too hard to implement. However I dislike the proof formatting, it is much too verbose: ```json "proof": { "@context": [ "https://www.w3.org/ns/activitystreams", "https://w3id.org/security/data-integrity/v2" ],...