![](https://lemmy.ml/pictrs/image/24716431-8f92-417a-8492-06d5d3fe9fab.jpeg)
![](https://lemmy.world/pictrs/image/cd3bcb14-6e19-4c76-b6d4-2461bd60e545.png)
Those are pretty common opinions. It’s sad that some people cannot accept them.
Lemmy maintainer
Those are pretty common opinions. It’s sad that some people cannot accept them.
Good example of AI making stuff up instead of simply saying “I don’t know”.
No that’s not merged yet, still needs more feedback from plugin devs.
The key is refreshed after 24 hours so it will work if you wait a bit.
There were optimizations related to database triggers, these are probably responsible for the speedup.
No that’s a completely different issue.
Yes something seems to be broken, but so far we don’t have any idea what it might be. On Monday we will deploy the 0.19.4 release candidate which has various performance improvements, hopefully that will help.
Yes I have more time available than expected, at least for now. And whenever I don’t program for a while, I get a strong urge to write some code so I can’t stop myself.
Yes I have more time available than expected, at least for now. And whenever I don’t program for a while, I get a strong urge to write some code so I can’t stop myself.
Alright Ive added @kevincox@lemmy.ml, @CrypticCoffee@lemmy.ml and @Lettuceeatlettuce@lemmy.ml as mods and removed the inactive ones.
I just opened an issue about it: https://github.com/LemmyNet/lemmy/issues/4744
This, particularly reports are not fully federated.
True there are a lot of issues related to notifications. I will see what I can do.
Here is the relevant issue, but no one is working on it currently.
It was always normalized, but recently there seems to be more backlash from maintainers.
Something filled up all the server RAM, not sure what. A restart fixed it.
We have never rejected any patches from lemmy.world admins or from sublinks developers.
Well written, it would deserve a separate post.
I couldnt find it in the repo, what sort of plugin hooks do you have?
You can use pg_stat_statements to find slow queries. Try sorting by top
total_exec_time
.