Lemmy Developer AMA and Dev Update, 2024-01-26, 1500 CEDT
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, @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.
- Liberapay (preferred option)
- Open Collective
- Patreon
- Cryptocurrency
You're viewing a single thread.
Will private messages ever be displayed in a threaded or grouped manner?
Please correct me if I'm wrong, but the current web interface is just a reverse chronological list of all sent and received messages. This can be confusing to follow if one is messaging multiple users over an extended period of time. I think the ability to group messages by user would be useful.
There can definitely be improvements, but I agree that they're low priority. I'm hesitant to put too much work into Lemmy's private messages or its interface, as they're inherently insecure and not E2EE (we even have warnings in the lemmy-ui interface about this).
Its best to rely on messaging apps like matrix and xmpp that were made for that job, which you can add to your profile. We also added a specific matrix_id field to your user settings, which enables a "Send secure message" button.
This is already possible in many Lemmy apps. I built the Quiblr web app and messages are more similar to a messaging app. Many Lemmy apps probably do similar as it's just a front-end change.
Cool! I haven't tried out web apps, but many mobile apps have this feature as well. Would be nice to see this feature merged into the native web interface.
Maybe, if someone implements it. Basically the same answer as all other low-priority feature requests.
I'm personally annoyed with how the default UI shows messages and mostly work on the frontend, so changing that is definitely on my agenda.