crosspostato da: https://lemmy.ml/post/16017036
Ecco il nostro aggiornamento regolare che spiega su cosa abbiamo lavorato nelle ultime due settimane. Ciò dovrebbe consentire agli utenti medi di tenere il passo con lo sviluppo, senza leggere i commenti di Github o sapere come programmare.
Stiamo preparando il rilascio di Lemmy, nelle prossime settimane, ma abbiamo ancora alcuni problemi da risolvere e dei test da eseguire.
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're readying the release of Lemmy v0.19.4
(currently on 0.19.4-rc.2
), in the upcoming weeks, but still have a few more issues to address, and testing that needs to be done. If you'd like to help us test betas to help find issues, you can go to https://voyager.lemmy.ml or ds9.lemmy.ml for the newest RC, or run your own test ones locally from our beta docker tags.
Please do not run unreleased builds in production, as these could cause issues which require some manual intervention to fix.
We've also added a few github milestones for our upcoming releases, to keep track of what we'll be working on, but you can also look at our pending pull requests.
@flamingo-cant-draw increased the character limit for alt-text fields.
@dullbananas just graduated from high school and will have a lot more time to work on Lemmy for a few months. Has been working on a custom database migration runner.
@matc-pub cleaned up and added a lot of asynchronous loading for various components in lemmy-ui.
@sleepless and matc-pub fixed an issue with leap years in lemmy-ui.
@sleepless fixed a bug with admin settings in lemmy-ui, fixed an issue with language not allowed, fixed an issue with video thumbnails, and upgraded to a non-deprecated QR library. Has also been adding a lot of the backbone for lemmy-ui-leptos.
@nutomic fixed some issues with importing partial settings backups, 2, made NodeInfo standard compliant, and upgraded to 2.1, added some test cases for user reports, removed unused federation code, added a stricter rate limit for logins, made password reset tokens non-reusable, marked DB fields as sensitive so they don't show up in logs, allowed passing of command-line params via environment vars. Also prevented removal of comments which are already deleted, and configured a max comment width in clippy.
@dessalines fixed some issues with image proxying, 2, made some fixes to our woodpecker CI jobs. Replies and mentions are now correctly hidden for blocked users.
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.
Immagini bene! La comunità reagisce solo quando è citata nel messaggio di apertura di un Thread.
Aggiungo che se viene citata più di una comunità Lemmy, solo una di esse aprirà il Thread.
Se invece viene citata una comunità Lemmy insieme ad altri gruppi Activity Pub, come i gruppi Friendica, allora quello che succede dipenderà più o meno dal caso (non è proprio così, ma rende l'idea) e potrebbe non aprirsi alcun thread su Lemmy... 😂