update readme

Author: PandorasFox

README.md

@@ -5,16 +5,13 @@ it is primary intended to be used with [niri](https://github.com/yaLTeR/niri) an
 but I'm open to implementing other compositor IPC agents once it is feature-complete.
 
 > [!NOTE]
-> pandora is functional, performant, and generally usable. New feature extensions (such as lockscreen functionality) are still being implemented.
+> pandora is performant and usable as a basic parallalx wallpaper daemon. New feature extensions (such as 2d scrolling & lockscreen functionality) are still being implemented.
 
 ## installing
-    cargo install --path .
+    cargo install --git https://github.com/PandorasFox/pandora
 
 ### usage
 
-> [!NOTE]
-> config file moved to its own directory because of inode shenanigans
-
 Make sure you copy the included `sample files/pandora.kdl` to `~/.config/pandora/pandora.kdl`
 (or `$XDG_CONFIG_HOME/pandora.kdl`), and edit it to reflect your outputs
 and desired wallpapers. It has some placeholder values of the various options
@@ -39,20 +36,15 @@ You will also need the following in your niri config:
 ## considerations
 
 Due to image geometry being critical for Pandora's many threads to operate across the board,
-some components (such as the Niri agent) won't be able to start up if an invalid or non-existant image is specified in
-the config file.
-
-Changing an output mode/resolution during runtime Doesn't Crash, but still needs some poking at to make it less jank (e.g. restarting the threads in-place leads to missized images sometimes?). Output plug/unplug events work fine though :)
+some components (such as the Niri agent) won't be able to start up if an invalid or non-existant image is specified in the config file.
 
-The config file will live-reload if-and-only-if it can successfully (pre)load every image in the config file, which should make this easier.
+There's live config reloading for playing with animation slowdowns and whatnot. The config should only be reloaded if all images in the config can be loaded (this is not strictly enforced on the initial config load, but will log warnings at runtime when reloading the config file).
 
 ## misc notes
 
-(mostly for myself to keep track of minor tidbits)
-* render command will eventually want a bit depth/buffer format option at some point
-  * outputs watcher thread will need to rig up a callback for the wl_shm (or dma?) object .format event => check available formats there
-* [session lock nonsense](https://wayland.app/protocols/ext-session-lock-v1) is pretty straightforward, just need to go write a generic lock thread
-that handles the lockscreen surfaces all in one thread (e.g. not using the existing render thread logic) for some mild separation
+* render command will eventually want a bit depth/buffer format option at some point.
+  * I have an HDR monitor, so I have a vested interest in testing and implementing this
+  once support lands in Smithay.
 
 This is my first rust project in a little while, and my first Wayland/graphics project ever, so feedback on
-those aspects is welcome. I still need to do.... a few different refactorings before adding more features.
+those aspects is welcome.