![](https://lemmy.ml/pictrs/image/24716431-8f92-417a-8492-06d5d3fe9fab.jpeg)
Good example of AI making stuff up instead of simply saying “I don’t know”.
Lemmy maintainer
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 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 @[email protected], @[email protected] and @[email protected] 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.
Well written, it would deserve a separate post.
One of the comments mentions that another app can trigger search through an Android intent. So its better to be safe and close any potential vulnerabilities, but this doesnt seem particularly useful for an attacker.
Im a former contributor to F-Droid with various merged pull requests. Looking at the indicated pull request I really doubt that it was an intentional attack. First of all its easy to forget for a new developer to escape SQL parameters, and the docs dont even mention a risk of SQL injection attacks. And of the users pushing for the PR to be merged, one is a long-time F-Droid contributor, and the other also looks like a real human with many contributions in other repos, so no sockpuppets in sight.
It simply looks like standard open source behaviour, for better or for worse. A new user makes a contribution for a highly demanded feature, and users want it to get merged as soon as possible. Maintainers are discussing the big picture of the change and want to avoid breaking changes, without getting into code review yet. The new contributor seems unwilling to make any design changes to his PR, and gets frustrated that it doesnt get merged as is. The potential vulnerability is only noticed half a year after the PR was opened, at which point it was already de facto abandoned. So not an attack, but simply a developer who is new to open source and doesnt understand how the process works.
We applied for funding last August, but unfortunately we are still waiting for it to be finalized. Seems like NLnet is quite overloaded these days.
We only do major versions around once a year so those could still be named, while using numbers for minor versions. Lemmy is more user-facing than react, so it would make sense to have a more user-friendly versioning.
We didnt make any changes to the Lemmy version running on this instance during the past week. So it must be something else…
You can use pg_stat_statements to find slow queries. Try sorting by top
total_exec_time
.