New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Chan.Type.Text -> Chan.Type.Messages1 #5

Open

gkiagia opened this issue Dec 13, 2016 · 0 comments

Member

gkiagia commented Dec 13, 2016

Chan.Type.Text is actually a bad name

unversioned, unlike all the other 'next' interfaces
doesn't really represent the content... nowadays it is very common to have other types of messages as well (images, audio, videos, etc...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment