X-Git-Url: https://git.xandkar.net/?a=blobdiff_plain;f=README.md;h=f95d159e9bb45758db2e553eecebdcb523c99427;hb=1fb22bdbf04f83c87c91c7e20e26f06b8ba7af62;hp=ee1a6b7bbb301e7c3b91e984d3b97a7d0a7575fa;hpb=476fcb1f8d869a0a4cdcee3546645165544aa1cb;p=khatus.git

diff --git a/README.md b/README.md
index ee1a6b7..f95d159 100644
--- a/README.md
+++ b/README.md
@@ -168,6 +168,7 @@ controller, which are in turn actualized as desktop notifications by the
 TODO
 ----
 
+- formalize message format and protocol
 - tests (design is starting to take shape, so it is time)
 - show how many Debian package updates are available
 - show how many Debian package security-updates are available
@@ -184,10 +185,30 @@ TODO
     - snooze time (if already alerted, when to re-alert?)
     - text: subject/body
 - monitor processes
+    - totals (grand and per state)
     - zombies
+    - threads
     - CPU hogs
     - memory hogs
     - memory leaks (if some process consistently grows)
+    - is select process up?
+    - log resource usage of select processes
+- monitor arbitrary HTTP endpoint availability
+    - is status within expected range?
+    - response time
+        - is responce time within acceptable range?
+- report detailed status upon request (to a terminal)
+    - use color to indicate age of data
+- monitor logins
+    - totals (per time period)
+        - failures
+        - successes
+    - most recent
+        - success
+        - failure
+- monitor battery time remaining
+    - monitor accuracy (is percentage change rate on track to meet estimate?)
+    - adjust estimate based on observed inaccuracies in past estimates (Kalman?)
 
 Redesign notes
 --------------
@@ -207,12 +228,34 @@ Redesign notes
 Ideas
 -----
 
+- track devices:
+    - alert when never before seen device is plugged-in
+    - report history and trends on when and how-often each
+      device/category is plugged-in, how-long it stays plaugged-in, etc.
+- daemonize `khatus`, so we don't have to re-launch `X11` to re-launch `khatus`
+- interoperate with other khatus instances
+    - prefix machine ID to each data source
+      (What should that ID be? Hostname? Pub key?)
+    - fetch remote data and process locally
+    - what transport to use?
+        - ssh + rsync + cache dumps per some interval?
+    - `A` can setup self penetration testing, by setting up probe of `A` on `B`
+      and fetching results from `B` to `A`
+- offline mode - quick disable all network-using subsystems (sensors, monitors, etc)
+- classify each sensor as either "local" or "remote" (what about `iwconfig`, et al?)
 - store data with rrdtool
-- report detailed status upon request (to a terminal)
-    - use color to indicate age of data
+- some kind of personal calendar thing integration
 - monitor tracking numbers (17track should be easiest to get started with)
+- monitor password digests against known leaked password databases
 - monitor stock prices
 - monitor some item price(s) at some store(s) (Amazon, etc.)
+    - https://docs.aws.amazon.com/AWSECommerceService/latest/DG/EX_RetrievingPriceInformation.html
+    - https://docs.aws.amazon.com/AWSECommerceService/latest/DG/ReturningPrices.html
+    - https://developer.amazonservices.com/
+- monitor Amazon order status
+    - https://developer.amazonservices.com/gp/mws/api.html?group=orders&section=orders
+- monitor eBay order status
+    - http://developer.ebay.com/DevZone/XML/docs/Reference/eBay/GetOrders.html
 - monitor eBay auctions (https://en.wikipedia.org/wiki/EBay_API)
 - monitor PayPal (https://www.programmableweb.com/api/paypal)
 - monitor bank account balance and transactions
@@ -264,6 +307,11 @@ Ideas
     - https://nvd.nist.gov/
     - https://vuldb.com/
     - http://cve.mitre.org/
+- vacation planning optimization
+    - I want to visit a set of places within some time period. Given the
+      current set of prices, a set of constraints (I need to stay some amount
+      of days at each, I must be in X at Y date, etc), which visiting dates for
+      each are cheapest?
 - browse https://www.programmableweb.com/ for some more ideas
 - GC trick: instead of actually doing GC, do a dummy run of building a status
   bar at `BEGIN`, to fill-in the atimes for keys we need, then use the atimes