nutomic

Hmm not sure whats the context of that quote.

Sure being more welcoming to outside contributors sounds good. Do you have any concrete suggestions how to recruit and train them? We do have some community contributors, but they seem very limited by the amount of time they have for Lemmy after their fulltime job.

Once the new round of NLnet funding is finalized we will publish those milestones. However Im not sure if a backlog like the one you linked is really helpful, it would take a significant amount of time to manage for little benefit. After all every open issue on the Lemmy Github is up for grabs for anyone to implement it.

I agree that its good for redundancy to have another development team for Lemmy. However they will be busy for the next few years redoing all the work we have already done for Lemmy. It would be much more efficient if they simply forked the existing Rust code and implemented their desired features on top. That would also make it easy to merge their changes back into Lemmy.

I see that comment but somehow cant fetch it from lemmy.ml. Would you mind asking what exactly they mean by "toxic development community"? Its honestly the first time I heard something like this about Lemmy.

I actually talked with Jason (one of the Sublinks maintainers) a while ago, asking about the features he was missing from Lemmy. Turns out it was just one or two minor API changes that could be easily implemented, but he never even bothered to open an issue about it. I think they just have fun reimplementing Lemmy, but it would take at least multiple years to catch up with the current features of Lemmy. And by then Lemmy will of course have many more features and improvements. So I wouldnt expect that this ever becomes useful for production.

Having a different license for each user would cause too much complexity and fragmentation. It makes more sense to have a license per instance. This can already be configured and gets displayed under /legal. Then based on the legal info users can decide where to signup, and admins can decide which instances to federate with.

You can run Lemmy in allowlist mode so it only federates with instances that you trust.

It should be very easy to distinguish edits and deletes which were made within a few minutes or hours after writing a comment, from those made months or years later right around the reddit blackout.

The problem is that "Threadiverse" is almost never used together with "Fediverse", so anyone unfamiliar with the terms will think that they are totally distinct. I can understand if you want to categorize different platforms within the Fediverse, but then we should also start referring to Mastodon and similar projects as the "Tootiverse".

I wish people would stop using this silly term "Threadiverse". There is no fundamental difference between Lemmy, Mastodon, Peertube, Friendica and so on. They all federate with the same protocol and are all part of the same Fediverse.

Its also good to explore for yourself. Maybe you notice something missing/outdated in the documentation and can fix it. The docs are generated from these files which are also used in the unit tests.

You can also find this in the documentation.