You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are a community of 100.000 user moving from irc to kandan.
Kadan is a great project and we would like to make it better.
The issue is that as we see, the are some bugs that make kandan not ready for us in daily use.
I will make a list observed by our BetatesterTeam and eventually open issuees one by one:
There is no private room support
Without that feature, my team cannot work in public. This is the most important feature in term of priority.
no kick ban user management
For a community large as our is not even possible to think to put the chat public with moderation powers.
attachment are and other stuff (es. channels tabs) needs to refresh the page, otherwise nothing works
This really important for normal users, they cannot use the chat without this feature
the chat does not scroll down automatically on new message if is not focused!
This means only skilled users will be able to use kanban, surely not random people of our community
We really want to make Kanban better and use it, but some must have feature are missing for us.
We are willing contribute some bucks to make some PR happen.
The text was updated successfully, but these errors were encountered:
0vermind
changed the title
Migrating to kandan
Migrating to kandan, missing crucial features
Jun 19, 2015
First off: sorry for the late reply! I've been heads down doing some kandan tweaks lately and have been going through old issues to see if we can add some features. Here's my thoughts:
Agreed on private room support -- it's been a long time coming. The initial idea behind Kandan was that it would be a more of a team chat tool, meaning that more channels made sense, but private rooms really didn't. As it's grown however, people use it more as a public facing chat, which means its nice to then additionally have a private chat as well. While technically you could just launch two kandan servers (one private, one public), it makes sense to have this in general -- it's been a staple of a chat server for years now.
I'm not against kicking and banning as a tool in a chat client (again, it's been a staple for a while), but it does somewhat go against the idea of a team / company chat tool -- usually people aren't kicking and banning employees in a chat client unless they are going to be fired soon as well.
Should be a pretty easy fix, I see this being not too hard to add.
This is one that I think is pretty much a preference thing, and I find it makes much more sense to not scroll down on a new message, unless there is a real use case for it. Not scrolling down on a new message seems to be in line with other chat clients (GChat, Slack, etc), and I know if I'm looking through the history of a channel scrolling backwards, the last thing I'd want to happen would be to be pulled down to be shown a new message
Hope this helps, let me know your thoughts. If you have private questions as well, you can shoot us an email at [email protected]
We are a community of 100.000 user moving from irc to kandan.
Kadan is a great project and we would like to make it better.
The issue is that as we see, the are some bugs that make kandan not ready for us in daily use.
I will make a list observed by our BetatesterTeam and eventually open issuees one by one:
Without that feature, my team cannot work in public. This is the most important feature in term of priority.
For a community large as our is not even possible to think to put the chat public with moderation powers.
This really important for normal users, they cannot use the chat without this feature
This means only skilled users will be able to use kanban, surely not random people of our community
We really want to make Kanban better and use it, but some must have feature are missing for us.
We are willing contribute some bucks to make some PR happen.
The text was updated successfully, but these errors were encountered: