[-] nutomic@lemmy.ml 28 points 1 month ago

It seems there are always people on the internet who spread negativity about those who actually create things. Best you can do is ignore them.

[-] nutomic@lemmy.ml 27 points 4 months ago

There were optimizations related to database triggers, these are probably responsible for the speedup.

https://github.com/LemmyNet/lemmy/pull/4696

[-] nutomic@lemmy.ml 25 points 5 months ago

Yes that's me :)

[-] nutomic@lemmy.ml 25 points 7 months ago

At minimum it means you don't have to create two separate accounts to make edits on both instances.

[-] nutomic@lemmy.ml 27 points 7 months ago

I was waiting for someone else to create a project like this. But it didnt happen so I had to write it myself when things became a bit calmer with Lemmy.

[-] nutomic@lemmy.ml 29 points 7 months ago

massive fragile ego, frankly horrible, acting shitty

So this is how you see me, all based on two issues out of thousands and never having talked with me directly. Honestly this comment would be a good reason to ban you for harassment and violating the site's code of conduct. But lucky for you I don't care what random strangers on the internet think about me.

[-] nutomic@lemmy.ml 30 points 7 months ago

Its simply not true that we have zero consideration for privacy or user safety. But that is only one aspect of Lemmy, we also have to work on many other things. And we werent silent during the CSAM wave, but most of it was handled by admins and all the related issues are long resolved. Lemmy has 50k active users, its obvious that we are too busy to work on every single thing that some individual user demands.

There is a reason that Lemmy still has version 0.x. If you have such high demands then you shouldnt use it, and switch to another platform instead. And yes you are clearly stoking an attack against Lemmy, I wonder why you hate our project so much.

[-] nutomic@lemmy.ml 29 points 7 months ago

There is a lot of misleading information in this post.

Something that I notice said consistently by those who have little experience in Lemmy admin spaces is “why not just contribute then?”And the answer people try. And this happens. This unfortunately leads into the next point that is the developer teams behavior.

Dessalines and I had some discussion whether the linked issue should be closed or not. Anyway we decided to leave it open in the end. Then some weeks later a user came along and made a completely offtopic complaint that this decision making process is somehow wrong. I admit that I overreacted by giving a temporary ban for this, but mistakes happen and its completely disingenious to spin this as some sort of general toxic behaviour from our side.

There is a fundamental lack of confidence amongst a majority of Lemmy instance admins towards the lead developers of Lemmy.

This is your opinion and I doubt it is as widespread as you think.

Another aspect of this is that the Lemmy devs run two instances: lemmy.ml & lemmygrad.ml

What makes you believe this? I can only speak for myself, and I am not involved with lemmygrad in any way.

The biggest piece that broke all confidence in the Lemmy developers amongst many admins including myself is that during the CSAM spam attacks there was complete radio silence. The developers made no statement on the matter. And when Github requests were made to try and propose ideas about how to fix what happened, the developers explicitly stated they didn’t have time to focus on that. No dialogue.

Correct the CSAM wave was handled by admins on their own. As far as I remember there were no specific feature requests that would have helped in this regard, and anyway they would have taken too long to implement and publish.

As well, when a post was made about Sublinks (A project I will touch a bit more on, and am involved in due to the reasons I have highlighted above) the comments that were made by Lemmy’s lead developers were extremely petty. This lessens peoples confidence in your project, not improves it.

Why do you consider it petty? Its a fact that jgrim never opened any issue for the features he wanted, not did he attempt to contribute with a pull request. Its also true that it took multiple years of fulltime work to get Lemmy ready for production, and I dont see how Sublinks can be any faster when it has only volunteer contributors. That doesnt mean I wish for Sublinks to fail, in fact I hope it will be successful so that admins and users have more choices available, and to improve resilience through independent codebases and development teams.

