- have the system only send 10 events a second, instead of 1000
- don't scan the same package+class name more than once a second
- put each event view scanner on its own thread keyed by package+class
- don't scan if there is already an existing thread for the package+class
this can still cause high cpu usage on views with lots of text
especially if the user continually interacts with it
but is overall much better
to recap:
- a given package+class can only be scanned at most once a second
- a given package+class can only have one scanner at a time
- text to scan will not be scanned if already scanned
- domains to scan will not be scanned if already scanned
Signed-off-by: Tavi <tavi@divested.dev>
some enhanced descriptions added translations and some overall enhancements in terms of "making sure the descriptions aren't too generalized as possible" because some translated functions could need more depth to describe its actual function in a securely matter. Other descriptions could have a more simplified form.
some descriptions could have a rewrite because there are many commonly used english words and definitions wich are already heavily used in the daily german language since most words are latin based and universal/international in use e.g (Performance/Download/). Other words and short terms are not too well known e.g (GUI)
but i know how important they are so i kept it as a translation itself.
Some english technical/development definitions and similar could be partly changed in common german use e.g (Sanity-Tests rather then Sanity-Checks).
Basically for all cases i kept in mind that these translations where technical related to hypatia but shouldn't be to difficult to understand for the not too technically involved user.
In some cases there may have been a too simplified definition e.g "schreiben/umbenennen = write/rename" should be more directed to the not heavily involved technical user because the detection of malware happens on write/rename to "files".
