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 must log in or register to comment.
Has Lemmy.ml been contacted by law enforcement yet to hand over user data? If yes, when was it, and what did you hand over?
Nope, never.
whats that thing where a company has a ‘we have never been contacted by law enforement or have been forced to disclose data’ sign on their website that theyll take down to implicitly inform users theyve received a request and a silencing order
Warrant canary. I doubt those really work because law enforcement could easily require you to keep updating it.
could you try regardless?
Not a question, just wanted to let you know I how much we appreciate and love you all for making Lemmy happen 🥰🥰
Thank you! Its great that you have been around all these years.
Thx a ton!
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?
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 @nutomic@lemmy.ml 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.
Thx! Goodluck and enjoy the path
Check the NLnet milestones in updated OP.
So many apps die before getting any users. For Lemmy however, when was the first time you really thought “Damn, this thing really might actually take off”?
For me it was long before the reddit migration (which was ~7 months or so ago). I noticed lemmy slowly but surely gaining traction. It felt more dead than it does now, but the trend was slow and steady growth, which is always a great sign. People were using lemmy, liking it, and sticking around.
At the same time, it was clear that we weren’t making the mistake of all the other reddit alternatives, by promising to be a free speech haven for bigoted communities. Those people actively did our work for us by warning their communities to stay away from Lemmy and its tankie devs, thereby making Lemmy a much more enjoyable place from the very beginning. That was a crucial test: we were not willing to sacrifice our values for growth’s sake.
It’s great to see that positivity confirmed by a researcher who did a qualitative and quantitative analysis about Lemmy migration, and finding that >90% of people saw themselves using Lemmy in the long term. We can all be very proud of that, and it means we have a bright future.
Lemmy was meant to be a Reddit replacement from the beginning, so it was always supposed to take off. Even in the early days the tech was working quite smoothly and users were happy so there was no real doubt about it. The only thing missing were more users. However I had no idea how a real migration would actually look like, so it was really overwhelming when last year people started to flood in and everything got overloaded and broke down.
A lot of people say there are a bunch of tankies on Lemmy which really begs the question: Where do you all keep your tanks and can I drive one?
They stay in the bunker except for emergencies like facebooks threats.net . You get to drive one when you can recite the first section of the communist manifesto from memory.
Thank you for being honest, most would deny the existence of the tanks. I’ll get to work on that right away, I wanna drive the tankie tank.
Maybe the real tankies are the comrades we made along the way
First, I want to say thank you for the incredible job you already have done in this area. However, do you have any thoughts on further improving some fundamental Lemmy UX painpoints? Examples such as:
- Migrating accounts between instances
- Tagging users across instances
- Linking communities across instances
- Finding communities across instances
As @phiresky@lemmy.world mentioned we have improvements coming down the pipe for linking content across instances.
Community linking and user linking do work currently (for example I just linked phiresky above), and a community example would be !risa@startrek.website , but we could improve this by extending it to posts and comments, as well as creating a url link standard that would work across apps.
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
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.
Do you have any estimate of how much storage (in GB) all the posts ever posted across Lemmy have taken up, to date? (Excluding media)
The SQL table for posts is 1.6 GB on lemmy.ml, and 5.7 GB for comments. That probably accounts for a majority of content on the Lemmyverse.
To add, lemmy.ml’s entire DB compressed as a
xzwith-0strength is about3.7 GB. But that also includes the activity tables which aren’t vital.1.6GB is impressively small for anything by modern internet standards
Back when the first Reddit exodus happened, there was a group heavily DDOSing many of the popular Lemmy instances. While it was a great opportunity to optimize Lemmy, did you ever find out who that attacker was?
Echoing the concern of @interdimensionalmeme@lemmy.ml, I want to ask about the issue of a lot of communities becoming big on different instances, to the point they consolidate the moderation and engagement power and ability for users. Posting to them is the only way to get ample engagement, even if same communities exist on other instances. This needs to be rectified.
Same communities across servers should be possible to engage with in a metacommunity format. This will be a game changer for Lemmy.
Yes, I did say in another comment that this requires the benevolence of admins/mods across instances. Each community may also have its own unique sub culture, just like Reddit, which complicates the problem even more.
IMO the only possible solution that is also user customisable is meta tagging for communities that users can utilise to create custom communities, which would be a subset of the multicommunities/multireddit style feature.
What are some cool “Lemmy Adjacent” projects you know of and want to share? (Things like LemmySchedule or Toast.ooo’s Canvas)
One that I can think of rn, is @CannotSleep420@lemmygrad.ml 's lemmy-bot, as well as ridoukousage’s TLDR bot.
With the web being so ad-infested and completely owned by google, people have noted how the TLDR bot means they often don’t have to leave their lemmy app at all, and can stay behind its privacy shield.
While of course I do think we can code a lot of functionality directly in to lemmy in a way that we couldn’t with reddit, there’s undeniably a lot of potential with bots that can do different things for us.
When and how are you going to address the thousands of open issues in the Github repository, that contain UI bugs, missing error messages (something looks as if it was sent for example if you send a direct message with too many characters, but actually isn’t), backend issues and other assorted bugs?
When we have about a dozen more developers. So far only dessalines and i work on Lemmy fulltime, and besides solving issues we also have to review pull requests, prepare releases and much more. So its just not enough time to keep up with all the new issues let alone resolve the whole backlog.
Thank you. A follow-up question: You sound like most things have to be done by full-time developers. Is there a healthy open-source community around Lemmy development? Do people submit enough pull-requests to fix bugs? Do people from the community contribute a substancial amount? features?
Of course contributions by volunteers are also welcome. However there are very few of those who are consistently contributing (particularly phiresky and sleepless one mentioned in op). And because they have a fulltime job their contributions are much smaller than mine or dessalines’. After the Reddit migration lots of people opened pull requests to implement new features, but most of them were abandoned after noticing how much work it takes to address review comments and actually get the pr merged. So fulltime devs seem very much preferable because they can put their full attention to Lemmy, and get a lot more done.
We’re no different from 99% of open source projects: there are a lot of one-off contributors that just do a feature or two they’d like to have, but the vast majority of work is done by a handful of core devs. This is why you should always base your infrastructure and decisions to support those devs, rather than cater to one-off contributors.
I hope those wants and needs aren’t mutually exclusive. I think most open source projects do a good job in catering for both. I’m not involved in Lemmy development so I don’t really know what’s going on here. But I’ve sent one-off contribution to various projects, sometimes contributed single features or helped to sort something out. It always felt appreciated.
Sure, a drive-by commit every now and then and no responsibility is a completely different level than maintaining a (large) project and putting in that effort and dedication. I think a healthy open source project has both. Maintenance and the responsibility/decisions by a core team. And the community contributions make up by adding diversity, being close to what the user needs and adding manpower by a larger group of people, meaning the individual contributions might be smaller, but by many more people. Good communication between the devs and the community usually helps to get quality contributions.
How did you feel when everyone was coming from Reddit to Lemmy?
Very excited, and then very overwhelmed because everything started breaking left and right.
Excited, but also extremely stressed out and exhausted. For about 2 months I was getting an average of 4 hours of consistent sleep a night after that happened. We were very happy when things calmed down.
Do you feel fully recharged now, or still catching up from the intensity of it all?
Mostly recharged from that now.
Good to hear. Thanks for the work you do on Lemmy. It’s nice to be free from the corporate machine that is Reddit.
No probs!
deleted by creator
So basically Oauth support? Theres an open PR for that.
First of thanks a lot for the effort that you put into creating lemmy. You have created a really friendly and welcoming place!
I have a question regarding licenses. When you started developing lemmy, what were the reasons for your choice of the AGPL? As you are marxist-leninists, did you also look into other licenses like the the Anti-Capitalist Software License?
AGPL was already used by most existing Fediverse platforms, and ensures that all code changes need to be published. Its basically an improvement over GPL which also takes effect when the software is hosted on a server, not running on the user’s computer.
The Anti-Capitalist Software License is not an open source software license.
That alone rules it out.
To me, AGPL is the most pragmatic choice. As a hard copy-left license, it enforces derivative works to adopt the same license, unlike the more open and “soft” copy-left licenses that let corporations capture and digitally enclose your labor as they see fit.
