Earlier quoted context omitted.
Was super skeptical about all those Jira replacement SaaS’s out there. But Clubhouse is actually pretty good. For people on the fence, give it a try.
I for one am still waiting for usable task management SaaS - one that doesn't limit me to "epic/project/task" split, but instead recognizes that the work is being decomposed recursively , and has dependencies. All I really want is a system that lets me arrange my tasks into a DAG. B is a subtask of A. C and D are subtasks or B. E is a subtask of D. F is a subtask of A, but depends on D being complete. It's simple and…
Slack’s new WYSIWYG input box is terrible
861–870 of 1001 posts
Re: Slack’s new WYSIWYG input box is terrible
#862Earlier quoted context omitted.
There's also wee-slack: https://github.com/wee-slack/wee-slack
Wee-slack was my go-to for the longest time but can no longer use it and it makes me sad... The problem with it now is that they had to migrate off the legacy API tokens. You now need an administrator to authorize wee-slack as an application for your organization. Not all organizations are willing to do this.
Re: Slack’s new WYSIWYG input box is terrible
#863Slack really is just such a frustrating tool to use (or rather be forced to use).
Re: Slack’s new WYSIWYG input box is terrible
#864Re: Slack’s new WYSIWYG input box is terrible
#865Re: Slack’s new WYSIWYG input box is terrible
#866Earlier quoted context omitted.
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.
As a current slack user, could you give a couple examples?
For me it was the video chat and voice chat though it seems he changed his tune on voice, as the last time I checked it was a 'Never'.
Re: Slack’s new WYSIWYG input box is terrible
#867Re: Slack’s new WYSIWYG input box is terrible
#868Earlier quoted context omitted.
Given that Microsoft Teams is literally an existential threat, they really want to listen to feedback internally!
Microsoft Teams is pretty horrible
At a previous company, we had slack and MS Teams side by side, to trial out MS Teams. Everyone preferred Slack by a huge margin. We were told to get use to Teams, because Teams is free.
Guess what, it was fine.. no notable productivity lose going from slack to teams. If anything, team's sharepoint file integration is much better than slack, for keeping a single source of truth.
Re: Slack’s new WYSIWYG input box is terrible
#869Earlier quoted context omitted.
Not until Microsoft Teams gets the layout fixed, see https://microsoftteams.uservoice.com/forums/555103-public/su...
Thanks for the link. I’ll be watching it. Out of curiosity, what do you think of the Stylish userscript that enables a compact mode in Teams and offers dark and light themes? https://userstyles.org/users/727497
I still prefer an App instead of the browser, but that's just personal preference.
Re: Slack’s new WYSIWYG input box is terrible
#870Alex Oct 31, 2:26 PM PDT
As a software developer I want to be able to use slack to communicate mono-spaced text within messages that I write without having to touch the mouse. The recent addition of dynamic text formatting in slack breaks the preexisting markdown functionality because it is not possible for the rendering engine to guess what my intent might be on the fly.
for example if I type this message:
The uuid portion is `D6B9E544-2306-41E7-9841-FF7E2AE0A5A4`_filename.txt
but then realize that I actually wanted a hyphen instead of an underscore before the word 'filename' there is no way to accomplish this without deleting and retyping "-filename.txt" (or doing a fancy trick where you add "f-filename.txt" and then delete the leading f)
This is not a failing of your system which is quite well implemented, it is simply a matter of WYSIWYG systems not being capable of rendering text with the same precision as markdown systems.
I suggest that you make the WYSIWYG text formatting a toggleable feature for people in the software development community.
---------their very nice but not helpful response-------- Hey Alex,
Thanks for writing in, though I'm sorry to hear WYSIWYG formatting is not working for you and your team as developers. It's not currently possible to turn this off, but I can certainly understand your reasoning here, and will share this feedback with the team so that we can best understand what the right solution is.
Please note, I can't promise that we'll be making this optional anytime soon, but will let the team know why it's not working in your case.
Sorry this isn't the answer you were looking for today Alex, but thanks again for taking the time to share your feedback with us.
All the best,
Susie