hey @lain could pleroma have like an "account timeout" where accounts that haven't logged on in some specified time will stop fetching posts for the accounts they follow? the reason I ask is basically my experience with an instance that used to be big but currently only has 5-10 active users a month: the instance is buggy, slow, big db, 500s, missing posts, etc. and I think it's mainly because there are 1000 user accounts, but it's a massive waste of resources because it's like those 990+ accounts haven't ever left... the accounts are still active fetching tons of posts, and those bloat the DB, increase DB response times, slow the mediaproxy down, and all of this causes problems doing routine things like performing activities (any) and even refreshing the page. the admin recently had to double their hardware specs just to keep up...
@teto I'm sorry, I'm just getting frustrated and had a weird day, I don't know how to explain it. I'm not referring to the old inactive account's posts being fetched, I mean they're the ones receiving new posts and they haven't logged in for 8 months or whatever
let's look at it this way, let's say you and I are the only people active on a server, and 100 other accounts are on that server. What happens is those 100 inactive accounts eat up resources for someone who is not even there. It fills up the db, it wastes cpu time and ram, it wastes storage, it clogs the media proxy, etc., it slows down the instance.
What I wish would happen is those 100 accounts would not be doing any of that.... so that the active resource usage is lower. this would make it cheaper to run an instance, it would also make running an instance long-term more feasible (12 months or more), and it would also keep resource usage down network-wide.
@jesu@lain well an additional setting could be "do not send notes older than x days" but the nature of the fediverse would mean this is always up to the admin of that instance
@teto@lain it's still going to eat a minute amount of resources, plus the opposite end, the sending server, it has no idea so that's wasted resources there
@jesu@lain imo pleroma having an auto-ignore or delete function that runs for any "note" older than x amount of days would be beneficial in general. Not like I know anything about hosting pleroma or anything like that hehe
@jesu i really doubt that a too busy server or a too full db is really the issue. i run the oldest pleroma server (pleroma.soykaf.com) on modest hardware, and a lot of activities come in. lain.com is on a small system, too. please check if the db settings have been changed, the default db config is the number one reason why instances become slow.
@lain I think so, yes... hmm... then it would go the *other* way around, don't send statuses to an inactive account, but we don't control other servers... hmm....