This has been slowing me down immensely. I would have figured an easy workaround would be to copy/paste any fancy markdown stuff I needed to use from my text editor or IDE, but that only results in completely unformatted text. At least slack is good with their /feedback command.
Slack’s new WYSIWYG input box is terrible
661–670 of 1001 posts
Re: Slack’s new WYSIWYG input box is terrible
#662I have contacted them, and they replied me with this Lucas (Slack) Nov 20, 9:15 PM PST Hi there, Thank you for taking the time to write in and provide this feedback. I apologize for the disruption to your existing workflows. Our aim is to build an editor that works for all Slack users to better format their messages and clearly communicate in channels, regardless of their technical expertise. While we are taking all…
Frustrating to get such a definitive “not going to change it” response like that. At least with a company like Google they wouldn’t even bother responding. Why even bother offering to accept feedback if they’re not willing to take it to heart? Maybe it’s just an attempt to placate their users. I don’t see why they would have an issue offering some type of preference setting or inline selection for this. What would be…
Spotify were also definitely not going to bring the Android widget back after removing it. A storm of complaints and cancellations - including mine - later and they changed their minds.
I found other options in the mean time; I didn't resubscribe my 10 year old family sub.
There won't be the same amount of choice re Slack..
Re: Slack’s new WYSIWYG input box is terrible
#663Earlier quoted context omitted.
Exactly. Personally, I recommend switching to Ripcord as a Slack client. That's what I did some time ago, and I couldn't be happier.
Thank you! I didn't know about Ripcord, and so far it is great. I am amazed how fast it is. I'm also depressed that this amazes me, as it basically does what mIRC did for me over a decade ago. This is developed in QT by one person, and it looks pretty feature-complete to me. I really don't understand why a company the size of Slack invests all their development effort into such a subpar platform as Electron, when a n…
I really don't understand why a company the size of Slack invests all their development effort into such a subpar platform as Electron, when a native solution is clearly doable with very limited resources.
Several things I can think of: "quantity is not quality"; JS developers far outnumber everyone; making web apps look exactly the way they want is easy, and they are not interested in platform-native functionality, preferring a "consistent" UI across platforms instead; "premature optimisation" dogma that means no one cares about efficiency anymore.
Microsoft Teams and (later versions of --- they actually moved away from perfectly decent native Win32) Skype also use Electron, and that's Microsoft. That says the size of the company and its resources matters little in things like this.
Re: Slack’s new WYSIWYG input box is terrible
#664I've been suffering from this one too so I'll share the most annoying part for me. I frequently have reasons to type out glob patterns generally in backticks. The interface for this is completely broken in the new WYSIWYG editor. Here's what happens when I try to type: `/ / `, things work normally up until the second " " at which point the "/" between them becomes gets bolded, which makes no sense, because you can't…
Interestingly, I suffered from the exact same asterisk problem last week, but it's now been fixed on my slack!
Good to see that they are shipping improvements to it now.
Re: Slack’s new WYSIWYG input box is terrible
#665Earlier quoted context omitted.
This is another argument against using proprietary SaaS solutions for such crucial purposes as business communication. There are free open source alternatives which give you full control and privacy: Mattermost, Riot.im, Rocket.chat, Let's Chat.
If you mean with "you" the operator of the tool, then yes I agree partially. But in this context it's more like "you" the user and then using open source alternatives doesn't make a big difference. Updates (which you generally want for security/good features/fixes/x) will still break your workflow regularly. It's about how the service handles change (e.g. options to use the old interface etc.) that make the differenc…
Exactly that. There was an interview with Basecamp founder here a few days ago and he highlighted that even now when the current version is Basecamp 3 they still maintain Basecamp 1 for clients who don't want to make the change.
Re: Slack’s new WYSIWYG input box is terrible
#666Specific bug gripes aside: I see this editor as emblematic of Slack's broader shift away from what I think it should be (primarily synchronous chat; irc with a friendlier ui and integrated bouncer features) towards what many people seem to want to use it as (async-heavy pseudo-replacement for email where I get to sit and watch the "...is typing" indicator flicker while somebody writes an essay at me). My rule of thum…
My memory is fuzzy a bit, but I think I saw Slack being called, or even calling itself, the "e-mail killer". This leads me to believe that the hybridization you mention is on purpose, and its goal is to make profit by destroying the only remaining decentralized communication protocol in widespread use.
I'm pretty sure it was discussed as the "email killer" even here on HN, where there is a tech-savvy audience. You know, in one of those recurring waves of comments to the effect of "email is broken" (and its cousin, "it's time to move past textual representations of code"). Thankfully after all this time email is still used by devs and text remains the primary representation of code -- both for good reasons!
Re: Slack’s new WYSIWYG input box is terrible
#667I want to encourage everyone who doesn't like the WYSIWYG input box to use `/feedback` directly from within Slack to let the folks over there know about it. I believe this is one of those occasions in which tons of user feedback is crucial to at least make that awful thing optional.
I am also running this command:
/remind me every day at 10am to remind Slack about the awful WYSIWYG input box
Re: Slack’s new WYSIWYG input box is terrible
#668Earlier quoted context omitted.
Concerning Clubhouse.io, it looks great, is there a download version? I know “Cloud is the way to go”, but I work in Men’s Rights (DV abuses, etc) and it is usually something that cloud companies don’t want on their platform, so we’re constantly at risk of being revoked.
I've just looked at the to 4 sites for mensrights and see hosting on Azure, GCP, Cloudflare and godaddy. Do you have any links to any cloud or other hosting company kicking out any mens rights sites?
The SPLC determined that the most famous of them were “promoting hate”, so PayPal pulled service, and it’s always the roulette on what is going to be pulled next. Each year the International Conference on Men’s Issues had to change venues at least once, and one year the venue pulled out less than a month before the conference.
Don’t say it doesn’t exist. And saying “All men are pigs” is apparently not a reason to pull support from the female equivalent. As much as “Women should be sentenced to smaller prison times than men” is apparently not a hindrance to staying head of the judges of UK’s Supreme Court.
So yeah, we need to avoid using cloud services.
Re: Slack’s new WYSIWYG input box is terrible
#669Earlier quoted context omitted.
Thank you! I didn't know about Ripcord, and so far it is great. I am amazed how fast it is. I'm also depressed that this amazes me, as it basically does what mIRC did for me over a decade ago. This is developed in QT by one person, and it looks pretty feature-complete to me. I really don't understand why a company the size of Slack invests all their development effort into such a subpar platform as Electron, when a n…
> as it basically does what mIRC did for me over a decade ago When Atlassian finally pulled Hipchat last year I was tasked with finding the replacement. Turns out the one that met everybody's needs best was a local IRCd and whatever desktop client for it people liked. Some problems have been solved correctly for a while; chat is one of them.
I'm actually in the process of doing this right now. (Looking for a Slack replacement.)
Which specific daemon did you settle on?
Re: Slack’s new WYSIWYG input box is terrible
#670Earlier quoted context omitted.
If it is the primary method of communicating within your team/company, then you will find it difficult to not use it, or rather you will be left out of major decisions/changes.
You’ve described the pathology and first reason to NOT use chat for anything important. What am I supposed to do? Sit on the chat all day so I don’t miss anything? I’m on a team that does this now. I ignore the 100 to 1000 plus messages and memes a day and I have missed “important decisions”. It’s a net negative imo.
I work on a remote small team, but we work on a highly complex, large code base.
We rarely pick up a phone, and we do not use email. Everything is 100% Slack.
This works well for us. You can bring in only the people you need, you can "star" messages and channels that are important, and none of us have any time to spam/meme the channels, so it's 100% business. We integrate the JIRA slackbot to keep abreast of what is going on in JIRA.
It all "just works" for us.