Lemmy Lead Developer and father of two children.
I also develop Ibis, a federated wiki.
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 will come with Lemmy 1.0
The change only affects posts which were deleted by the creator and have at least one comment. If the post was removed by a mod or admin the behaviour remains unchanged, and only the creator as well as mods/admins can view it.
For comments there is no change. For posts, if you delete a post which has no comments it wont be visible to anyone else. If it has comments and you delete the post, then it will only be accessible by direct link but not via post listings on the community page or frontpage.
This will be partially addressed in Lemmy 1.0 by making deleted posts and their comments viewable, but only by direct link (not via post listings).
In theory apps can do anything that the website can, but this app probably hasnt implemented the feature yet.
We always dream, but usually we cant remember the dreams. It helps to keep a dream journal, ie every morning directly after waking up, write down as much as you remember from last nights dreams (or instead talk about it with someone). Over time you will remember more and more details.
You are using Piefed but this community is only for help with Lemmy.
This is a problem with your instance (lemmy.org) so you will have to contact the admin.
These logs are from the api, not from federation. So a client is trying to access posts and comments which dont exist. Is the Lemmy frontpage looking normal? Regarding federation, other instances would have marked your instance as dead by now. This should be reset automatically after a few days, or you can manually trigger it (eg unfollow and refollow remote communities).
I would also suggest you join the admin chat on Matrix to get more help: https://matrix.to/#/#lemmy-support-general:discuss.online
Por supuesto puedes hablar en Español por aquí.
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 :)
Sounds like an adoption of this bible text. Basically a version of karma.
“Put your sword back in its place,” Jesus said to him. “For all who draw the sword will die by the sword.”
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:
Lemmy 1.0 is backwards compatible with the current API v3. You can try it here. This uses the API from our test instance at voyager.lemmy.ml which runs the latest alpha version.