Hacker News Reader

Comment by Twirrim | Hacker News Reader

Why.... why would you want to pipe output from your terminal to a third party service like slack to store and analyse at will?

Who gives a shit about security, let's throw everything at Slack, because Slack!

Ya! I mean, when would it ever be useful to share a log file from your server with your team?

Because nothing confidential ever appears in logs, right?

because

A: "I'm haaving a problem with blah. It says Y is misconfigured" B: "send me the output of Y-configurator --display"

is way easier when you don't have to dump the output into text and email it (or trash formatting with copy and paste)

Is that significantly simpler than having them capture the output, and then make a Slack snippet?

  # on mac:
  Y-configurator --display | pbcopy
  # or on linux:
  Y-configurator | xclip -sel clip

I mean, it's two steps instead of Slackcat's one step, but seems to require less configuration on their end.

Edit: Fellow devs seem to confirm that this is my misconception, and that slackcat pretty much rocks. :D