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 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 ]