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.

  • GravitySpoiled@lemmy.mlEnglish
    85·
    11 months ago

    Is there a public roadmap of some sort?

    Maybe a blog post like “a year in review and what’s up for this year”

    I’m not talking about bugs or minor tweaks. Just a general where are we, where are we coming from and where are we going to? What are important milestones?

    • Dessalines@lemmy.mlOPMEnglish
      35·
      11 months ago

      I’ve just updated the post body with some updates about this, but if we get approved for another year of funding from NLNet, the the two new devs will be working on these milestones in 2024 (still a draft at this point).

      Being an open source project, we can afford to be less strict about a roadmap, as anyone (including ourselves) can take on any of the open issues on the issue tracker. Part of the fun of these is getting to pick which things you’d like to work on, and that you personally think are important.

      Outside of maintenance-related tasks and merging PRs (which does take a significant chunk of our time) of course @[email protected] and I both have things we’d like to prioritize this year. My main priorities are:

      • Getting Jerboa as fully functional as lemmy-ui.
      • Notifications (Unified push).
      • Working on lemmy-ui-leptos, our proposed replacement web UI for lemmy-ui written in Rust.
      • Performance improvements (DB, federation code)
      • Stabilizing the API
      • Becoming fully funded by donations, and growing our dev co-op.
      • Steve@communick.newsEnglish
        22·
        11 months ago

        I wouldn’t put a timeline to it. Just a list of features, broad and specific. As time goes on, they can be marked as “in progress” or “included”. New things can be added over time, or made more specific. All without timetables. For now call it a wishlist.

    • Blaze@discuss.onlineEnglish
      22·
      11 months ago

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

      Edit: Leaving this here