- corrected install script to fix [14](https://github.com/raspishake/rsudp/issues/14)
- corrected social media URL destination [15](https://github.com/raspishake/rsudp/issues/15)
- adding feature requested in [9](https://github.com/raspishake/rsudp/issues/9) (additional text for twitter posts [documented here](https://raspishake.github.io/rsudp/settings.html#tweets-twitter-notification-module))
- edited language as requested in [13](https://github.com/raspishake/rsudp/issues/13)
- added feature requested in [17](https://github.com/raspishake/rsudp/issues/17) to control forwarding of `ALARM` and `RESET` messages as well as data
- added feature requested in [18](https://github.com/raspishake/rsudp/issues/18) to forward messages to multiple destinations (this changes the syntax of the `"address"` and `"port"` fields of the `"forward"` settings section to lists)
- changed logging structure to be more downstream-friendly. downstream software can now initialize logging to `/tmp/rsudp/XYZ.log` by calling `rsudp.start_logging(logname='XYZ.log')`
- addressed ([23](https://github.com/raspishake/rsudp/issues/23)) which prevented data from being written to the output directory
- added tests for alert, alertsound, consumer, custom, forward, plot, printraw, rsam, producer, packetize, Telegram, Twitter, and write modules as suggested [in review](https://github.com/openjournals/joss-reviews/issues/2565) ([#22](https://github.com/raspishake/rsudp/issues/22))
- added `.coveragerc` and code coverage basics