101–110 of 225 posts
Took me a bunch of time to track down the issue, as it worked for a few people, but the bot would completely ignore other people – including my boss.
Earlier quoted context omitted.
Just bring back IRC
Where did IRC go?
Otherwise, all the major networks are still around and two or three of the really really really hardcore old school users from the 90s may still be around. I still ask random geeks I meet if they used to hang in #FreeBSD back in the day, hoping to reunite with old peoples.
Earlier quoted context omitted.
Source?
https://news.ycombinator.com/item?id=21592828
Having the WYSIWYG thing as an option is nice - forcing everyone into it less so.
In case anyone's interested, here's the Chromium bug(s) that's one of the main reasons the WYSIWYG editor has such issues in Chrome(/Electron): - https://bugs.chromium.org/p/chromium/issues/detail?id=102937... - https://bugs.chromium.org/p/chromium/issues/detail?id=608393 - https://bugs.chromium.org/p/chromium/issues/detail?id=608162 The gist of it is that they "canonicalize" the DOM selection when you have two adjac…
It's mystifying, absolutely mystifying, to me that Slack shipped that editor when both electron and chrome show such obvious problems. What sort of out of control process let this get out, and also let them ignore bug reports for so long? This significantly lessens my opinion of Slack and their internal culture. In prior threads there were rumors that Slack employees were hesitant to give negative feedback internally…
Bring back the IRC gateway.
Just bring back IRC
But slack's strength for me comes from decent unfurling of links, threading and history searching - I could live without threading, but link unfurling is a hill I'll die on.
Earlier quoted context omitted.
Ha, I wish I could disable "threads" so nobody else can use them...
We have a culturally enforced strict rule of moving literally ALL new conversations into a subthread and I absolutely LOVE it. This means that if you want to respond to a comment, you never do it in the channel but in the subthread of _that_ comment. This means that when you browse the channel itself, each individual line represents a conversation on a specific topic. You can essentially browse the "headlines" of the…
It is interesting to me that the rant post about Slack's WYSIWYG editor was the 18th most upvoted HN post of all time. No idea what conclusion should I draw from it, if any at all, but surprising for me at least.
lots of hn readers use slack lots of hn slack users disliked the feature lots of hn slack users who disliked the feature went straight to hn to vote up any post complaining about it that's how communities around tech broadly tend to work
They closed the loop, folks!
Now support real Markdown.
"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 feedback on board, disabling the new formatting tool isn't an option that we will be offering."
> regardless of their technical expertise Good luck with that. Trying to make one product powerful enough for the techies yet simple enough for the normies is the software equivalent of Napoleon attacking Russia.