Update on Muninn
Sep. 8th, 2014 04:24 pmIt worked! First production run this AM, and a recipient confirmed receipt.
As of right now, where I am:
The reminder system is operational and apparently working correctly (SMS only, command line/batch file/cron interface, on mixo in ~/forge).
The receipt of incoming SMS system is also working correctly (on muninn.sb/~$num) and mostly properly secured (SSL + HTTP Basic Auth), though the interface is v. crude and non-scalable. The "reply" function not yet implemented.
So things that need happening:
- ssh access to sb (where are we with this? I connected support about the key generation bug.)
- implementing the authorization check specified by Tilio on the security page
- make the reply function work
- decide what if any forwarding is desirable, and implement
- scalability of web interface: paging, other
- populate contacts
- build interface for populating/editing contacts
- make pretty (CSS)
Things that might be nice:
- multiuser? installer?
- template for schedule?
- remind self to make schedule?? :)
- swap to HTTP Digest Auth?
- web interface for scheduler?
- web interface for subscriptions?
- system for non-batch or exception reminders? ("and bring the book.")
- voice!
- refactoring
Self, good job at identifying the minimal adequate functionality and not oversolving!
As of right now, where I am:
The reminder system is operational and apparently working correctly (SMS only, command line/batch file/cron interface, on mixo in ~/forge).
The receipt of incoming SMS system is also working correctly (on muninn.sb/~$num) and mostly properly secured (SSL + HTTP Basic Auth), though the interface is v. crude and non-scalable. The "reply" function not yet implemented.
So things that need happening:
- ssh access to sb (where are we with this? I connected support about the key generation bug.)
- implementing the authorization check specified by Tilio on the security page
- make the reply function work
- decide what if any forwarding is desirable, and implement
- scalability of web interface: paging, other
- populate contacts
- build interface for populating/editing contacts
- make pretty (CSS)
Things that might be nice:
- multiuser? installer?
- template for schedule?
- remind self to make schedule?? :)
- swap to HTTP Digest Auth?
- web interface for scheduler?
- web interface for subscriptions?
- system for non-batch or exception reminders? ("and bring the book.")
- voice!
- refactoring
Self, good job at identifying the minimal adequate functionality and not oversolving!