![](https://lemmy.ml/pictrs/image/24716431-8f92-417a-8492-06d5d3fe9fab.jpeg)
![](https://lemmy.world/pictrs/image/f3189f30-f8c8-4c4f-b957-e3a7bfd1c784.png)
I couldnt find it in the repo, what sort of plugin hooks do you have?
Lemmy maintainer
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.
Lemmy.ml runs on a single server and is much bigger than db0. Sure you can’t get 100% availability this way but no one expects that.
Images can be stored in S3 so that’s not an issue. And Lemmy has some tracing logs as well as Prometheus stats, not sure if db0 tried looking into those.
I’m not saying you did it wrong, it’s open source so of course you can use it in any way you like. But some ways have a higher risk of breaking than others.
As someone hosting a service like this, especially when it has 12K people in it, this is very scary! While 2 lemmy core developers were in the chat, the help they provided was very limited overall and this session mostly relied on my own skills to troubleshoot.
This reinforced in my mind that as much as I like the idea of lemmy (or any of the other threadiverse SW), this is only something experts should try hosting. Sadly, this will lead to more centralization of the lemmy community to few big servers instead of many small ones, but given the nature of problems one can encounter and the lack of support to fix them if they’re not experts, I don’t see an option.
I disagree with this conclusion. If you had installed Lemmy according to the official instructions, you would have the database, backend and everything else on the same server and would never have run into this particular issue. And any problems youd have would likely be noticed (and debugged) by many other instances too. Your setup is heavily customized so it is only natural that there are few people who can help with it.
Anyway its an interesting journey, thanks for writing down your experience and for improving the documenation!
It should be very easy to distinguish edits and deletes which were made within a few minutes or hours after writing a comment, from those made months or years later right around the reddit blackout.
Has Google never heard of CI to perform such checks?
If people want to help they can contribute to lemmy directly, or write moderation tools in other languages. It won’t help anyone to spend 8+ man years of development only to reach feature parity.
That paper is eight years old and yet there has been no major hack of the Telegram protocol.
Signal is based in the United States, enjoy having CIA and NSA reading all your messages.
Telegram isn’t perfect, but it is infinitely better than Whatsapp because it doesn’t belong to Facebook, and also isn’t from the United States. Also it can be used by normies without problem, unlike Matrix or Xmpp or what have you.
As a workaround you can go into the database and query directly for users with rejected application and email provided. Then write a script to email them. Getting a fix developed, reviewed, merged and deployed will take a few days in the best case. And even longer now because we are busy with lots of things.
Wow this is a great idea. You can make a pull request to link this in the Lemmy docs. Once its a bit more mature we could even merge it directly into Lemmy.
Thats because todays browsers are way too bloated. A fork that trims unnecessary features could be very effective.
Osmand is great, especially for hiking its better than google maps. Only disadvantage is that it has almost no businesses listed.
We have never rejected any patches from lemmy.world admins or from sublinks developers.