Generally you seem to have an extremely entitled attitude. Lemmy is an open source project that is provided for free. I would also love to fix all the problems that users report, and implement all those features. But unlike Reddit we are not a billion dollar company with thousands of employees. We are just two individuals funded by donations and working from our homes. There is only a limited number of hours in each day and only so much work we can finish in that time. If you are unhappy with Lemmy then by all means switch to a different platform, because we dont get any direct benefit from having more users.

[-] nutomic@lemmy.ml 23 points 8 months ago* (last edited 8 months ago)

These people previously asked Dessalines and me to participate in one of their conferences, and expected us to pay the full ticket price. I think its really outrageous to charge so much money for setting up some video calls, considering that most people who run the Fediverse don't get any money at all. There are also no recordings published afterwards, which goes completely against the spirit of openness of the Fediverse.

149
submitted 8 months ago by nutomic@lemmy.ml to c/lemmy@lemmy.ml
0
submitted 9 months ago* (last edited 9 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.

73
submitted 10 months ago* (last edited 10 months ago) by nutomic@lemmy.ml to c/asklemmy@lemmy.ml

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.

[-] nutomic@lemmy.ml 29 points 10 months ago

There is no specific release date. It depends how much time we need to fix remaining bugs which are being reported.

-1
submitted 10 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.

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.

[-] nutomic@lemmy.ml 26 points 11 months ago* (last edited 11 months ago)

Yes it includes community follows, saved posts, blocklists and profile data. Here you can see everything thats included:

https://github.com/LemmyNet/lemmy/blob/main/crates/apub/src/api/user_settings_backup.rs#L41-L60

Edit: I just noticed that instance blocks are missing from the export. Added here

124
submitted 11 months ago* (last edited 10 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.

142
submitted 1 year 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.

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.

15
submitted 1 year ago by nutomic@lemmy.ml to c/technology@lemmy.ml

In my experience the translated subtitles were even better than some human-made ones.

223
submitted 1 year ago* (last edited 1 year 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.

We are slowly getting closer to the 0.19 release, although there is still a lot of work left. Client developers should read this post with information about breaking changes to update their projects.

Edit: You can test the latest 0.19 code on voyager.lemmy.ml, or by installing 0.19.0-beta.8 on your server. Be sure to report any bugs on Github.

@nutomic has closed over 100 issues, most of them duplicates, invalid or already resolved ones. He also made numerous pull requests to fix minor bugs and implement small enhancements. This includes a bug fix for federation of admin actions which was released as 0.18.5. He is also changing the way HTML escaping is handled to avoid broken texts.

@dessalines is working on redesigning the join-lemmy.org website, adding the apps and instances pages. Also worked on rewriting the Docker images to use Debian as base instead of Alpine. Additionally he is adding support for new backend features to lemmy-ui (scaled search and cursor-based pagination).

@SleeplessOne1917 has implemented support for new block instance feature, finished implementing the remote follow feature, and updated 2-Factor-Auth to account for a backend rework. He also implemented some bug fixes. He has also been working on adding authentication to 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.

405
submitted 1 year ago by nutomic@lemmy.ml to c/lemmy@lemmy.ml

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.

152
Lemmy RFCs (github.com)
submitted 1 year ago* (last edited 1 year ago) by nutomic@lemmy.ml to c/lemmy@lemmy.ml

We created a new repository for host requests for comment. It is based on the Rust RFC repo and meant to describe how major new features can be implemented. In this way more people can get involved in the discussion, without having to know Rust or getting lost in implementation details. If there is a major new feature you would like to see implemented, please consider writing an RFC first. Also feel free to suggest changes to the RFC process so that it works better for Lemmy.

One RFC was already created a few weeks ago for supporting post tags. It should be added to the repo soon.

1
submitted 1 year ago by nutomic@lemmy.ml to c/announcements@lemmy.ml
1
submitted 1 year ago by nutomic@lemmy.ml to c/announcements@lemmy.ml

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.

view more: ‹ prev next ›

nutomic

joined 4 years ago
MODERATOR OF