I agree that scaled sort is not working ideally right now. However the issues you linked were opened before the feature was released, so they are not relevant anymore. You are definitely welcome to open a new issue about improving the implementation. The scaled sort logic is here, if you have any concrete suggestions how to improve it thats even better. And I would rather improve this existing functionality to make it work as expected, before tacking on an entirely new feature which may or may not work.
Actually scores are regularly calcuated from a scheduled task which runs in Rust. Yes the score caculation is currently implemented in SQL, but it could also be changed to a Rust implementation or a plugin. This would probably need some optimization so that the plugin only calculates scores for recent posts, not every single known post. In any case it would need someone with the time and motivation to implement it.
Tagging would make sense to categorize posts within a single community. But you seem to suggest tags which are shared across communities. I dont really see the point of this, as communities themselves are already used for a global "tagging" of posts. So it would only duplicate that functionality.
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!
If my work on Lemmy is meaningless then please stop using it. You cant have it both ways.
Thanks for the donation!
That sounds great! Be sure to get in contact if you run into any problems or limitations with the API.
I wish everyone could be so humble.
There is already such an API endpoint which is available for mods and admins.