(#br6vghq) I mean, hey, mutt is already optimized to handle lots and lots of e-mails. Had I written all this myself, it might be quite a bit slower. 🤣

(#br6vghq) @movq Yeah I didn't design `yarnd`'s active cache / archive just for performance reasons (_it's true, it keeps things performance but also keeps memory usage under control_) but also "human" / "social" reasons too. The ideas is that Twts fall off the Active Cache into the Archive over time automatically.

@prologic (#br6vghq) Could be done, yeah. I don’t know yet if I want to, though. 😁

@prologic (#br6vghq) Mhm. We’ll have to see. 🤔 For now, I’m not seeing performance issues or anything, it’s just … very crowded. 😁

@quark (#br6vghq) Haha, yeah, it’s a ton of traffic recently. I currently have ~27k twts in my box. Honestly, I just skim over new ones, then mark them as “read”, and be done with it. No organisation whatsoever. I don’t know how long this approach is going to work … To be honest, I never expected to see this much traffic in the first place. 🤣

(#br6vghq) @movq I wonder if this is something you can do with `mutt` + `jenny` where you can archive older conversations off automatically or with some key bindings/function? 🤔

@quark @movq (#br6vghq) The way `yarnd` handles this is through two configurable options: - Max Cache TTL - Max Cache Size Twts go through the active cache and are then archived.