Live data from Hacker News

Show HN: Use Slack for Everything

operator.im

1–10 of 48 posts

Re: Show HN: Use Slack for Everything

#2
I'm not sure if this service specifically requires full access permissions or not, but I do know a ton of these (awesome/neat) plugins like this popping up require a company to give the plugin full write/read permissions. And for that reason, it's stopped our company from being able to use them.

I'd be curious to see how many companies would actually allow a 3rd party service to have that full amount of permissions. It's sort of like GitHub and how some services require the access to private repos. I'm not sure of a solution, but am just curious how it really holds back awesome services like this when companies don't feel comfortable giving it the level of access it has to have (but may not use that full access).

Re: Show HN: Use Slack for Everything

#3

I'm not sure if this service specifically requires full access permissions or not, but I do know a ton of these (awesome/neat) plugins like this popping up require a company to give the plugin full write/read permissions. And for that reason, it's stopped our company from being able to use them. I'd be curious to see how many companies would actually allow a 3rd party service to have that full amount of permissions.…

Run an IRC server, configure a hubot. Yes, 'cloud'-based chat is pretty, but it's a new coat of paint over something that's been around for decades (IRC). For a company less than several thousand people, running your own singleton IRC server is about as complicated as setting up a basic 3-tier web application (i.e., a little fiddly, but not hard at all)

Re: Show HN: Use Slack for Everything

#4

I'm not sure if this service specifically requires full access permissions or not, but I do know a ton of these (awesome/neat) plugins like this popping up require a company to give the plugin full write/read permissions. And for that reason, it's stopped our company from being able to use them. I'd be curious to see how many companies would actually allow a 3rd party service to have that full amount of permissions.…

It's a slash command, should only need a webhook AFAIK.

Re: Show HN: Use Slack for Everything

#7
post #3

I'm not sure if this service specifically requires full access permissions or not, but I do know a ton of these (awesome/neat) plugins like this popping up require a company to give the plugin full write/read permissions. And for that reason, it's stopped our company from being able to use them. I'd be curious to see how many companies would actually allow a 3rd party service to have that full amount of permissions.…

Run an IRC server, configure a hubot. Yes, 'cloud'-based chat is pretty, but it's a new coat of paint over something that's been around for decades (IRC). For a company less than several thousand people, running your own singleton IRC server is about as complicated as setting up a basic 3-tier web application (i.e., a little fiddly, but not hard at all)

Clients on the other hand are somewhat lacking for IRC.

We use Slack in a company of ~30, and while all the devs could easily use IRC, most of the rest of the company would struggle with it, and certainly wouldn't be able to communicate in the wide variety of ways (uploaded files, images/gifs, videos, code snippets, etc) that they do now. Slack is great at making all those rich media types 'just work', and while it was possible with plugins to some IRC clients, the UX was prohibitively bad in my experience.

Re: Show HN: Use Slack for Everything

#8

I'm not sure if this service specifically requires full access permissions or not, but I do know a ton of these (awesome/neat) plugins like this popping up require a company to give the plugin full write/read permissions. And for that reason, it's stopped our company from being able to use them. I'd be curious to see how many companies would actually allow a 3rd party service to have that full amount of permissions.…

Hey there! This is a great point and something we recognized when developing operator. We wanted to make a service that didn't expose your entire chat to a third-party service.

The OAuth scopes operator asks for are the following: chat:write:bot - so we can post to your channel operator's response. commands - to install the commands. users:read - so we can get a bit more information about you (name, team permissions, etc).

We even toyed with the idea of eliminating the "users:read" to be as minimally invasive as possible.

Re: Show HN: Use Slack for Everything

#10
post #3

Earlier quoted context omitted.

Run an IRC server, configure a hubot. Yes, 'cloud'-based chat is pretty, but it's a new coat of paint over something that's been around for decades (IRC). For a company less than several thousand people, running your own singleton IRC server is about as complicated as setting up a basic 3-tier web application (i.e., a little fiddly, but not hard at all)

Clients on the other hand are somewhat lacking for IRC. We use Slack in a company of ~30, and while all the devs could easily use IRC, most of the rest of the company would struggle with it, and certainly wouldn't be able to communicate in the wide variety of ways (uploaded files, images/gifs, videos, code snippets, etc) that they do now. Slack is great at making all those rich media types 'just work', and while it w…

That's a fair criticism. I know https://grove.io/ does great work in making 'real IRC' available to the masses, but it's still hosted. It would be nice if they would release their web-client as open source, or if someone wrote an OSS clone.
Post reply on HN