911–920 of 1001 posts
Supposedly this feature is being walked back now. I just received the following from their support. I'm ecstatic to hear this and hope their Product Management has reassessed the importance of non-WYSIWYG inputs. >>> 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 mista…
Supposedly this feature is being walked back now. I just received the following from their support. I'm ecstatic to hear this and hope their Product Management has reassessed the importance of non-WYSIWYG inputs. >>> 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 mista…
Earlier quoted context omitted.
It's genuinely hard to make a good design for something, but if you put the time and effort required, that's the difference between Atom and VS Code. The only way I know how to make a good design, is to have a good Product Owner. Prototyping helps a little bit, User testing absolutely not. You can have five different PO working on the same epic and still get a bad design, but it only takes one to find the perfect sol…
That seems pretty confusing to me, as now you’re left wondering which will actually render, and which text won’t...
If I'm imagining it correctly, it should work like this:
writing `help` will render it inline. A rendered `help`^H becomes an un-rendered `help
The rendering doesn't need to show the backticks, but it seems to me that it's perfectly reasonable to have it exist from the text-editing perspective.
The real problem might be that hitting help can either move invisibly between one of the two stars (technically correct), or jump a star to place the cursor just after p (visually correct).
I would think the best solution is to have all editing keys (eg backspace, delete, insert-then-type) be technically correct, and all movement keys (eg arrow keys) be visually correct.
I think this is also how Typora does its markdown rendering, which was functionally intuitive in my experience (I stopped using it because it slowed down severely with any file larger than like 300 characters, so a worthless text editor, but UI-wise it worked well)
Supposedly this feature is being walked back now. I just received the following from their support. I'm ecstatic to hear this and hope their Product Management has reassessed the importance of non-WYSIWYG inputs. >>> 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 mista…
Firefox Addon: https://addons.mozilla.org/en-US/firefox/addon/disable-slack... Chrome Extn: Pending Review
Per Sean0-'s comment, it looks like this might not be necessary though.
Edited: formatting
[1]: https://github.com/pocc/no-wysiwyg [2]: https://github.com/kfahy/slack-disable-wysiwyg-bookmarklet
Earlier quoted context omitted.
HiPPO stands for HIghest Paid Person's Opinion , a trait of dysfunctional culture, in which power politics trumps data. The concept seems to originate from Netscape's CEO and the acronym exists since 2006, according HiPPO FAQ: http://bitly.com/HIPPOExplained
Why are you trying to track us? Please post non-tracking links https://exp-platform.com/Pages/HiPPO_explained.aspx
Mattermost CEO here. In my mind Slack’s target persona is no longer an engineer (if it ever was) - It is more likely a less tech savvy person who wants a WYSIWYG editor for rich text inputs. For what it’s worth, Mattermost is an open source alternative built for engineers by engineers. The interface is markdown.
imo a fast native client, that doesn't look like a sad slack clone (which teams currently does) would put you streets ahead of the entire field.
I know it means increasing code complexity.
but by golly would it be nice to have a truly nice client.
Supposedly this feature is being walked back now. I just received the following from their support. I'm ecstatic to hear this and hope their Product Management has reassessed the importance of non-WYSIWYG inputs. >>> 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 mista…
I just got the same copy sent to me. Our collective rage is working
Supposedly this feature is being walked back now. I just received the following from their support. I'm ecstatic to hear this and hope their Product Management has reassessed the importance of non-WYSIWYG inputs. >>> 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 mista…
Just for anyone who'd like some confirmation of this. Their official Twitter account it's also saying the same[1] I'm glad they listened to the feedback but their attitude towards people who wrote in with bugs/criticism should also be learned from. Being told 'We know what's best for you, we're not reverting the changes' was pretty insulting. [1] https://mobile.twitter.com/SlackHQ/status/119764013617293721...
I 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…
slack --inspect=4444 //will let ya connect to main electron process via chrome remote debug Then run this require('electron').BrowserWindow.getAllWindows()[0].webContents.executeJavaScript(` javascript:(_ => { const redux = slackDebug[slackDebug.activeTeamId].redux; const {wysiwyg_composer, wysiwyg_composer_ios, wysiwyg_composer_webapp, ...payload} = redux.getState().experiments; redux.dispatch({ type: '[19] Bulk add…