undefined | Better HN

0 pointsKarunamon6y ago0 comments

Re 1: Most users of Slack don't even use the slash commands, so I'd say that requiring what ammounts to CLI syntax to manage channels and accounts, something you get for free in a user-friendly way in most modern communication tools, is a nonstarter.

Re 2: ZNC works, but is a really trash user experience from both sides. For instance, you never really know if someone is there or not. Also no push messages, which breaks the "get this person's attention" thing that most people use it for.

And you get the same problem if for some reason the bouncer loses connectivity.

0 comments

efreak6y ago

1. GUIs can be (and have been) written for channel management and other functions. There's multiple clients (or client plugins) for such functions as changing modes (with checkboxes), changing the topic, etc.

2. ZNC has plugins for push messages, or at least it did when I was using it several years ago. My personal bouncer was configured to automatically set my away status when I went offline; alternatives include (de)voicing (in)active users, changing nickname, etc. When my bouncer had no clients connected and someone sent me a pm, it was configured to send a message to Pushbullet.

If you're not using a bouncer or the bouncer is down, services packages such as anope may include a memoserv for sending messages to offline users; on services login, memoserv will notify you of pending messages.

KarunamonOP6y ago

1: At the client level, sure. Where's the ChanServ/NickServ/OperServ GUI (that interoperates with the 5 or 6 most common service packages?)

2: Which ties right back into point 1 that setting this up is not user-friendly.

j / k navigate · click thread line to collapse