Live data from Hacker News

Slack’s new WYSIWYG input box is terrible

quuxplusone.github.io

141–150 of 1001 posts

Re: Slack’s new WYSIWYG input box is terrible

#141
post #64
post #3

I've given up entirely on the Slack desktop app and use Ripcord exclusively. Much faster, more responsive and easier to use for 99% of my time spent on slack.

So Ripcord is making money on illegal thing? Discord / Slack ToS forbids third party app afaik. Edit: Why am I being downvoted? https://old.reddit.com/r/discordapp/comments/8tukek/ripcord_...

From the official Slack API docs site,

https://api.slack.com/community

we find

"terminal-slack - Terminal client for Slack"

"Slacker - Simple Slack client for the CLI"

"scudcloud - Ubuntu client for Slack"

I'm pretty sure there are others in that list which are also standalone thirdparty clients, but clearly they would not be listing those on their own site and providing plenty of API docs if they forbid them.

Re: Slack’s new WYSIWYG input box is terrible

#143
post #3

I've given up entirely on the Slack desktop app and use Ripcord exclusively. Much faster, more responsive and easier to use for 99% of my time spent on slack.

Sadly they aren't going to implement some of my most used features from slack in ripcord so I stopped using it. Was ready to pay a ton of money to the dev as well.

Re: Slack’s new WYSIWYG input box is terrible

#145

It's something so simple that they made complex. It's not just code formatting, even things like italics are annoying to escape from if you're used to the old interface. Also, I totally understand their desire to get rid of the subdomain aspect of slack. As a developer I get it, I really do, but now there is no way to easily go in the browser to the slack that you want. It used to autocomplete now I have to figure ou…

wait what is happening to the subdomain?

Re: Slack’s new WYSIWYG input box is terrible

#146
post #48

You can submit feedback to Slack using "/feedback" command. The nice thing it appears they have real people give you real replies. I encourage people to use it. I asked them for the option to turn it off. An excerpt from their response. > ... we understand that this has caused a disruption in workflows for some of our more technical users. While we don't have any active plans to make this configurable at the moment,…

This is https://slackhq.com/new-slack-features-invites-message-forma... right? Isn’t there an option to turn this off with the show formatting button?

edit: oh nm i only noticed the ui, not that it totally broke typing

Re: Slack’s new WYSIWYG input box is terrible

#147
post #114

The exact same happened with the draft feature. The importance of habit forming UI is very well documented, going back at least as far as Jef Raskin's The Humane Interface and the draft feature completely breaks it -- if you as much as accidentally leave a character in there, you can't find the channel/DM at its normal place. Despite repeated calls to make it optional, nothing. Threads are also broken, has always bee…

I've had these exact same problems with Slack and every application that evolves and makes decisions for you. Usually they have the right idea, but sometimes they take decisions way too far and don't let us as users decide for ourselves.

I understand the concept of continual updates but these are some breaking changes and it scares me that they just show up overnight with no warning.

Re: Slack’s new WYSIWYG input box is terrible

#148
Slack's everything is terrible.

At MongoDB, we were supposed to be on it at all times. It was a continuous source of stress and broken concentration. It is what I left behind most eagerly.

Curiously, Google Chat has not become similarly stress-inducing. Yet. Gmail has become moreso lately, though. At least once a week it manages to conceal an important message.

Since Google Chat works, I expect them to drop it soon.

Re: Slack’s new WYSIWYG input box is terrible

#150
post #18

I get that it's bad right now, but it hasn't even rolled out fully. It's quite clearly not 100% done or it would be 100% rolled out. This seems like literally one bug.

So if only 50% of the users have this, we should assume that it's only 50% done, and that by the time everyone has this thing, it will be perfect? More seriously, while "this doesn't work right" is part of the complaint, the larger complaint is "this is fixing something that wasn't really broken." If Slack wanted to improve their editor, that'd be great, but they could have done that without losing what people liked…

[deleted]
Post reply on HN