anarcat
anarcat
> so i ended up actually _compiling_ this code and testing it, and the progress dialog never comes up, because even my largest directory never triggers the "one second" delay....
> ugh. so removing that limit makes it hang on something _else_: just the directory crawler seem to be taking a couple seconds itself, in my case, but the other...
i tried to look at merging `getFoldersRecursive` and `updateSubFolders` and this whole thing is just a mess. there's a lot of business logic that happens in `getFilteredFileInfoList`, so we'd need...
On 2024-08-20 09:36:01, scrubbbbs wrote: [...] > Eliminating `getFoldersRecursive` and adding the progress dialog seems to be a decisive move in the right direction. Rome wasn't built in a day...
@novomesk dupe of #297.
let's break it down. wallabag does this: 1. plain ``: good 2. ``: not great 3. ``: good feedburner does this: 1. ``: broken? 2. ``: good it also has...
this PR should be closed.
i would find having silence notifications useful. i've been drilling through the code to figure out whether there would be some webhook we could use, but couldn't find anything, and...
one thing that could help in implementing this on our own (without patching alertmanager to implement direct notifications) would be to *log* those silences and, lo and behold, there's been...
uh, look at that, i completely forgot i did that. let me fix that PR.