Getting started with our beta platform(api.slack.com)
api.slack.com
Getting started with our beta platform
https://api.slack.com/future/get-started
15 comments
We (reclaim.ai) have a fairly advanced Slack integration. Custom actions, modals, Slack status, interactive messages, custom bot home screen, etc.
I truly can’t tell what this is. I also had never heard of Deno before so that context didn’t help.
At first glance it seemed to be a next gen way to build interactive UIs in the Slack app, compared to the callback nature we built our app with.
But digging a bit deeper, it seems to be more narrowly focused on their “workflows” feature, which is one of the few things in their platform we haven’t used.
I’d love to learn more, but also if anyone from Slack is reading: your platform is pretty complex and announcements like this don’t help folks like me.
I truly can’t tell what this is. I also had never heard of Deno before so that context didn’t help.
At first glance it seemed to be a next gen way to build interactive UIs in the Slack app, compared to the callback nature we built our app with.
But digging a bit deeper, it seems to be more narrowly focused on their “workflows” feature, which is one of the few things in their platform we haven’t used.
I’d love to learn more, but also if anyone from Slack is reading: your platform is pretty complex and announcements like this don’t help folks like me.
I wonder why using CLI requires you downloading Deno. Can't Deno compile to static binary?
https://www.infoq.com/news/2021/02/deno-compiles-native-bina...
https://www.infoq.com/news/2021/02/deno-compiles-native-bina...
The CLI generates a project scaffolding for you, which is a Deno project. So I’m not sure the issue is the CLI itself, but the apps you will be building are Deno based.
This doesn’t seem like a CLI/TUI for chatting on slack, but more like a CLI tool for building commands to be used within Slack, like /mycommand, which they call “slack apps”
Thanks. I haven’t been following why there is should be a CLI in slack, or what they’re doing here. And in classic “tech things for tech people” manner, they don’t seem to explain their intent in the post. How, but not why.
Ok. So they want me to be able to write commands that go between slack and my app, and I assume get results back in to slack.
Do I want this?
I don’t have to open a terminal window if I’m already in slack, and I assume the real thing here is I can get complex actions right? IDK, maybe it’s another thing I just don’t get.
Ok. So they want me to be able to write commands that go between slack and my app, and I assume get results back in to slack.
Do I want this?
I don’t have to open a terminal window if I’m already in slack, and I assume the real thing here is I can get complex actions right? IDK, maybe it’s another thing I just don’t get.
I'm currently working on a small Slack app and the experience has been fairly horrendous. The documentation is all over the place. I'm not sure if adding yet another chunk of stuff to it is such a good idea - where does this leave Bolt?
https://slack.dev/bolt-js/
https://slack.dev/bolt-js/
This is the strongest validation signal I've seen for Deno in some time. I had the impression it was withering on the vine, but hopefully this puts some wind in its sails.
On a quick glance, this really caught my eye too. Interesting they chose to go that route. I’ve only been loosely following deno, but this has to be one of the first large companies I’ve seen to use it.
With one hand they give us nice new tools, with the other they're pulling Fedora support.
I'm not very enthusiastic about writing any more integrations or apps.
I'm not very enthusiastic about writing any more integrations or apps.
Fedora supports Chrome.
Slack on Chrome supports notifications, thus slack supports Fedora.
Slack on Chrome supports notifications, thus slack supports Fedora.
> Deno is currently a pre-requisite for using the CLI — if you do not have Deno installed, please do so first.
I'm sorry but that's not what CLI are supposed to be, they should be self-contained with the least amount of dependencies possible and the smallest possible, otherwise it completely defeats the purpose
I'm sorry but that's not what CLI are supposed to be, they should be self-contained with the least amount of dependencies possible and the smallest possible, otherwise it completely defeats the purpose
The CLI itself is self contained binary, and it generates a project scaffold for you which is a Deno project. So you will be developing on Deno, without it obviously you’re not going to be able to do anything.
https://news.ycombinator.com/item?id=29244968