![](https://lemmy.ml/pictrs/image/24716431-8f92-417a-8492-06d5d3fe9fab.jpeg)
![](https://lemmy.world/pictrs/image/44bf11eb-4336-40eb-9778-e96fc5223124.png)
Thank you for bringing this to my attention. We are currently making some last improvements to the RFC, and it should get merged within the next days.
Lemmy maintainer
Thank you for bringing this to my attention. We are currently making some last improvements to the RFC, and it should get merged within the next days.
Well someone has to write the code.
There is no need for any “green light”, if there was a problem with the rfc we would have said so from the beginning. From what I can tell the rfc is not completed yet, and when it’s completed someone still needs to step up to implement it. Even my own rfc which was finished months ago is still not merged and not implemented.
It was always normalized, but recently there seems to be more backlash from maintainers.
We have never rejected any patches from lemmy.world admins or from sublinks developers.
I couldnt find it in the repo, what sort of plugin hooks do you have?
Sure the plugin hooks still need to be implemented. It wouldnt make much sense to do that now before any actual use case exists, then the hooks would remain unused or wouldnt even work properly. Thats why it should be implemented together with a proof of concept plugin.
Its not necessary to learn Rust to improve mod tools in Lemmy. There can be external mod tools implemented as api clients using any language, such as LemmyAutomod. Its also possible to add plugin support for Lemmy, which again can be implemented in various languages thanks to webassembly
This is not true, Lemmy can definitely have plugins and there is an extensive discussion about this topic. The conclusion is that plugins should be implemented in webassembly, so that they can be written in many different languages. See extism for details. Whats needed is someone with a clear use case who can implement a proof of concept, as it wouldnt make sense to add plugin hooks that no one uses.
Also mod tools can be implemented as api clients such as LemmyAutomod.
I dont have time to read all that. The problem with Beehaw is that the admins are extremely entitled, as if we had some obligation to work for them for free. Similar to what is described in OP.
However we are consistently improving the mod tools, and accept contributions in that area. You can see in the dev updates.
What is this “stance on mod features” that you are talking about?
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.
500 Mb symmetrical. It’s more than enough even while running a home server.
Hold on the scammer could spend 8000 usd without even knowing the card’s PIN number?
deleted by creator
Admins and mods can see this in the latest version.
This is already possible.
It’s already largely resolved through the feature to export/import user profile.
Interesting. However in this case the plane came down vertically so the wings/engines would hit the ground beside the building. In case of the pentagon, the plane supposedly flew horizontally at ground level, so the wings should crash directly into the building.
The RFC is merged now!
https://github.com/LemmyNet/rfcs/blob/main/0004-post-tags.md