load the history on initial load.

inefficiently as well, but we've got no api yet, so it's probably ok.
maybe per-date would be a nice compromise? but that would potentially
mean lots of requests for going back through time, so an api would be
nicer.

it could even work with daily files, reading them into memory (potential
oops) and then serving ranges of dates. hm...

js/babl/index.html

			var messagesEl = document.getElementById("messages");
			var inputEl = document.getElementById("input");
			setTimeout(loadHistory, 0);
			var ws = new WebSocket("ws://localhost:8080");
			inputEl.onkeyup = function(ev) {
				messagesEl.appendChild(msgEl);
			}
			ws.onmessage = function(ev) {
				var msg = JSON.parse(ev.data);
			function handleMessage(msg) {
				switch (msg.type) {
					case "message":
						displayMessage(msg);
				}
			}
			ws.onmessage = function(ev) {
				var msg = JSON.parse(ev.data);
				handleMessage(msg);
			}
			function sendMessage(msg) {
				var msg = {
					type: "message",
				console.log("sending: ", msg);
				ws.send(JSON.stringify(msg));
			}
			function loadHistory() {
				var xhr = new XMLHttpRequest();
				xhr.open('GET', location.href + "/../msgs.json");
				xhr.onreadystatechange = function() {
					if (xhr.readyState == XMLHttpRequest.DONE) {
						var msgs = JSON.parse(xhr.responseText);
						msgs.forEach(function(msg) {
							handleMessage(msg);
						});
					}
				}
				xhr.send();
			}
		</script>
	</body>
</html>