Slack’s new WYSIWYG input box is terrible

Re:Slack’s new WYSIWYG input box is terrible by bandrami on Thursday November 21, 2019 @09:54AM (#21594576)

> It does not have well-functioning and reliable file transfers.

If only there were some sort of Universal scheme for denoting the Location of a Resource. That would let you map a relatively short string to one of many possible file access services, and put that string in a text chat channel, rather than conflating two distinct problem domains.

Also every server I know and most clients do logging.

[ Parent | on HN ]

Re:Slack’s new WYSIWYG input box is terrible by DagAgren on Thursday November 21, 2019 @09:54AM (#21594592)

I am well aware of how to do this, yes. I do not find this a good solution.

So dial back the snark.

[ Parent | on HN ]

Re:Slack’s new WYSIWYG input box is terrible by bandrami on Thursday November 21, 2019 @10:00AM (#21594685)

I concede the snark and withdraw it, but my point remains: one tool for one job. There are tools for sharing files, and URLs allow those files' locations to be shared over text channels. One tool for one job.

[ Parent | on HN ]

Re:Slack’s new WYSIWYG input box is terrible by DagAgren on Thursday November 21, 2019 @10:21AM (#21594926)

That is a tool that takes something like 10x the effort of having built-in file transfers. It is just not a good solution.

[ Parent | on HN ]