nutomic

joined 4 years ago
MODERATOR OF
[–] nutomic@lemmy.ml 3 points 2 days ago

Or even some logic to automatically exclude from the list any instance with more than x% of active users.

[–] nutomic@lemmy.ml 3 points 2 days ago* (last edited 2 days ago)

I posted about this in the admin chat on matrix, but you're right the pull request was merged very quickly.

The lemmyverse link is also a good idea, but users only see it after filling in their email and password. At that point it's unlikely that they would cancel it and go to a different website.

Edit: I'm now thinking to change the joinlemmy code so that any instance with more than x% of active users will automatically be hidden.

[–] nutomic@lemmy.ml 8 points 2 days ago (2 children)

Right, I didn't think how it would affect the total active user count. Will have to think of a solution for that.

[–] nutomic@lemmy.ml 0 points 3 days ago (1 children)

Another proof that Dutch is just German with slightly different writing/pronunciation.

Pas op drijfzand -> Pass auf Driftsand -> Watch out Quicksand

[–] nutomic@lemmy.ml 2 points 5 days ago (1 children)

Why don't you post about these stories then?

[–] nutomic@lemmy.ml 4 points 5 days ago

I mean phone number verification like steam does. It's only one of many possibilities when you are a major company.

[–] nutomic@lemmy.ml 6 points 6 days ago (2 children)

Interesting, I never used digg and didn't know about it's history. It seems like they could have easily fought back bots with captchas, email verification, phone verification and so on.

[–] nutomic@lemmy.ml 40 points 6 days ago (23 children)

I pay around 80€ per month for the lemmy.ml server, plus a few euros for image hosting and domain. So that's around 3 cents per active user.

[–] nutomic@lemmy.ml 13 points 6 days ago

I believe there is still an open issue on Github for this, but no one was interested to help implement and test it. So use the search function and contribute!

[–] nutomic@lemmy.ml 4 points 1 week ago (2 children)

Please open an issue for this if there isn't already one. Then I can have a look once the summer holidays are over.

[–] nutomic@lemmy.ml 11 points 1 week ago

I would be happy to give an interview, but so far no media seems particularly interested in Lemmy.

 

This library is responsible for federation in Lemmy, and can also be used by other Rust projects.

 

This library is responsible for federation in Lemmy, and can also be used by other Rust projects.

-1
submitted 8 months ago* (last edited 8 months ago) by nutomic@lemmy.ml to c/announcements@lemmy.ml
 

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.

Last Friday we finally released Lemmy 0.19.0, after a long development time and extensive bug fixing. Read the announcement to find out about the major changes. A few days later on Wednesday we had to publish 0.19.1 to fix a few more bugs that slipped through.

@phiresky fixed the critical bug with outgoing federation in 0.19. Previously he fixed an authentication bug in lemmy-ui which was blocking the 0.19 release.

@dessalines fixed the broken logic for "hide read posts". He also fixed a problem with email login being case sensitive

@nutomic reenabled pushing to crates.io so Rust developers can easily interact with Lemmy. He also made performance optimizations for /api/v3/site and the optimized the Activitypub context sent by Lemmy, reducing the database size and the amount of data sent between instances. He fixed various tests to prevent random failures in continuous integration 1 2

@dullbananas has long been busy improving the database queries for Lemmy, such as fixing a bug in the way different posts sorts are combined, and improving the test cases.

This is our last update for 2023. It was a very busy year for Lemmy, and it looks like 2024 might have even more changes in store. So lets enjoy these holidays, have a Merry Christmas and Happy New Year!

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.

 

Let's say someone created a Wikipedia clone with Activitypub support, so you can freely read and edit articles on other servers. Basically the same way that Lemmy works. What would be a good name for such a project? Bonus points if the name goes with a cute animal mascot.

Edit: Here you can see the names of existing Fediverse projects.

 

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.

This week we finally started deploying 0.19 release candidates to lemmy.ml, as a final testing step before release. Unfortunately there are some nasty authentication which we have been attempting to debug all week, without success so far. So it will take some more time to fix this and other issues before publishing the final version.

@rasklyd made Lemmy releases for ARM64 platforms possible. @kroese did the same for lemmy-ui. This means that official releases from Lemmy 0.19 will work on devices such as Raspberry Pi.

@dessalines has been very busy attempting to fix the previously mentioned authentication bug. He also worked on other bug fixes and upgraded Jerboa for Lemmy 0.19.

@nutomic again fixed various problems that were introduced during 0.19 development, to get ready for the release.

@Sleeplessone1917 implemented the frontend for user settings import/export. He also started work on an overhaul of context menus.

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.

-1
submitted 10 months ago* (last edited 9 months ago) by nutomic@lemmy.ml to c/lemmy@lemmy.ml
 

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.

@Neshura87 submitted the first ever RFC for Lemmy! It describes how post tags can be implemented.

0.19.0 is getting closer and closer to release, but we are still busy squashing bugs and getting lemmy-ui ready. For now there is another release candidate deployed on voyager.lemmy.ml for testing. Here is the full list of changes since the last release candidate for Lemmy and lemmy-ui

