This is a chance for any users, admins, or developers to ask anything they’d like to myself, @nutomic@lemmy.ml , SleeplessOne , or @phiresky@lemmy.world 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 @phiresky@lemmy.world 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.

    • spaduf@slrpnk.netEnglish
      15·
      11 months ago

      While I agree with the content of that article I don’t know if we should give up on Eugen just yet. The Mastodon team has not disclosed what their plan is regarding the groups rework currently on the mastodon roadmap. There is an old proposal here, but I think we have good reason to believe that implementation will be revisited. To that end, it is very important to advocate for the adoption of FEP-1b12 which is the standard that Lemmy uses.

      It may also be a good idea to advocate for the adoption of FEP-d36d both here and on lemmy. This is a standard for group-to-group following. Effectively allowing communities to subscribe to other communities.

      Here’s a slightly older but fairly comprehensive write-up of the situation: https://blog.erlend.sh/group-convergence

    • sab@kbin.social
      12·
      11 months ago

      I think there’s a risk of lacking a coherent direction if decision-making is outsourced too much to the community. Furthermore, core developers might lose ownership of the project and then lose interest. As long as it’s open source, I’m pretty happy to have the core maintainers develop projects according to their own vision, and the community fork it should this vision differ too much from their own. :)

      • Ademir@lemmy.eco.brEnglish
        11·
        11 months ago

        As long as it’s open source, I’m pretty happy to have the core maintainers develop projects according to their own vision

        The problem is, after we as users helped Mastodon to grow strong the dev thinks it is better to do stuff outside of the standards so nothing works for other fediverse platforms. He has too much power and most people are mindless.

      • Blaze@discuss.onlineEnglish
        6·
        11 months ago

        the community fork it should this vision differ too much from their own. :)

        Definitely :)

    • simple@lemm.eeEnglish
      8·
      11 months ago

      Mastodon’s main dev isn’t really open. Have a look at the “Ego” part of this article

      That article was over 5 years ago now. I would expect that there has been massive change now that Mastodon is way more popular, and the project is way more involved. Also, blocks and mutes do work now.

      • sab@kbin.social
        4·
        11 months ago

        Also something to be said about how a thing or two has happened in the last five years. Whatever Mastodon is doing seems to be working for a large number of users.

        It’s not for everyone, and that’s fine. The freedom of choice is why we’re in the fediverse in the first place. But the fact is that quite a few people want what Madison is offering. :)

      • Omega_Haxors@lemmy.mlEnglish
        3·
        11 months ago

        Ah 5 years ago? That explains it. Early mastodon was rough but they seem to have gotten their shit together pretty recently.