this post was submitted on 25 Jan 2024
392 points (98.5% liked)

Announcements

23319 readers
1 users here now

Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.

You can also find major news on join-lemmy.org

founded 5 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 9 points 10 months ago (2 children)

What does lemmy v1 look like?

[–] [email protected] 10 points 10 months ago

I'm sry I can't give a good answer there... but to me it seems like when we go a certain length of time (not sure how long) without any breaking changes. That will have proven that the API as it exists is stable and well-formed.

That seems a long way off atm, because of all the features and new fields we've been adding and modifying on existing data structures.

[–] [email protected] 3 points 10 months ago (2 children)

Nutomic said in another comment:

Yes once we reach 1.0 there will be way fewer breaking changes and then it will be easier to do more frequent releases.

So maybe that?

[–] [email protected] 5 points 10 months ago

Yes thats it, 1.0 just means there are no more breaking changes (until we decide to release 2.0).

[–] [email protected] 5 points 10 months ago (1 children)

I'm more curious what it will take to get to 1.0, rather than what happens after 1.0.

[–] [email protected] 4 points 10 months ago

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.