Martin Polehla

Hi, did you solve this problem ?

> One major issue with the previous attempt was that performance with larger numbers of files/folders I just tried with 10 000 and 100 000 files in random folders, and...

### I did more testing of the performance and did some tweaks: * I believe, limited height of FancyTree improved the initialization performance when 10 000 files in root folder...

> @p0l0us Nice to see you are still active on this! Something seems to have gone wrong rebasing, lots of unrelated changes in the PR. I hope fixed. I appreciate...

> Again, I think we have different definitions of "locally ignored" or I am misunderstanding what you're trying to accomplish. Let's start with a plain text description of what you're...

> Why limit it to receive-only folders though? There is no specific reason to limit the feature for receive-only folders apart of more potential bugs and more testing. ### Feature...

> Can we have a discussion about what this is supposed to do and what use case it fulfils? It looks to me like it implements a surprising definition of...

> That's not really what you're doing here, though. You're basing this on files in the database with the `ignored` flag, See `protocol.go` and follow `protocol.FlagLocalIgnoredExisting` please. I mean I'm...

> Yes, you've added a flag to indicate whether the ignored file exists on disk locally. This doesn't change any of my reasoning above, since that is about whether the...

> Whether the list is built and kept in memory during regular scanning, or produced on demand when the API endpoint is requested, is a basic decision to make. Or...