Wadera That's all what I've found so far Per: Wadera Great improvements (Thank you!) get full screen chat will be great UX improvement - expecially on mobile. . I've described here: Wadera hide chat (like chat between peoples or group of peoples - not channels) after leaving. Right now it's still on the list and showing notifications about new messages after leaving which is annoying. Oportunity to improve: notification about new messages when chat is minimised (on chat bar? Separate notification icon) notification about new messages on separate channel on mobile full screen mode (top bar?) integrate with upload extension get options to get e-mail notifications when someone open new private chat / mention me on main channel reacts to messages be able to get link to specific message would be great respond to messages search engine night mode support
Wadera Unfortunetly - last version is unusable if you have multiple channels / chats created: Chat field is pushed up and up so far that's start disappear outside browser window 🙁
askvortsov Wadera Thank you very much for putting these together, not sure how so many issues slipped through the cracks! I'll have fixes within the next 1-2 weeks, as I have exams to study for over the next few days.
Wadera askvortsov I'll have fixes within the next 1-2 weeks, I hope exams go smoothly 😉 Any updates on the foront of bug fixing?
Wadera Feel free to catch me on Discord (mention me here if I'm offline), so I can do some more testing before next release 😉
Littlegolden @Xelson Can you enable the Issue feature on GitHub ? Here it is, the translation .xelson-chat.forum.chat.message.deleted is currently deleted by. It's better to change it to deleted by {user} , so it can be translated to {user} deleted a message. It alse applies to .xelson-chat.forum.chat.message.deleted_forever.
Wadera Littlegolden @Xelson Can you enable the Issue feature in GitHub ? It ill be quite difficult to achive regarding to: Xelson Since I will be absent for quite a long time, @askvortsov agreed to support the extension. Many thanks to him for agreeing to help in my difficult situation!
askvortsov Littlegolden Here it is, the translation .xelson-chat.forum.chat.message.deleted is currently deleted by. It's better to change it to deleted by {user} , so it can be translated to {user} deleted a message. It alse applies to .xelson-chat.forum.chat.message.deleted_forever. I'll implement this when I fix the issues Wadera reported above. Feel free to keep reporting issues in this thread
pupsik Just for fun, enabled this chat, Settings woun't open, no chat showing, Member bar on top gone, Something went wrong while trying to load the full version of this site. Try hard-refreshing this page to fix the error. No error logs
askvortsov pupsik Most likely you don't have Pusher or websockets installed. I'll document this better / have it fail more gracefully before the full release
Wadera askvortsov Or even better - allow it to run without websocket - just add reload button somewhere on frontend and warning / link to docummentation on backend? 😉
pupsik I did it on my test localhost, Since I have no clue what those extensions are, they probably not installed on my machine. lol
askvortsov pupsik Essentially, it's the tech that allows messages to be updated without reloading the page.
pupsik I get that part, just not sure how to install them, or probably no will to temper with it. Seems complex.
pupsik Or automatic reload/refresh about 10 sec. I mean grab any existing chat script and it runs without additional sockets.
luceos Adding multiple methods to fetch data (pull vs push) increases the complexity of the code, the burden of maintenance on the developer and the possibility of unforeseen bugs and security issues. Push technology like websockets are quite simple and you can easily start using it on the free plan from pusher.com with max 100 concurrent users and 200k messages a day.
Wadera luceos Adding multiple methods to fetch data (pull vs push) increases the complexity of the code I didn't know that's make so much difference. In that case - just gracefull failover with link to docummentation and explanation will be fine imho. Epcecially as this extesion slowly grow to something simillar to small text Discord chat and using it without websockets is quite waste of potentiall.
