Update README.md

README.md

@@ -1,8 +1,23 @@
 # DieKnow
 
-This program should significantly improve the performance of your laptop, especially with the C++. The Python version is known to be relatively CPU-heavy (around 5%). However, this is minimal compared to DyKnow, which uses up to 15% of the CPU consistently, and on an Intel Core i3, there isn't much to spare.
+A bypass of DyKnow.
 
-You'll have to type "exit" to exit the application or some lingering multitasking threads will continue to run in the background.
+DieKnow will significantly improve the performance of your laptop by a large amount, especially on the CPU. However, it will use around 3% of the CPU when running. But this is minimal compared to DyKnow, which uses up to 15% of the CPU consistently, and on an Intel Core i3, there isn't much to spare. It's not lightweight for something to take screenshots of your entire device screen at 4K resolution and at sixty frames per second.
+
+What can DyKnow do (or does do):
+
+* Monitor your device screen (including when you press "Show password" when typing a password)
+* Monitor your search history
+* Monitor what apps you've been on
+* Lock your device
+* Track your device's location
+* Make your computer really, really slow
+* Track your keystrokes
+* Make your computer useless
+
+It's possible that this information could be sold to third-party advertisers for a way to generate revenue, as DyKnow is actually quite cheap for the school.
+
+You'll have to type `"exit"` to exit the application or some lingering multitasking threads will continue to run in the background.
 
 ## Installation
 
@@ -24,7 +39,7 @@ NOTE: this application only works on Windows, as it uses the Windows API.
 
 ### `start`
 
-Start the DieKnow process. DyKnow executables will be terminated forcefully every five seconds, which is sufficient to keep DyKnow consistently closed down. If the delay was too low (or none at all), CPU usage would be very high, possibly as high or higher than DyKnow.
+Start the DieKnow process. DyKnow executables will be terminated forcefully every five seconds, or whatever is set in [`interval.txt`](interval.txt), which is sufficient to keep DyKnow consistently closed down. If the delay was too low (or none at all), CPU usage would be very high, possibly as high or higher than DyKnow.
 
 ### `stop`
 
@@ -67,6 +82,8 @@ DieKnow provides an API that is accessible at [`dieknow.py`](dieknow.py), which
 
 DyKnow creates executables dynamically. Once you kill its process using Task Manager or the `taskkill` command, it restarts right back up, but with a modified executable name. How it does this is unknown, but it likely uses Task Scheduler. My approach leverages the Windows win32 API, specifically the [`TerminateProcess`](https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-terminateprocess) function, to repeatedly close DyKnow.
 
-A `ctypes` precompiled C++ binary is located in [`api.dll`](api.dll), which is accessed by [`main.py`](main.py) to call the C++ functions. C++ is used as it lowers the CPU usage of DieKnow compared to Python. The DLL file is over 3 MBs because it is statically built (with use of the `-static` g++ option), allowing easy distribution of it.
+A `ctypes` precompiled C++ binary is located in [`api.dll`](api.dll), which is accessed by [`main.py`](main.py) to call the C++ functions. C++ is used as it lowers the CPU usage of DieKnow compared to Python. The DLL file is over 3 MBs because it is statically built (with use of the `-static` g++ option), allowing easy distribution of it and without having to manage all the dependencies, such as `<windows>`.
 
 Using a command such as [`taskkill`](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/taskkill) will result in an error: `Access is Denied`.
+
+I was able to program this bypass not because I'm smart, but because the people who programmed DyKnow weren't or thought the students were stupid or both.