811–820 of 1001 posts
What the F? I use it as normal I mean I use the ``` symbols as I'm used to without issues? Am I missing something ?
Did Slack ship a buggier version of this yesterday? I have it on one of my workspaces, and it's fine . I can still type `backticks` in the editor, with the exact same combinations of keystrokes I used before, it's just that they render as they will on the channel, rather than showing me the backticks (and only when I type the closing backtick. GIF here: https://i.imgur.com/o3wPWN0.gif ) Triple backtick does the same,…
It may have been buggier yesterday, but I had the change applied to my desktop client today and it is still buggy. Try to edit an `inline code` section. Or enter two code blocks back to back. Or paste in anything with formatting, especially if there is a code block at the end.
This is not one of those "oh, that's annoying, i'll have to remember that and learn to work around it" issues. It's more like "I want to immediately stop using this software but have no choice". Its driving me crazy - Slack is all text input. Don't break text input dummy!
I feel like this is the way of things with Slack: poorly implemented new features are introduced with no way to disable them, and a significant portion of their users end up needing to work around them. I'd love to have time to research replacements for my employer's use of Slack because they clearly care more about being "innovative" than meeting the needs of their existing userbase. Other examples: * The UX around…
``` blocks are such a pain in the ass to edit now. Say you have ```aaa bbb``` and you decide you actually want... ```aaa``` ```bbb``` You get stuck in the stupid codeblock editor, to actually leave it, you need to insert newlines and extra ``` until it splits AND YOU END UP WITH MORE ```. Slack...please fix this garbo
Earlier quoted context omitted.
I expressed my discontent to them as well and just received this reply: "I'm afraid there is no way to disable this at the moment, and it's not in the roadmap to roll back on this feature. That said, we're still in the initial stages here, so our focus right now is listening to feedback as we consider certain changes for improvement as we move forward. You've raised some fair points here, so I've shared your feedback…
So their rollout methodology here was to go live with beta software, on production servers, to paying customers, and force them to find the bugs. Brilliant!
This is funny because I work across the street of Slack’s office in Vancouver, Canada and two Slack engineers who I frequently chat with during our daily commute already told me they —and a handful of other employees— hate the WYSIWYG input box too, but were afraid to express their feelings because their role is irrelevant compared to the people who made the decision to ship it.
For the life of me, I cannot figure out how to create two adjacent but separate code blocks. ``` one ``` ``` two ``` I've tried and tried.
Did Slack ship a buggier version of this yesterday? I have it on one of my workspaces, and it's fine . I can still type `backticks` in the editor, with the exact same combinations of keystrokes I used before, it's just that they render as they will on the channel, rather than showing me the backticks (and only when I type the closing backtick. GIF here: https://i.imgur.com/o3wPWN0.gif ) Triple backtick does the same,…
Earlier quoted context omitted.
I feel like this is the way of things with Slack: poorly implemented new features are introduced with no way to disable them, and a significant portion of their users end up needing to work around them. I'd love to have time to research replacements for my employer's use of Slack because they clearly care more about being "innovative" than meeting the needs of their existing userbase. Other examples: * The UX around…
What don't you like about threads? I think they're actually my favorite Slack feature. I find myself missing them in more casual chat apps like Discord.
Earlier quoted context omitted.
Why does everything need to cater to idiots instead of making them learn? If we continue down this trend we’ll end up with keyboards with a single button to cater to some monkeys out there who can’t manage to use a proper keyboard, at the expense of everyone else’s productivity. Is this the future we really want?
Because they’re not idiots but rather people with different priorities and backgrounds who were underserved previously. You might disagree that this is helpful but it’s unlikely that you know more about Slack’s users than their UX team. Treating everyone involved with respect is a much better strategy than what you’re doing.
They're not treating the users who prefer markdown formatting with respect at all. It's basically: "fuck those guys, we want to cater to a different audience".