With 4500 posts per minute you will probably get a lot of other scaling issues too, like with your database or the processing of incoming and outgoing activities. In any case its a good way to learn how Activitypub works. Is the code open source? Dont see it on your codeberg.

Using the plugin system you basically just need a way to get notified about each new post and comment, right? I expect that will be one of the major use cases for plugins. We will likely provide various official plugins, eg push notifications for Android and iOS. The same thing should also work for you.Version 1.0 will let you subscribe to communities to get notifications for all new posts and comments (code).

To get new posts and comments for all known communities you only need to make regular requests to /api/v3/post/list?limit=50&sort=New&type_=All and /api/v3/comment/list?limit=50&sort=New&type_=All. Its not necessary to make separate requests for each community. The default rate limit allows 180 read requests per minute so you can comfortably poll this every second (in practice every 30s or so should be enough). If you miss an item (ie post or comment id was skipped) just load the following page.

The plugin system in 1.0 would be another option. It will still take some time until that is released, but there shouldnt be any reliability issues.

Youre right that federation solves these problems, but instead you get another problem of writing all this federation code and making sure it is compatible with different platforms. Lemmy’s federation code has around 12k lines so that is a lot. It seems much simpler to use the API for Lemmy, Piefed etc and write abstractions for common functionality.

Anyway this is my opinion. Its your project so in the end its your decision how to implement it.

Donations are to pay for the development of Lemmy which is a full-time job and pays for our bills. Donating to Lemmy does not mean “supporting transphobes and tankies”, thats a really weird thing to say.

Interesting, why do you think that scriptable moderation bots need a completely new platform? Wouldnt it be much easier to utilize the Lemmy api directly?

Most of these features are also implemented in Lemmy, and others too such as private communities (which can only be browser by users that were manually approved by moderators). However we have very high standards for correctness, performance and UX so it takes a while to get all of this released in the upcoming 1.0 version.

You can donate for Lemmy development through the link below. Thank you in advance :)

https://join-lemmy.org/donate

To everyone in this thread, if you notice a problem in Lemmy please open an issue. We are only two developers and dont have time to browse the Fediverse all day to come across such things. Only if we know about a problem can we actually fix it and make a new release.

For reference here are the issue and proposed fix:

• https://github.com/LemmyNet/lemmy/issues/6016
• https://github.com/LemmyNet/lemmy/pull/6017

I had a video chat with them once, but afterwards they ignored me. So they are clearly not interested in giving us a grant.

Adding a new sort type is not a big deal, so dont worry about it. And a new admin setting for this would also require UI changes, so the new sort type is easier overall.

The current sort options calculate the rank for each post only from the data on that post (number of votes, creation time). Your suggested algorithm looks much more complicated than that, as it requires two iterations and needs to access data from multiple posts at once. Im not sure if this can really be implemented in a way thats performant enough for production use. Anyway feel free to open a pull request, then hopefully other contributors can help you to get it working.

Sounds interesting, though from your links it’s not clear to me how exactly it works. Depending on that it could make more sense to implement as a separate sort option, then each user could try and compare it to the existing sorts.

The proxied images will be refetched from the origin if they cant be found locally. There should also be a configurable maximum size for the image cache but I dont see it mentioned in the pictrs readme. So like Dessalines said you need to ask the developer directly.

The ranking is implemented in a rather complicated way for performance reasons:

• First there are SQL functions which calculate the rank for a specific post or comment (defined here)
• These SQL functions are used by a scheduled task which updates post ranks at a regular interval (defined here)
• Then there are the database tables which store the calculated rank (eg post.hot_rank)
• Also the API parameters to specify the requested sort, and preferences for default sort options etc
• These params are used in the post listing db query to sort posts by the given rank field (here)

The “Chat” option does just that, with newest comments at the top.

Showing crossposts below comments doesnt work if you have a thread with 100+ comments as it keeps auto-loading more comments. Hiding the crosspost details themselves seems unnecessary as we render them rather small. A button to expand these small details into the full post view with comments also makes sense to me.

Read posts already show with a different color. So this could be a problem with your browser, or the specific Lemmy theme you are using.

Looks similar to the new UI in the PR linked above, except you have to expand it manually.

Just noticed that this post is already two weeks old. Im aware of the other discussion, there are a lot of ideas and we still need to decide what is the best way to implement it.

Could you post a link or screenshot to see how Photon displays crossposts?

I implemented this recently: https://github.com/LemmyNet/lemmy-ui/pull/3387

Outgoing federation actions are kept for 7 days. So if your instance is down shorter than that it will catch up with everything.

This is not possible unless you are an instance admin and query the database directly with sql.