Here is our regular update that explains what we have been working on for the past two weeks. This should allow average users to keep up with development, without reading Github comments or knowing how to program.
We should also have a bugfix release for a few issues with the last release, and have 0.19.8 sometime soon.
flamingo-cant-draw
avdb13
dessalines
Nutomic
- Add test cases for community with non-ascii name (ref #5239)
- Return content of removed comments for admins (ref #5232)
- Add note wrapper (fixes #2657) (#5221)
- Enable site languages for new user (fixes #5234)
- Instance blocks with mod log entry and expiration (fixes #2506)
- Allow bypassing image proxy for specific domains
- Add note wrapper (fixes #2657)
- Proxy pictrs healthz endpoint
- More test coverage for private community, fix some bugs
- Guess image mime type from file extension (fixes #5196)
- Dont sanitize RSS content manually (fixes #5171)
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 # to comment.
Any update on improving Lemmy fundraising process?
KDE recently did a post where they describe the result of adding a notification asking for donations. the money they received from only paypal alone in the 7 days of December is almost 5 times higher (62K) then their biggest previous month (October 13K).
Lemmy donations are down from march to today , while piefed is having a modest organic growth . maybe this could boost development resources bringing features users have been asking for years and improve the speed of experimentation that will help perfect Lemmy’s design and feature set.
Thanks for the hard work again!
No probs! We have an issue to discuss more funding options, because it definitely is a problem. Only 2 full-time devs is not enough to handle this project and all its requests, and we need to grow our lemmy dev coop to keep up. Minimum I’d say we’d need 4 full-time devs in different areas just to keep up with issues.
I’m definitely open to adding those annoying wikipedia-style notifications inside lemmy-ui to hit a fundraising goal, because they do work. There are other possibilities too.
maybe this could boost development resources bringing features users have been asking for years and improve the speed of experimentation that will help perfect Lemmy’s design and feature set.
Most of those features have been funded: https://join-lemmy.org/news/2024-09-11_-_New_NLnet_funding_for_Lemmy
iirc they were already listed as goals in previous NLnet grants, so it has already been a while, not mention that Lemmy budget is a drop in the ocean compared to reddit and that money could definitely be used.
If you’re referring to this: https://codimd.tyhou12.xyz/s/TukD_H96z , I think this was a plan before they got the grant.
Money could be useful, but I also feel that now the issue is finding people willing to write the code
Thank you!
o7
Thanks for your work.
Ignore the ungrateful ones
No probs!
Awesome!
Is there a roadmap somewhere?
I have some issues I’m prioritizing, but you can either look at our github, or the milestones as to the upcoming features.
Thanks for the changes 🙏 I wonder, is 0.19.8 going to be last 0.19 before 0.20? I’m planning to upgrade if its stable enough.
Not sure, if ppl find other bugs we may need to do more 0.19 releases. 0.20 will have a lot of breaking changes.
what is necessary for lemmy to reach a version 1.0.0 ? Does the current 0.19 number mean that lemmy is not stable enough yet?
The current number is because it’s very much still in early development and the developers reserve the right to make breaking changes with any release.
I don’t know that we’ll ever get to a 1.0 status, because feature development hasn’t slowed down, and doesn’t seem to be anytime soon. We’d need like 3 more devs to even not get behind.