@nutomic fixed a bug with following local communities in the release candidate. He added a first integration test for image uploads.

@dessalines has been busy updating lemmy-ui to account for Lemmy API changes, and squashing various bugs like an issue with timezone db migrations, adding a creator_is_admin field to Post and Comment views.

@SleeplessOne1917 has implemented support for settings import/export in lemmy-ui, as well as some bug fixes.

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.

 

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 published a new release candidate for Lemmy 0.19.0. Note that this so-called release candidate is really a beta. In the future we will use more appropriate version names.

Most importantly it includes the new feature to export user settings, and later import them on another instance.

The Docker image was changed from Alpine to Debian which should improve stability and performance (#3972). This unfortunately broke ARM builds, so we'd need some assistance getting them working again for debian.

The remaining changes are mostly minor improvements and bug fixes, you can see them in the full changelog. Please test the new version on voyager.lemmy.ml or by installing tag 0.19.0-rc.3 on your server. If you encounter any problems, report them on Github.

For Developers: This version includes various API changes compared to rc.1:

  • The endpoints for exporting and importing user settings are at GET /api/v3/user/export_settings and POST /api/v3/user/import_settings. Note that the returned json is not meant to be parsed, but directly stored to disk (#3976).
  • /api/v3/login now sets the auth cookie automatically, so clients might not have to handle it anymore. There is also a new endpoint /api/v3/logout which clears the cookie and invalidates the auth token (#3818).
  • There is a new endpoint /api/v3/user/validate_auth which returns errors in case of invalid auth token. This is necessary because other API actions silently ignore invalid auth and treat the user as unauthenticated. We are changing various endpoints to return simply {"success": "true"} (#3993, #4058 (not included in rc.2)).
  • The endpoint /api/v3/post/mark_as_read can now take an array post_ids instead of single post_id value but remains backwards compatible (#4048).

@nutomic improved the way that titles for Mastodon posts are handled (#4033). He also worked on various minor fixes and enhancements, see here.

@dessalines is nearly done with the redesign of join-lemmy.org. You can see it here, and check the pull request to provide feedback / suggestions. Also worked on cleaning up stale lemmy issues.

@SleeplessOne1917 reworked a much cleaner 2FA interface for lemmy UI (#2179), fixed a bug with the emoji picker (#2175), and added an enable_animated_images setting to users (#4040). Also worked on lemmy-ui-leptos.

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.

 

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. 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, with a two-step process to enable 2FA which prevents locking yourself out. Additionally he is reworking the API authentication 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.

@dessalines is currently implementing a redesign of the join-lemmy.org website. He is also keeping the lemmy-js-client updated with the latest backend changes 1 2 3.

@phiresky optimized the way pagination is implemented. He is also fixing problems with federation workers which are causing test failures and performance problems in the development branch. These problems were introduced during a complex rewrite of the federation queue which was recently finished, and is thought to allow Lemmy federation to scale to the size of Reddit.

@SleeplessOne1917 is implementing remote follow functionality, 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 .

@codyro and @ticoombs have been making improvements to 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. Recurring donations are ideal because they allow for long-term planning. But also one-time donations of any amount help us.

 

The new major version of Lemmy is now ready, and we need your help with testing. Most importantly it uses HTTP for API requests now, which is much more efficient than websocket. Additionally Two-factor-auth is supported. There are also countless other improvements and bug fixes.

You can register on any of the following servers to start testing, no approval required. You can post to your hearts content to find out if anything is broken. The test instances only federate with each other to avoid affecting production instances with spam.

If you encounter any bugs that aren't present in 0.17, open an issue and mention in the title that it happened with a release candicate version. Over the next days we will publish new RC versions to fix bugs that will invariably pop up.

Instance admins can try the new version by using Docker images dessalines/lemmy-ui:0.18.0-rc.2 and dessalines/lemmy:0.18.0-rc.1. Make sure that working backups are in place. For production instances its better to wait at least some days for the major issues to be fixed.

 

The instance list has a couple of recommended sites at the top. They are defined in this file and seperated by language. For most languages there is only one recommendation or none at all, so you can simply add yours by making a pull request.

In case of English, the situation is a bit different. The current recommended instances (beehaw.org and sopuli.xyz) are already quite large and would be shown near the top of the list anyway. So it makes sense to recommend smaller instances instead.

To be recommended, an instance should meet these requirements:

  • It should be a general purpose instance
  • At least one member of the admin team needs to be in the Instance admin chat to coordinate with other admins
  • The admin team needs to be prepared for a large influx of users, both in terms of hardware and moderation

We can use this thread to discuss which instances should be recommended. There is no maximum number of recommendations, but it should be an even number to work with the desktop layout.

On a side note, the instance list itself could use many improvements such as showing more details about instances or using different sorting methods. If you are a programmer or web designer, you can contribute to improve the website.

Edit: If you are a Lemmy admin and want your instance to be recommended, go ahead and open a pull request for this file. Developers can also contribute in the same repo to improve join-lemmy.org.

view more: ‹ prev next ›