@mischievoustomato@genmaicha@scathach There's also a similar setting, but only for sensitive posts. It's probably somewhere in settings, but it's easily accessed with the "filter" icon on the timeline header.
@mischievoustomato If your system doesn't come with a cron daemon by default, you are using a bad system.
Imagine needing to write 5+ lines of INI configuration to a specific file in your home directory and running systemctl --user enable something.timer, for a script to fire every few minutes.
@munir@m0xEE@mint Yeah, make sure to put 20 as the number of connections (or more if you are running also something else that uses the DB on the same box) and don't use the "network storage" option as your storage. It will output few configuration lines, which you should then change in your postgresql.conf file.
Depending on how much free RAM you have on the box, maybe increase or decrease the effective_cache_size setting. And maybe increase the random_page_cost to something like 4. The rest should be fine to copy as is.
EDIT: postgresql restart is probably required for all changes to take effect. Pleroma should ideally be shut down for that, but it will survive even if it is not.
@dj@m0xEE@munir@mint Glussy is a retard, Pleroma isn't configured to use that many and there's not point in doing that anyway. 90% of the time Pleroma here uses 10 connections leaving the other 5(?) unused. 90% of the time Pleroma here uses 2 connections leaving the other 8(?) unused.
It just uses memory that can be used elsewhere for no reason.
Meanwhile I have to lookup the manpage for systemd timers every time when I want to set what day of the week the timer should fire and the syntax for it.
@icedquinn@jae@newt Yeah, I've built a computer for someone in my family and they didn't want to pay for Windows and also weren't fond of re-learning everything since they were coming from XP to 10. Mint (Ubuntu LTS) was a good solution for that.
@fluffy@icedquinn@jae@newt System becoming unbootable three times in those years because Ubuntu is just more broken Debian and shipped unbootable kernel updates for the Ryzen 3000 APUs. Also there was some amdgpu flag that needed to be set for the GPU to not crash after waking up from S3.
@jae@icedquinn@newt I have a very big problem with wasting my time on unnecessary stuff, so any corpo that has a lot of completely unneeded bureaucracy is mostly a no for me. I simply can't handle it.
@jae@icedquinn@newt Computer you configure once and don't want to touch it for years to come. So not your personal machine, but a computer for someone or a computer that won't have stable internet access for long periods of time.