Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The latest version of Slack has a setting to disable the WYSIWYG editor

twitter.com

Post reply on HN
Print view View original

81–90 of 225 posts

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#81

Post by Jamwinner »

danShumway wrote: post #79

This is a good reminder that sometimes complaining about companies on social media like Hackernews and Twitter does actually help. Not always, maybe not even usually. But Slack went from, "no, we have no plans to adjust this", to "yes, we'll include a toggle", and the reason was that a bunch of people publicly complained and wrote a bunch of messages to support. It is a very, very, very small victory, and if I was go…

Isnt that just a silent admission that modern tech support is woefully broken, more than a twitter is good message?

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#82

Post by munk-a »

coryfklein wrote: post #57
saltcured wrote: post #40

Earlier quoted context omitted.

Ha, I wish I could disable "threads" so nobody else can use them...

We have a culturally enforced strict rule of moving literally ALL new conversations into a subthread and I absolutely LOVE it. This means that if you want to respond to a comment, you never do it in the channel but in the subthread of _that_ comment. This means that when you browse the channel itself, each individual line represents a conversation on a specific topic. You can essentially browse the "headlines" of the…

This isn't our standard for all channels, but we do have a channel dedicated to this approach that's meant to contain large direction decisions that are soliciting team opinions. We've also enforced keeping that opening message to a minimum (sort of like a title).

I don't know how I'd feel about all channels being this way (since visibility and notification control are much weaker in this format) but for time limited discussions that may warrant revisiting it's quite helpful.

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#83

Post by munk-a »

nitrogen wrote: post #53
beatgammit wrote: post #44

Earlier quoted context omitted.

I'm glad it's not just me. Threads are terrible and hide potentially important information.

Just to provide a counterpoint, threads are very useful for channels with hundreds of members, so that anyone can ask a question but the responses don't make other questions invisible. In that case, the lack of threads would hide important information.

Is this in the context of a public slack? For our internal slack I'd strongly question why questions needed to be raised in a channel with so many people - at my office we have two channels that most people are in, a #general for company announcement and releases and #random.

Otherwise I think dedicated team interaction channels are the biggest of ours and we try and keep those pretty small still.

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#84

Post by ricefield »

Jamwinner wrote: post #81
danShumway wrote: post #79

This is a good reminder that sometimes complaining about companies on social media like Hackernews and Twitter does actually help. Not always, maybe not even usually. But Slack went from, "no, we have no plans to adjust this", to "yes, we'll include a toggle", and the reason was that a bunch of people publicly complained and wrote a bunch of messages to support. It is a very, very, very small victory, and if I was go…

Isnt that just a silent admission that modern tech support is woefully broken, more than a twitter is good message?

Broken how? This feels like a good example of a company building and launching something, then watching and responding to how the public/users react to it.

Isn't that more or less what you should do as a company? Build things and then adjust your strategy based on how the market likes or dislikes it?

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#85

Post by braythwayt »

BurningFrog wrote: post #63
Someone1234 wrote: post #51

Earlier quoted context omitted.

“There are only two kinds of languages: the ones people complain about and the ones nobody uses.” -- Bjarne Stroustrup I've found this quote extremely true, but not just with programming language but with all things. People complain about Slack because they use Slack a lot, so minor quibbles become a daily frustration. It is when people go quiet about a product that you should really worry. They're either extremely h…

The turning point is when tools go from something enthusiasts choose to being mandated by management.

Digging deeper on your excellent comment, when ai was inEnterprise Sales, we were taught that there were people who made buying decisions, people who influenced buying decisions, and users.

Sometimes users belonged to one of the first two categories, but often not. Companies that pivot from selling to people who use the product to selling to enterprise organizations pivot from building things for users, to building things for decision-makers and decision-influencers.

So it’s not only that management are choosing products for users, but the products themselves evolve to please managers at the expense of users.

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#86

Post by o-__-o »

cygned wrote: post #67
wst_ wrote: post #60

Earlier quoted context omitted.

I'm not really sure I follow. What does the WhatsApp has which is missing in Slack?

You can answer and the original post is shown below your answer. You can do the same with Slack by sharing the post, but other solutions make it way simpler, basically just one click.

this sounds dumb, but it's most likely due to patents [0]. in fact whenever you find really simple behavior missing from an app from a large organization you should first assume IP litigation played a role

[0] https://patents.google.com/patent/US9219704B2/en

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#87

Post by jdnenej »

OJFord wrote: post #39
ceejayoz wrote: post #17

Earlier quoted context omitted.

I'd be 100% fine with drafts if it cloned the channel listing instead of moving it.

I provided that /feedback as soon as it rolled out (to me) I guess 6mo ago. I even got a reply along the lines that it was totally reasonable and eminently sensible, and yet here we are.

I provided feedback to slack once and got a reply similar to that. I wonder if they say that just to make you feel good and then throw the feedback in the bin.

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#89

Post by braythwayt »

qxnqd wrote: post #41
dividedbyzero wrote: post #38

Earlier quoted context omitted.

Ugh no. IRC was great in its day, and I'm sure there are things today that it's still good enough for, but at work, I vastly prefer Slack (and possibly other similar tools, but I haven't power-used any of them yet.) I've been a very, very regular IRC user up until a few years ago. I wouldn't want to go back. With IRC, there is no simple, just-works-for-non-techies way to receive messages if you aren't online; running…

No way to embed things... no emojis... no editing or deleting... seems like you are enumerating the advantages of IRC

Reminds me of trying to explain why Markdown is so good.

Alice: “But why do you use it? It doesn’t do so much!”

Bobbi: “Exactly why I love it.”

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#90

Post by munk-a »

agluszak wrote: post #13

Still waiting for an option to disable "drafts" (channels all of a sudden jumping to the top of the channel list)

I've been loving their responsiveness lately /s. I `ctrl-k` jump to another convo and start typing and the lag between `ctrl-k` closing and switching to the new convo is enough that I end up typing a few characters into the prior conversation - then I need to jump back to clear out the draft.

Their channel listing is generally crap though, I gave up on trying to navigate it and just use `ctrl-k` jumping for everything, which isn't terrible because it means I spend less time on the mouse.

Post reply on HN