791–800 of 1001 posts
- https://bugs.chromium.org/p/chromium/issues/detail?id=608393
- https://bugs.chromium.org/p/chromium/issues/detail?id=608162
If you star/comment on them to increase the understanding for Chrome's team that they are incredibly frustrating that would be amazing!
Earlier quoted context omitted.
Funny enough, I kind of like it better - the way that the enter key changed in and out of a ``` block would always screw me up and I'd end up sending messages before I wanted to, and then instead of bugging someone for 1 message I have to send 3 with the middle being "sorry, hit enter too soon".
There was already a setting for this with markdown: >When typing code with ```, Enter should not send the message. >With this checked use ShiftEnter to send. So they didn't really provide anything new here, just changed the default behavior. edit: formatting
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!
Earlier quoted context omitted.
Why does anyone (tech savvy or otherwise) need to bold or italicize anything. In my mind bolding/italicizing are nice-to-haves alongside emoji. You wouldn't compromise the entire functional user experience of the central feature of your app for nicer emojis. (at least I hope not).
You literally just italicized "need", and I read it the way you intended it. That's why tech people italicize stuff.
Or, as your reply has highlighted, even with the additional emphasis, people will still fail to read it the way it was intended.
Earlier 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.
We shouldn't fetishize control as much. In >15 years what I have seen is that OSS comes with a huge cost of attention - that you'd be better off focusing on your business need. Running most of these OSS even at a medium employee count scale is a full-team-commit-nightmare. It essentially means your it department now needs a specialist who will be able to handle your org quirks, remember the tweaks and keep baby sitti…
That’s not even wrong because nowadays almost all software comes with some OSS contained. So the non oss set is basically empty. I wonder if HN comes with a huge cost of attention because it runs on some OSS lisp?!
You can submit feedback to Slack using "/feedback" command. The nice thing it appears they have real people give you real replies. I encourage people to use it. I asked them for the option to turn it off. An excerpt from their response. > ... we understand that this has caused a disruption in workflows for some of our more technical users. While we don't have any active plans to make this configurable at the moment,…
There are definitely several things that I don't like about Slack, but their support has been very responsive. I've reported at least two issues, and they have always taken my input seriously. A while back, I reported a bug with copy/paste, and they asked questions, acknowledged it, and had it fixed by the next release. More recently, I had a question about why the UI behaves in a certain way I didn't expect, and the…
Earlier 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.
We shouldn't fetishize control as much. In >15 years what I have seen is that OSS comes with a huge cost of attention - that you'd be better off focusing on your business need. Running most of these OSS even at a medium employee count scale is a full-team-commit-nightmare. It essentially means your it department now needs a specialist who will be able to handle your org quirks, remember the tweaks and keep baby sitti…
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!
Other examples: * The UX around threads is still horrendous, and there's no way to turn it off. * There's no way to turn off "drafts", which still causes me to lose messages I'm working on.