Remote-control your Slack bots with JSON | Hacker News Reader

Remote-control your Slack bots with JSON

blog.jasonette.com

Update: This is not from 2016, but actually a Fresh New post I published this morning (in 2017!) but messed up the timestamp with jekyll, sorry for the confusion!

Hi guys, I wrote the post, but the creator is @smcavinney1 on this thread, please ask him any questions :)

I personally thought this was really cool because it's a Slack bot that actually does something useful, and am super glad Jasonette enables cool projects like these.

p.s. Could someone with the permission update the title so it doesn't say 2016?

Thanks for posting this Ethan. Jasonette made creating this app a breeze for a 'non-dev' like myself.

Using a mobile app to control a chat bot is less elegant than using chat to control a chat bot. I don't get it... isn't it just a mobile app with a chat integration at that point? Or does it not even matter?

I don't think there's any "chat" involved in the slack bot mentioned in the post

Thanks for the question about this. For some context we drink a lot of coffee at my office. We have two pots (bold & light roasts). People never know when coffee is ready or brewing without going to the kitchen. We have a #coffee channel so people can post that they are brewing, but then we had issues with people stealing cups before the pot was done (don't do this). So this app gives an interface for people to just click their face and the bot will handle it from there. It says that a pot is brewing, and 12 minutes later will post that the pot is ready.

To your point, it is just a mobile app with a slack integration. I built it to test out jasonette, which was a great experience, but I have no delusions of grandeur here.

> we had issues with people stealing cups before the pot was done (don't do this).

That's some amazingly annoying and inconsiderate behavior. We had the same problem at one place where I worked, so when the coffee pot was low I had to not only make a fresh pot, but then stand watch over it while it was brewing.

I think it was more about ignorance about how it affects the flavor of the brew. People are generally good about making a new pot after they kill it.

I'm confused. In this context, what is "stealing a cup", and how does that "affect the flavor of the brew"?

With coffee, what is extracted first tastes different from what you extract at the end.

There are different compounds extracted at different times.

In espresso, a ristretto shot is a espresso that's been pulled short. Meaning that it has the same volume of coffee but less water. Around half the water.

Ristretto shots tend to be less bitter and bolder. It's more concentrated.

Finally a bot that actually does something useful, instead of just another assistant bot that everyone's making

Thanks Ethan! Would you mind updating the post with more instructions on using heroku or a way to host the json? I was trying to dump the generated json into S3 and point jasonette to the URL, but that doesn't work because the submit action still points to localhost. Any thoughts?

Hey thanks for the question. I think, just for trying it out you don't even need heroku, you should be able to run it from localhost.

BTW the original author of the app is @shaunymca, so I think he'll be able to help you better than me :)

Maybe try asking on https://github.com/shaunymca/coffeeapp/issues ?

Thanks!

Hi, app author here. When I wrote the readme I wasn't expecting anyone to think about it outside of my company. You can host this on Heroku, that's what I'm doing. Just make sure to add the environment files in the settings. Then you can either build the a jasnonette app or use the relevant Jason apps and point the url to <your-heroku-url>/jsonette.json

Why "in 12 minutes"?

That's roughly the amount of time it takes for our coffee pot to brew 12 cups of coffee. So it posts immediately that a pot is brewing to save people a walk to the kitchen, and again when the pot is done.

> Update: As a mistake I timestamped this as 2016, but this post was just freshly published on January 17th of 2017. Sorry for the confusion! :D

Also, does 2016 really need the 2016 qualification?

It appears that HN automatically added the (2016) tag by looking at the permalink, which I mistakenly set as 2016 (still need to get used to 2017!), and that was what I was trying to say, because it looked as though the post was written a year ago.

Sorry for the confusion!

Reply on news.ycombinator.com