* Firefox Addon: https://addons.mozilla.org/en-US/firefox/addon/disable-slack-wysiwyg/
* Chrome Extn: Pending Review
* Source: https://github.com/pocc/no-wysiwyg
edit: formattingDisable new Slack WYSIWYG editor with this bookmarklet
101–110 of 110 posts
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#102Earlier quoted context omitted.
Some users prefer having a separate app with its own icon and window instead of another tab in a browser. It keeps things Separate
You can do this already for slack in chromium browsers. Click Menu -> More Tools -> Create Shortcut. The app will run in an app window and NOT a tabbed browser window, just like a PWA, with it's own dock icon and cmd-tab icon.
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#103Earlier quoted context omitted.
Slack is extremely hostile towards user feedback. I sent them comments on what I believe to be a terrible feature and they also told me it will never be changed.
"extremely hostile" sounds hyperbolic. Unless you were somehow attacked, threatened, sent a C&D, or had an account disabled, they simply steamrolled over your opinions. And they are far from the first consumer-facing company to deal with user backlash when a new feature came out. Facebook notoriously got an onslaught of negative opinions and sometimes press when a feature in the UI changed. The UI never caused any si…
This is what hostility looks like. They think they know better than their users. They don’t.
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#104Good news, they're backpedaling. Just got this in a support request: >We really appreciate your feedback, and we hear your frustration. We're sorry for the impact this is having on your ability to communicate with your team and on your overall productivity. We made a mistake by forcing everyone into this feature without providing an opt-out for customers like you: people for whom the existing behavior was working jus…
A couple of WEEKS???
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#105Earlier quoted context omitted.
Slack is an enterprise product. You aren't the guy who buys it, so what you think is irrelevant. They don't care anymore, user experience won't affect their bottom line unless it somehow becomes a Powerpoint bullet vs. some other enterprise competitor, which by definition is equally unconcerned about end-user opinions for the same reasons. Atlassian is the same way now, providing any kind of feedback to them is equiv…
> what you think is irrelevant If Slack thinks this, they are only 2-3 years from getting overtaken by a disruptor. I don't think they do. How much sway angry emails have over actual usage is a different question. Facebook notoriously used analytics and A/B tests to decide if feature changes stayed, not angry complaint messages.
There are literally dozens to hundreds of cases that prove otherwise. Look at all the current tech giants...
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#106Earlier quoted context omitted.
You can include native code in Electron apps. I am not sure it is actually needed in any of the messaging Electron apps (Slack, Discord), but the capability is there. My favorite Electron app is Balena Etcher. It is "dd" but uses 200MB of RAM. It is AMAZING.
Hmm, that doesn't seem totally fair - it's 'dd' but with guardrails so that schoolchildren who want to flash raspbian onto an SD card don't accidentally overwrite their boot disk.
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#107Earlier quoted context omitted.
You can include native code in Electron apps. I am not sure it is actually needed in any of the messaging Electron apps (Slack, Discord), but the capability is there. My favorite Electron app is Balena Etcher. It is "dd" but uses 200MB of RAM. It is AMAZING.
Does it actually include any native code, or does it just wrap `dd`? I tried this app and it was beyond awful. I went back to `dd`.
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#108Good news, they're backpedaling. Just got this in a support request: >We really appreciate your feedback, and we hear your frustration. We're sorry for the impact this is having on your ability to communicate with your team and on your overall productivity. We made a mistake by forcing everyone into this feature without providing an opt-out for customers like you: people for whom the existing behavior was working jus…
> we expect to have it available on the desktop within a couple of weeks, A couple of WEEKS???
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#109You can do it in the desktop app as well. If you run it with SLACK_DEVELOPER_MENU=true in env vars, it'll enable you to right click to Inspect Element, open devtools and run this code snippet there
Alternatively, you can run `launchctl setenv SLACK_DEVELOPER_MENU true` and then the dev menu will work if you launch slack from anywhere, and will persist until you log out. If you create the following plist in ~/Library/LaunchAgents, macOS will set that env variable every time you log in (except if you tell it to reopen windows when logging back in). Change "NAME.OF.FILE" to the plist's filename without the .plist…
Re: Disable new Slack WYSIWYG editor with this bookmarklet
#110 We really appreciate your feedback, and we hear your frustration.
We're sorry for the impact this is having on your ability to communicate with your team and on your overall productivity.
We made a mistake by forcing everyone into this feature without providing an opt-out for customers like you: people for whom the existing behavior was working just fine.
We've started working on a preference that will let you return to the previous message composer.
We don't have a specific release date to share right now — it's this team's top and only priority, however, and we expect to have it available on the desktop within a couple of weeks, with Android following shortly thereafter.
We will follow up with another note when this option is available to you, and we'll include instructions on how to enable it.
Again, we're sorry for the disruption and we're grateful for the feedback.
We missed the mark on this feature! We will do our best to learn from this and avoid similar mistakes in the future.