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

Slack’s new WYSIWYG input box is terrible

quuxplusone.github.io

Post reply on HN
Print view View original

371–380 of 1001 posts

Re: Slack’s new WYSIWYG input box is terrible

#371

Post by xfitm3 »

dfsegoat wrote: post #301
xfitm3 wrote: post #210

Fuck slack. They're hostile to user choice and preferences, pushing a one-size-fits all attitude. Communication preferences are extremely personal and must be respected. I have a custom ssl proxy to intercept slack.com and modify their api, eliminating what I believe to be dark patterns. Some things I do: * Force dark mode always * Disable favicon.ico updating when there are notifications in DnD * Group channels base…

I’m just curious about the ssl proxy + api modification part in general - got a ref for that for a more mundane application?

I'm using something I wrote for work. Basic steps:

- Create and trust a CA

- Issue SSL for api.slack.com

- Deploy something like https://github.com/chimurai/http-proxy-middleware/issues/97 with your code to modify the response body

- Strip HPKP headers, if present

- Strip CAA in DNS, if present

Re: Slack’s new WYSIWYG input box is terrible

#374

Post by ss3000 »

Arathorn wrote: post #35

Amusingly, for https://riot.im we just shelved our WYSIWYG editor efforts after trying two completely separate implementations over the years (one via Draft.js, the other via Slate.js) because: a) it's a nightmare to get right, b) nobody used it anyway (it was optional), c) chat isn't a wordprocessor, d) markdown (commonmark) + floating formatting toolbar is good enough. Our current editor was written from scratch (c…

Curious if you've explored something based on ProseMirror?

I've heard good things about it and it seems to have a decent implementation for hybrid WYSIWYG + Markdown.

https://prosemirror.net/examples/markdown/

Re: Slack’s new WYSIWYG input box is terrible

#375

Post by nirvdrum »

vailripper wrote: post #99
nerdponx wrote: post #69

Earlier quoted context omitted.

You know what else has a terrible WYSIWYG editor? Microsoft Teams. It's kind of sort of like Markdown, except when it isn't, or when it breaks. At least it's a step up from Lync.

Sounds like Atlassians approach with Jira - "it supports markdown, except when it doesn't!"

Doesn’t Jira use textile? Or has that changed?

Re: Slack’s new WYSIWYG input box is terrible

#376

Post by sebazzz »

thelittleone wrote: post #335
rbavocadotree wrote: post #314

Earlier quoted context omitted.

65 of the fortune 100 companies use slack.

I’m always a little wary about these claims. For example I worked at a Fortune 500 before and I created a setup on an app like Slack using my corporate email account. There is a big difference between “used by company Y” and “used by tiny team X inside company Y” (probably without IT approval).

True, my team happens to be slack but the company actually employs Teams as a chat solution.

Re: Slack’s new WYSIWYG input box is terrible

#377

Post by Bananaman28 »

vailripper wrote: post #99
nerdponx wrote: post #69

Earlier quoted context omitted.

You know what else has a terrible WYSIWYG editor? Microsoft Teams. It's kind of sort of like Markdown, except when it isn't, or when it breaks. At least it's a step up from Lync.

Sounds like Atlassians approach with Jira - "it supports markdown, except when it doesn't!"

This is my experience as well. Moving over to their new editor has left the markdown support in limbo between different views. I.e it varies between the view when creating an issue, editing an issue and commenting on an issue.. It's really infuriating. I asked them about it on Twitter and it's apparently a work in progress?

Re: Slack’s new WYSIWYG input box is terrible

#378

Post by igetspam »

function_seven wrote: post #285
tbabb wrote: post #111

This reminds me of Atlassian's god-awful WYSIWYG editor. In both cases, I get that some users can't or don't like to use a machine grammar/markup, however simple. For some people markup is bad UX. Give them a WYSIWYG; that's fine. But don't remove the markup editor if your WYSIWYG editor is anything but a perfect one-two-one replacement for markup (and I have never seen one that satisfies that). IIRC there was a time…

Same here. I had to resort to making all edits in my browser's devtools instead. If a page in our Confluence wiki looks decent, there's a good chance it's because I hand-edited the underlying HTML. (There's also a good chance it's old, because I've largely given up on using Confluence for new articles. I just email distro lists like it's 2001)

When I had to use confluence, I did all my editing in gists and copied the rendered version into confluence. I've done that with jira too but the copy/paste seems to get mangled.

Re: Slack’s new WYSIWYG input box is terrible

#379

Post by labster »

arkh wrote: post #369
vailripper wrote: post #99

Earlier quoted context omitted.

Sounds like Atlassians approach with Jira - "it supports markdown, except when it doesn't!"

> it supports markdown, except when it doesn't! So, markdown? Every website has its own flavor of it. Just reading some of the answers around here you can read "to do markdown better we made our own markdown". Maybe because it is shitty. Just let users use HTML.

Great idea!

Re: Slack’s new WYSIWYG input box is terrible

#380

Post by _wolfie_ »

kelseydh wrote: post #360
danShumway wrote: post #139

Earlier quoted context omitted.

> The goal is for workflows to evolve This exchange is a pretty good summation of one of the biggest purely practical reasons why I'm so obsessive about tools, and why I'm so willing to put up with the initial cost of learning systems like Linux and Vim/Emacs. Outside of fundamentally better workflow improvements, most professional fields don't randomly change their tools. If you gave a professional artist a new penc…

If we embraced this philosophy none of us would be typing quickly on touch screen phones. Steve Jobs knew it beat a physical keyboard, and when pressed by people who complained about the new iPhone's touchscreen keyboard, he grinned and said "You'll get used to it." And oh boy, did they ever.

And I still didn't, keep using physical keyboard and believe it's superior. Luckilly there still are phones with full-qwerty keyboards out there.
Post reply on HN