portsoc / chator Goto Github PK

E.g. If the client triggers a code 400 error on the message send due to a blank message. Have a popup appear saying "You can't do this because X" or the like, so the client understands what they did wrong.

Allow the user to press enter after typing to send messages

Custom limit it on a user by user bases

This will allow people to chnage their nickname.

Nicknames people have set would appear next to their messages, for example:

Person A: Hello.
Person A: How is everyone doing?
Person B: I am good, you?
Person A: Yeah I'm good..
Person B: Nice.

etc etc

The app will be storing and sharing strings created by users.
Those strings may be malicious and

• damage our servers, or
• be used to attack other users
  if we do not adequately sanitize them.

This repo is a lot better wink wink nudge nudge
https://github.com/Portsmouth-Computing

When you have sent a message, have the box auto empty and not retain the message within.

to prevent some basic kinds of unkindness

use webRTC to do a p2p connection between clients instead of having to rely instead on a server to communicate new messages to the client

App could allow for username integration and allow the same user to edit messages that they have posted to the message board.

Make it be able to send and receive image in the chat

See title

I suspect there might be an issue with emoji now because by default the DB may not support UTF8 but it can be enabled.

Eventually, we want the chat messages to be persistent.

Anyone with ad-blocking or privacy software (so, everyone) needs to be warned on the login page that they should whitelist the site or login will not work, and you'll not be able to do a nice error handler.

Otherwise you end up with clients that lag behind

Add the widely use twitch emojis from twitch.tv

Messages on the client side have a timestamp next to them based in UTC
Which is based upon when the server received the message

There are several reasons why passing more data per message would be useful.

1. The request for nicknames (#14)- the Nick should not be part of the message content.
2. Adding message timestamps (#16).
3. Messages now have DB ids which could be used in recognising when a message is already displayed on screen and thus does not need to be added (reducing the tendency of the UI to jump when auto-refreshed).

Allow support for emotes within the chat app
https://github.com/twitter/twemoji

It is better to separate the CSS from the HTML

Allow message to be send using markdown

• input field should be auto-focused to reduce user clicks
• enter should submit messages
• messages don't need numbers
• message background should alternate
• stop using serif typeface (this is not 1996)
• text box should expand with text as 281 chars are typed
• Submit and refresh buttons are redundant once auto-refresh and enter-to-submit are working
• UI is prone to jumping - make it smoother by only inserting and removing messages that have changed since the last time (see issue #24 ).

Check on the server side if the message sent is blank as a backup in case code is edited on the client side

Mobile should be a tier-one platform. By default, mobiles try to display web pages as though they're desktop computers. We can make them be honest about their size using viewport.
<meta name="viewport" content="width=device-width, initial-scale=1">

we may want to have a continuous integration / continuous deployment setup