3 ms·

Slack Introduces New Platform with Help from Deno

60 points by 0xedb 5y ago

slownews45 5y ago
This I think is third revision of API for slack? That said - I really like the idea of a relatively straightforward way to wire up actions. I'd especially love to be able to get into and out of a database. I starred another project - retool as well with an eye towards those quick crud apps that used to be basic WinForms + database server for windows users.
dangoor 5y ago
FWIW, Slack's page about this is a lot more interesting: https://api.slack.com/future https://api.slack.com/future
syspec 5y ago
Where might I find a code sample? I clicked through several pages, but could not find it.
_hao 5y ago
I really wish I could use only e-mail instead of Slack/Teams for anything related to my day-to-day job. Both can stay for calls and ceremonies, but that's it. No messaging, no million other sub-applications in Slack/Teams that connect and integrate to everything. I find the whole thing truly tiresome to use.
- tatersolid 5y ago
  I wish for the exact opposite. Email is a disaster because it is permission-less. With a 25 year old email address the spam gets through even Google Microsoft or barracudas filters. Not to mention phishing being the #1 source of all data breaches. Email also suffers from terrible UX, inconsistent threading, reply-all storms, top-posting, malware… Closed system messengers are better than email for work in nearly every way. My company has basically stopped using email for anything internal in favor of chat channels.
BoorishBears 5y ago
But can we add emojis with user auth tokens?
Croftengea 5y ago
This is probably the worst announcement from a big company I ever saw. No word about use cases or advantages. It’s not even clear what is a platform for Slack.
- e12e 5y ago
  "We work with BigCorp. Invest in our upcoming series B"?
orf 5y ago
I built a slack app today and it was a lot harder than it should have been. Event payloads are really inconsistent (one even is a JSON object encoded in a form data field), data about users is inconveniently hidden, and building a functional home tab with navigation is just annoying. This looks like it might solve some of that. The deployment side of things looks awesome, and the typescript types will really help with the inconsistent event structures. However I’m not sure if they are not cutting out a huge part of their target audience with their approach to hosting. How would I connect to an internal service or database with this? I can’t, which makes it super inconvenient for “quick company specific workflows”, which seems to be exactly what they are targeting. That being said, I love the idea of Slack becoming a GUI for an event bus connecting various things together. URL should also be changed to https://api.slack.com/future https://api.slack.com/future
wizwit999 5y ago
Most useless rewrite in rust project ever.

60 points by 0xedb 5y ago

This I think is third revision of API for slack? That said - I really like the idea of a relatively straightforward way to wire up actions. I'd especially love to be able to get into and out of a database. I starred another project - retool as well with an eye towards those quick crud apps that used to be basic WinForms + database server for windows users.

dangoor 5y ago

FWIW, Slack's page about this is a lot more interesting: https://api.slack.com/future https://api.slack.com/future

syspec 5y ago

Where might I find a code sample? I clicked through several pages, but could not find it.

_hao 5y ago

I really wish I could use only e-mail instead of Slack/Teams for anything related to my day-to-day job. Both can stay for calls and ceremonies, but that's it. No messaging, no million other sub-applications in Slack/Teams that connect and integrate to everything. I find the whole thing truly tiresome to use.

tatersolid 5y ago
I wish for the exact opposite. Email is a disaster because it is permission-less. With a 25 year old email address the spam gets through even Google Microsoft or barracudas filters. Not to mention phishing being the #1 source of all data breaches. Email also suffers from terrible UX, inconsistent threading, reply-all storms, top-posting, malware… Closed system messengers are better than email for work in nearly every way. My company has basically stopped using email for anything internal in favor of chat channels.

BoorishBears 5y ago

But can we add emojis with user auth tokens?

Croftengea 5y ago

This is probably the worst announcement from a big company I ever saw. No word about use cases or advantages. It’s not even clear what is a platform for Slack.

e12e 5y ago
"We work with BigCorp. Invest in our upcoming series B"?

orf 5y ago

I built a slack app today and it was a lot harder than it should have been. Event payloads are really inconsistent (one even is a JSON object encoded in a form data field), data about users is inconveniently hidden, and building a functional home tab with navigation is just annoying. This looks like it might solve some of that. The deployment side of things looks awesome, and the typescript types will really help with the inconsistent event structures. However I’m not sure if they are not cutting out a huge part of their target audience with their approach to hosting. How would I connect to an internal service or database with this? I can’t, which makes it super inconvenient for “quick company specific workflows”, which seems to be exactly what they are targeting. That being said, I love the idea of Slack becoming a GUI for an event bus connecting various things together. URL should also be changed to https://api.slack.com/future https://api.slack.com/future

wizwit999 5y ago

Most useless rewrite in rust project ever.