News for hackers. Stuff that matters.

A comment on Slack’s new WYSIWYG input box is terrible. Parent comment

Re:Slack’s new WYSIWYG input box is terrible by vorpalhex on Thursday November 21, 2019 @09:48AM (#21594508)
If you have control of the entire IRC stack (the daemon, the bouncers, etc) you can work around a lot of those issues.. though at that rate, it's probably a lot less work to just host something like Riot..
[ Parent | on HN ]
Re:Slack’s new WYSIWYG input box is terrible by DagAgren on Thursday November 21, 2019 @09:55AM (#21594602)
How do you work around the lack of a kept history?
[ Parent | on HN ]
Re:Slack’s new WYSIWYG input box is terrible by bandrami on Thursday November 21, 2019 @09:59AM (#21594660)
In our case, we didn't. Kept history wasn't a feature people used or wanted. Stuff you were going to refer back to later was for email.
[ Parent | on HN ]
Re:Slack’s new WYSIWYG input box is terrible by DagAgren on Thursday November 21, 2019 @10:20AM (#21594916)
As I said, I use this every single day of the week. Not having it means it is not even close to a solution.
[ Parent | on HN ]
Re:Slack’s new WYSIWYG input box is terrible by mavhc on Thursday November 21, 2019 @10:28AM (#21595015)
Quassel, The Lounge, etc
[ Parent | on HN ]
Re:Slack’s new WYSIWYG input box is terrible by DagAgren on Thursday November 21, 2019 @10:33AM (#21595092)
Forcing each user to maintain an always-online machine is not really a good solution compared to just... having the history available to everyone, always.
[ Parent | on HN ]
Re:Slack’s new WYSIWYG input box is terrible by mavhc on Sunday November 24, 2019 @07:55AM (#21620131)
If it's an internal chat system then the server admin just runs that second layer on top for those who want it, they're all multi user
[ Parent | on HN ]
Re:Slack’s new WYSIWYG input box is terrible by vorpalhex on Thursday November 21, 2019 @10:57AM (#21595426)
You just run the bouncers on the same machine as the daemon.
[ Parent | on HN ]
Re:Slack’s new WYSIWYG input box is terrible by DagAgren on Friday November 22, 2019 @03:31AM (#21603866)
This does not strike you as ridiculous, at all?
[ Parent | on HN ]
Re:Slack’s new WYSIWYG input box is terrible by mavhc on Sunday November 24, 2019 @02:10PM (#21622551)
running 2 programs to provide another higher level interface? not really.

IRCd - real time, ram buffering of messages. Quassel - reads and stores buffers in a database, allows users to retrieve them.

[ Parent | on HN ]
Re:Slack’s new WYSIWYG input box is terrible by t34543 on Thursday November 21, 2019 @10:09AM (#21594776)
Lack of history is a feature, not a bug. If you want persistent storage of decisions/etc there are better options out there.
[ Parent | on HN ]
Re:Slack’s new WYSIWYG input box is terrible by eythian on Thursday November 21, 2019 @10:31AM (#21595064)
It is definitely not a feature in most corporate environments.
[ Parent | on HN ]
Re:Slack’s new WYSIWYG input box is terrible by DagAgren on Thursday November 21, 2019 @10:20AM (#21594910)
Yes, like Slack.
[ Parent | on HN ]
Re:Slack’s new WYSIWYG input box is terrible by maxaf on Thursday November 21, 2019 @10:29AM (#21595025)
Slack is more CYA than a store of knowledge. Yes, it's really great for pointing fingers: you can literally link to a specific message, saying "here, this dude made the call".
[ Parent | on HN ]
Re:Slack’s new WYSIWYG input box is terrible by DagAgren on Friday November 22, 2019 @03:32AM (#21603870)
Again: I use it every single day. Not for "CYA". No need to be condescending.
[ Parent | on HN ]
Re:Slack’s new WYSIWYG input box is terrible by xfitm3 on Friday November 22, 2019 @04:21AM (#21604095)
Respectfully it seems like you may be condescending
[ Parent | on HN ]