Implement basic IO for the application

[stuf]

There might be some alternatives on how to cleanly manage application IO. Some uses for a nicer managed IO scheme includes taking a screenshot, import and export of data and desktop notifications, are first that come to mind.

Some interesting alternatives for this:

• IO typeclass in flow-static-land
• Alternatively, ramda-fantasy's IO based on the Fantasy Land spec

Do some testing with these and see how things could work out. At least based on some looking around, thestatic-land implementation offered in flow-static-land seems like it could be a good pick, as parts of Calmm as well as Kefir supports static-land algebraic types, as well as the added benefit of static type checking with Flow.

[stuf]

For self-note, the chainability of FL-compatible libraries might seem like a good idea at first. Currently sanctuary is used out of curiosity for handling incoming data in network.js. This was actually written while on a HEL-OSL flight, which I decided to take into use.

In retrospect this part doesn't sit well in with the rest of the module, so optionally this could be rewritten with flow-static-land to ensure more consistent handling of borderline cases with API data. This mainly concerns the step between having received the data from the API and when parsing the data into use for the appropriate handlers.

I'll make a separate issue for this, since the way network data is handled currently (collecting the entire request to have all the relevant data for each request; rather, separate the request and response handlers to their own parts to do their respective part of the work.