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.

  • glibg10bEnglish
    287·
    11 months ago

    Please stop using time zone abbreviations. Everyone can read an offset (UTC +02:00 in this case). But almost everyone has to look up the abbreviation

    • DessalinesOPMAEnglish
      9·
      11 months ago

      I linked a timezone convert link (before I updated the post), which I think I’d have to do even if we used the UTC offset format. I must be just far away enough from UTC to not know what my offset is at any given time.

    • Microw@lemm.eeEnglish
      92·
      11 months ago

      No, I can not read an offset. Because we have summer time and winter time here, and I dont instantly know what the offset is for which one.

      • toastalEnglish
        21·
        11 months ago

        Developing countries still catching up to the no-DST of the rest of the world. Asia, Africa, Central/South America 💪

    • davidgro@lemmy.worldEnglish
      2·
      11 months ago

      Time math gets a bit difficult far enough from UTC. Where I live virtually any event in Europe or Asia will be happening on a different day there than here, so it’s not fun to try and figure in one’s head.

      The only universal solution is to link to a converter site.

      Personally I wish everything supported the automaticly-converting timestamps I’ve seen in Discord which just show up in local time or as a countdown.