lemmy.ml fits those criteria.

https://github.com/mastodon/mastodon/pull/19059

Over three years without any progress.

This is not possible with the way Lemmy is implemented, because each post belongs to exactly one community. This is not something we can realistically change. We are considering to show comments from different posts with the same url together, but that is controversial.

In any case NodeBB, Lemmy and Piefed are different platforms with different implementations and different users. So it makes sense that some features are implemented differently, or only available in a subset of platforms.

This is a known issue and will be fixed in Lemmy 1.0: https://github.com/LemmyNet/lemmy/issues/5210

The best channel is through the issue tracker, for example github.com/LemmyNet/lemmy-ui. In practice Im not sure how the UI could be changed to make this clearer. Do you have an idea, or an example how another website handles this?

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

It seems that the post is getting refetched over federation and marked as deleted again. So you will have to run that SQL query regularly (eg in a cronjob) to restore the post every time. Its also worth setting locked = true to prevent users from commenting.

By the way I opened an issue to fix this properly: https://github.com/LemmyNet/lemmy/issues/6044

You can run the SQL command update post where id = 53505862 set deleted = false. That way it will be visible on db0 again, although not on other instances.

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

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.

curl -H 'Accept: application/activity+json' https://piefed.europe.pub/post/35873 | jq

This directly sends the object json for https://lemmy.dbzer0.com/post/53225502 which fails domain validation. Instead https://piefed.europe.pub/post/35873 needs to send a redirect to https://lemmy.dbzer0.com/post/53225502

I developed the Android app for Syncthing years ago. But then I didnt have time (or motivation) for that anymore. Developing Lemmy is much more interesting for me really nowadays.

Message Customization: Send any custom message in Morse code.

Morse Code Decoder: Convert received Morse code into readable text.

Neat, this means you can talk to someone in morse code without having to learn morse. Did anyone try how well it works in practice?

This feature is already implemented for Lemmy and will be in version 1.0