In principle it’s finished, but last time we put it on lemmy.ml for testing there were performance problems and we had to revert. So far it’s not clear what caused those problems, so we need to try again somehow.

No that’s not merged yet, still needs more feedback from plugin devs.

No that’s a completely different issue.

Yes I have more time available than expected, at least for now. And whenever I don’t program for a while, I get a strong urge to write some code so I can’t stop myself.

Yes I have more time available than expected, at least for now. And whenever I don’t program for a while, I get a strong urge to write some code so I can’t stop myself.

I dont have time to read all that. The problem with Beehaw is that the admins are extremely entitled, as if we had some obligation to work for them for free. Similar to what is described in OP.

However we are consistently improving the mod tools, and accept contributions in that area. You can see in the dev updates.

What is this “stance on mod features” that you are talking about?

I don’t see how that would work with federation, as there would be multiple separate groups of community mods (and also admins) who could remove comments.

Thanks, I hope you’re right :D

Thank you :)

Has Google never heard of CI to perform such checks?

Not that I know, it looks like they are only just learning the basics of Rust.

Warrant canary. I doubt those really work because law enforcement could easily require you to keep updating it.

We have lots of unit tests, and also a test suite which launches a couple of local lemmy instances and ensures that they federate as expected. But it’s not possible to cover every single functionality, at least not with our limited resources. The problems all happened with things that are difficult to test and had major breaking changes in this release. In the future we won’t need such breaking changes so there will be less problems.

Also keep in mind that Lemmy is provided for free and as is. We have no legal obligation to users. And you can always stay with an older version if you want more stability.

Im from Germany, living in Spain.

Of course contributions by volunteers are also welcome. However there are very few of those who are consistently contributing (particularly phiresky and sleepless one mentioned in op). And because they have a fulltime job their contributions are much smaller than mine or dessalines’. After the Reddit migration lots of people opened pull requests to implement new features, but most of them were abandoned after noticing how much work it takes to address review comments and actually get the pr merged. So fulltime devs seem very much preferable because they can put their full attention to Lemmy, and get a lot more done.

We want to change the API paths to make them more consistent, and have separate endpoints for image uploads (eg POST /api/v3/account/avatar). Not much else really.

We are getting about 4000 Euros per month which is not much to pay for two developers, so more donations would definitely be nice. From NLnet Dessalines and I still have a few milestones leftover from 2022 but those should be finished very soon. We could definitely use more developers, its impossible to keep up with all the issues so we have to try and prioritize the most important ones.

The people on Lemmy are generally very nice, so I cant complain.

We publish multiple release candidates and run them on lemmy.ml before the final release. That allows the community to test changes. We dont have a quality assurance team, and developers are notoriously bad at testing their own code, so I dont see what we can improve in this regard.

When do we get advanced moderation features? And for example the ability to block all users from a single instance to prevent for example brigading? I mean for the user, so we don’t have to rely on defederation so much.

This could be added to the existing instance block feature, but so far no one has even bothered to open an issue I think.

Are you planning to revamp defederation? I mean it’s rather complicated the way it works and the triangle that is the user’s instance, the other user’s instance and the instance the community is located.

Its very simple and effective in that in prevents all network connections to the blocked instance. So I dont think it makes sense to change that, but other tools can be added on top for more fine-grained restrictions (eg user-level instance blocks in 0.19).