Skip to content

Commit 6af11c1

Browse files
author
Jonathan King
committed
Add last pictures
1 parent 6380178 commit 6af11c1

File tree

4 files changed

+10
-10
lines changed

4 files changed

+10
-10
lines changed

_posts/2015-12-08-christmas-slack-o-meter.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -40,30 +40,30 @@ One of the topics for this Hackathon was Christmas, so we chose a simple Hack th
4040

4141
Obviously we were going to make something huge, loud and fantastically ambitious. We wanted a massive sign with flashing lights, sound, and a HTML front-end displayed on the big monitor in the corner of our office. This would sound a klaxon and go crazy every time a certain keyword was mentioned on one of the public channels on Slack. Since the Hackathon's topic was Christmas, our keywords would be christmassy things like 'turkey', 'sleigh bells', or 'over-commercialised'. We We lost no time in making a big mess and covering our desks in wires, arduinos, raspberry pis and coffee.
4242

43-
![Clorama Hacking on the Hardware](/img/posts/2015-12-08-christmas-slack-o-meter/making-a-mess.jpg)
43+
![George Hiding His Face](/img/posts/2015-12-08-christmas-slack-o-meter/george-hiding.jpg)
4444

45-
The team consisted of Aisling, fashioning the front-end, Clorama, hacking on the hardware and me bashing away at the backend. In no time we had our own mini-PRISM, our very own internal GCHQ snooping on every message in our public Slack channels. By using Slack's [outgoing webhooks](https://api.slack.com/outgoing-webhooks) we could POST every message to our own servers and analyse the text to find incidences of our trigger keywords.
45+
The team consisted of Aisling, fashioning the front-end, Clorama, hacking on the hardware and me bashing away at the backend. In no time we had our very own internal GCHQ snooping on every message in our public Slack channels. By using Slack's [outgoing webhooks](https://api.slack.com/outgoing-webhooks) we could POST every message to our own servers and analyse the text to find incidences of our trigger keywords.
4646

47-
I used [Hapi](hapijs.com), a rich API framework that we've used for Hacks before. I wanted to use this Hackathon to familiarise myself with its structure, and I found it great - a quickly assembled springboard to launch our application from. For persistence we used [MongoDB](https://www.mongodb.org/) and to simplify DB connections and schema we used [Mongoose](http://mongoosejs.com/), both of which play nicely with Hapi.
47+
![API diagram](/img/posts/2015-12-08-christmas-slack-o-meter/cristmas-meter-diagram.png)
4848

49-
![George Hiding His Face](/img/posts/2015-12-08-christmas-slack-o-meter/george-hiding.jpg)
49+
For the API I used [Hapi](hapijs.com), a rich API framework that we've used for Hacks before. I wanted to use this Hackathon to familiarise myself with its structure, and I found it great - a quickly assembled springboard to launch our application from. For persistence we used [MongoDB](https://www.mongodb.org/) and to simplify DB connections and schema we used [Mongoose](http://mongoosejs.com/), both of which play nicely with Hapi.
5050

51-
But the hardware was still giving us a headache. After much deliberating and some eating of humble Pi we decided to scale back our ambitions and instead focus on the Live Demo we would have to give in what suddenly seemed like very little time.
51+
But the hardware was still giving us a headache. After much deliberating and some eating of humble Pi we decided to scale back our ambitions and instead focus on the Live Demo, since 5pm had somehow leapt on us out of nowhere, like an Australian dropbear.
52+
53+
![Drop Bear](http://ftg.operationsupplydrop.org/wp-content/uploads/2015/04/drop-bear-image.jpg)
5254

5355
### The Second Idea
5456

5557
We decided to make something interactive, a simple challenge that we could issue during the Live Demo. Our front-end would be a huge gauge that would constantly poll our API for the current number of triggered keywords and display it using a big, red, jolly needle. Ho ho ho. We would then challenge our audience to send the needle flying with a deluge of Christmas excitement. The first person to send the needle over edge of the gauge would be declared the winner, preferably amid explosions and baubles.
5658

57-
Now with a suitably re-scoped idea, we set to work on the front-end. We made a simple script that would poll our API and translate that into a `transform: rotate(x)` css declaration for the needle.
58-
59-
![Pic of front-end](jgnnksdnjsdkng)
59+
Now with a suitably re-scoped idea, we set to work on the front-end. We made a simple script that would poll our API and translate our Christmas metric into a `transform: rotate(x)` css declaration for the needle.
6060

6161
With a bit of frantic typing right up until the last moment, we managed to do it. And here's a screencapture of the amazing, exhilirating moment when we declared the winner.
6262

63-
![Gif of explosion](jgnnksdnjsdkng)
63+
![Gif of Hack ending](/img/posts/2015-12-08-christmas-slack-o-meter/christmas-hack.gif)
6464

6565
### In Summary
6666

67-
It was a great Hackathon, and we learnt a lot about some technologies we'd never even touched before. Although the end result was a bit naff, and there's a low probability that our invention will actually save mankind, we did manage demonstrably measurable amounts of good cheer.
67+
It was a great Hackathon, and we learnt a lot about some technologies we'd never even touched before. Although the end result was a bit naff, and there's a fairly low probability that our invention will actually save mankind, we did manage demonstrably measurable amounts of good cheer.
6868

6969

img/posts/.DS_Store

6 KB
Binary file not shown.
1.62 MB
Loading
18.1 KB
Loading

0 commit comments

Comments
 (0)