Some years ago we used to post weekly development updates to let the community
know what we are working on. For some reason we stopped posting these updates,
but now we want to continue giving you information every two weeks about the
recent development progress. This should allow average users to keep up with
development, without reading Github comments or knowing how to program. We’ve
been working towards a v0.19.0 release of Lemmy, which will include several
breaking API changes. Once this is ready, we’ll post the these changes in dev
spaces, and give app developers several weeks to support the new changes. This
week @nutomic finished implementing the block instance feature for users
[https://github.com/LemmyNet/lemmy/pull/3869]. It allows users to block entire
instances, so that all communities from those instances will be hidden on the
frontpage. Posts or comments from users of blocked instances in other
communities are unaffected. He also reworked the 2-Factor-Authentication
implementation [https://github.com/LemmyNet/lemmy/pull/3959], with a two-step
process to enable 2FA which prevents locking yourself out. Additionally he is
reworking the API authentication [https://github.com/LemmyNet/lemmy/pull/3946]
to be more ergonomic by using headers and cookies. Finally he is adding a
feature for users to import/export community follows, bocklists and profile
settings [https://github.com/LemmyNet/lemmy/pull/3976]. @dessalines is currently
implementing a redesign of the join-lemmy.org website
[https://github.com/LemmyNet/joinlemmy-site/pull/243]. He is also keeping the
lemmy-js-client updated with the latest backend changes 1
[https://github.com/LemmyNet/lemmy-js-client/pull/184] 2
[https://github.com/LemmyNet/lemmy-js-client/pull/185] 3
[https://github.com/LemmyNet/lemmy-js-client/pull/181]. @phiresky optimized the
way pagination is implemented [https://github.com/LemmyNet/lemmy/pull/3872]. He
is also fixing problems with federation workers
[https://github.com/LemmyNet/lemmy/pull/3960] which are causing test failures
and performance problems in the development branch. These problems were
introduced during a complex rewrite of the federation queue
[https://github.com/LemmyNet/lemmy/pull/3605] which was recently finished, and
is thought to allow Lemmy federation to scale to the size of Reddit.
@SleeplessOne1917 is implementing remote follow functionality
[https://github.com/LemmyNet/lemmy-ui/pull/1875], which makes it easy to follow
communities from your home instance while browsing other instances. He is also
fixing problems with the way deleted and removed comments are handled
[https://github.com/LemmyNet/lemmy/pull/3965]. @codyro and @ticoombs have been
making improvements to lemmy-ansible
[https://github.com/LemmyNet/lemmy-ansible], including externalizing the pict-rs
configuration, adding support for AlmaLinux/RHEL, cleaning up the configuration,
as well as versioning the deploys. These will make deploying and installing
Lemmy much easier. ## 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
[https://join-lemmy.org/donate]. Recurring donations are ideal because they
allow for long-term planning. But also one-time donations of any amount help us.
- Liberapay [https://liberapay.com/Lemmy] (preferred option) - Open Collective
[https://opencollective.com/lemmy] - Patreon
[https://www.patreon.com/dessalines] - Cryptocurrency
[https://join-lemmy.org/donate] (scroll to bottom of page)
Is this useful to anyone? Would it win over enough libs to federate with lit.cafe?
The actual text:
This week @nutomic finished implementing the block instance feature for users. It allows users to block entire instances, so that all communities from those instances will be hidden on the frontpage. Posts or comments from users of blocked instances in other communities are unaffected.
I think that would let smaller instances that don’t wanna be overwhelmed by our posts avoid that but still let them see our comments on their posts.
we love our big beautiful devs folks, don’t we?