Skip Navigation
Announcements @lemmy.ml Dessalines @lemmy.ml

Lemmy Developer AMA and Dev Update, 2024-01-26, 1500 CEDT

This is a chance for any users, admins, or developers to ask anything they'd like to myself, @[email protected] , SleeplessOne , or @[email protected] about Lemmy, its future, and wider issues about the social media landscape today.

NLNet Funding

First of all some good news: We are currently applying for new funding from NLnet and have reached the second round. If it gets approved then @[email protected] and SleeplessOne will work on the paid milestones, while @dessalines and @nutomic will keep being funded by direct user donations. This will increase the number of paid Lemmy developers to four and allow for faster development.

You can see a preliminary draft for the milestones. This can give you a general idea what the development priorities will be over the next year or so. However the exact details will almost certainly change until the application process is finalized.

Development Update

@ismailkarsli added a community statistic for number of local subscribers.

@jmcharter added a view for denied Registration Applications.

@dullbananas made various improvements to database code, like batching insertions for better performance, SQL comments and support for backwards pagination.

@SleeplessOne1917 made a change that besides admins also allows community moderators to see who voted on posts. Additionally he made improvements to the 2FA modal and made it more obvious when a community is locked.

@nutomic completed the implementation of local only communities, which don't federate and can only be seen by authenticated users. Additionally he finished the image proxy feature, which user IPs being exposed to external servers via embedded images. Admin purges of content are now federated. He also made a change which reduces the problem of instances being marked as dead.

@dessalines has been adding moderation abilities to Jerboa, including bans, locks, removes, featured posts, and vote viewing.

In other news there will soon be a security audit of the Lemmy federation code, thanks to Radically Open Security and NLnet.

Support development

@dessalines and @nutomic are working full-time on Lemmy to integrate community contributions, fix bugs, optimize performance and much more. This work is funded exclusively through donations.

If you like using Lemmy, and want to make sure that we will always be available to work full time building it, consider donating to support its development. Recurring donations are ideal because they allow for long-term planning. But also one-time donations of any amount help us.

370

You're viewing a single thread.

370 comments

  • What are the plans around admin tools?

    Instance owners currently gets notified when someone has reported a user for spamming or trolling, but frequently it's a user that is not on his instance, so he can't do anything about it. Wouldn't it be better if instance owners got notified only when they can take actual action (like the user being registered on their instance)?

    • If you've been following our code commits / PRs, we've been adding a lot of mod tools improvements not just lately, but over lemmy's entire life. I would even go so far as to say we have the strongest mod tools of any project in the fediverse, all the more necessary for us because of the community-focus.

      The upcoming roadmap for 2024 includes some mod additions, such as mod warnings, attaching report counts to items, viewing mod actions for items, etc.

      Instance owners currently gets notified when someone has reported a user for spamming or trolling, but frequently it’s a user that is not on his instance, so he can’t do anything about it. Wouldn’t it be better if instance owners got notified only when they can take actual action (like the user being registered on their instance)?

      Instance admins are responsible for what content their users see, so if a troll is visible to their users and ruining their day, then it should be taken care of everywhere necessary.

    • I have seen this first hand. I think when someone hits report it needs to go to the moderator of the community. From there the mod should be able to forward it to where it needs to go.

      Instance admins should be able to intersect this process.

      • There's some more context for this in this issue, and we each have different views on it, because there are tradeoffs no matter what.

        My personal view (based on experience modding and admin'ing), is that we should prioritize handling a report ASAP, by the first eyeballs that see it, rather than whose jurisdiction it is. On all but the largest communities, admins are generally more active, and more likely to see the report and take action on it.

    • The AMA is upcoming on Friday, it’s not this thread

      Edit: Leaving this here cause why not

370 comments