antoniovdlc / chat Goto Github PK

Yeah, so the scroll to last is a bit broken ... so yeah, may need to look into that! 😬

We want to make this as easy as possible!

Right now we are limited to only seeing the unread messages or the last 10 that were sent to the chat ... ideally the user should be able to load older messages when scrolling all the way to the top!

😬

... I may actually need to add a build step for the front-end after all (even if it's just to put a hash on the assets names) 😒

Because what's the point of a chat app if you don't get notifications when people send messages to the channel? 😬

Copied from: https://github.com/efrei-int/chat/issues/21

For now I've only seen this behaviour in Chrome on mobile, and it does look a little odd with the app's pull to load older messages ... so, might need to look into that!

... yeah, the title says it all! 😬

Copied from: https://github.com/efrei-int/chat/issues/13

Because the world doesn't revolve around Facebook, maybe people want to login with Twitter or Google ... or whatever!

Copied from: https://github.com/efrei-int/chat/issues/18

Find a nice way to add date information into the UI ... Maybe grouping messages under a date "header" like most messaging apps do?

Just a visual update to be able to differentiate one's messages from the others!

Right now every message is sent to the server and then sent back to every client (even the one that sent it) before being painted in the app.

Ideally, the messages sent by a user must be painted directly in the app (and then be confirmed once it comes back from server). That change will allow to deal with errors, retries, and confirmations (à la WhatsApp I guess 😬 ).

Copied from: https://github.com/efrei-int/chat/issues/19

The front-end has grown a bit wild and it's not very DRY ... it might need a little refactor at some point, even tough for now it still holds!

For some reason this error pops-up while trying to login with Twitter:

Error: httpExecute: HTTP response is not 200/OK as expected. Actual response:
Response Status: '401 Unauthorized'
Response Code: 401
Response Body: Error processing your OAuth request: Invalid oauth_verifier parameter
Request Headers: [key: Authorization, val: OAuth oauth_consumer_key="",oauth_nonce="",oauth_signature="",oauth_signature_method="",oauth_timestamp="",oauth_token="",oauth_verifier="",oauth_version="1.0"] 

... 🤷‍♂️

Just a few things that could be improved based on a audit made in the Chrome DevTools!

They say to refresh your browser, but if you're using the app as a PWA there ain't no browser no more ... 😝

From running a little audit on the current version of the chat, a few accessibility errors came up:

An idea would be that when you click on the avatar in the header, it'll open a pan with the list of people connected!

Dates are always such a pleasure to work with ... toLocaleString() doesn't really cut it for me, so maybe looking into improving the date formatting can be interesting!

For now the chat is open to anyone with a Facebook account, but we would ideally want to whitelist/blacklist people so that only certain people can log in and chat!

This would need some discussion about how to best implement user filtering within the app!

Copied from: https://github.com/efrei-int/chat/issues/17