Aditya-138-12 / Aditya-138-12/CSE-Department-Student-Faculty-Visualization-Tool
Pending features of the Chat
- Linguagem predominante
- JavaScript
- Estrelas
- 3
- Forks
- 2
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
- [ ] There are concurrent web socket emits when any user starts typing, but it doesn't stop, cuz there is no `state` controlling that, hence when the user keeps on typing in the `message box`, the web socket keeps on `emitting`, which in turn becomes a total of over a `million web sockets messages` when tested with `~200` simultaneous users using `k6`. So this need to be fixed, cuz it is hurting efficiency so badly.
- [x] Adding backend support to save the chats [7eab776](https://github.com/Aditya-138-12/CSE-Department-Student-Faculty-Visualization-Tool/commit/7eab776e116a35583fe525175a9e6899b1e255cb)
- [ ] Adding dates to display the chats datewise
- [x] Auto scrolling to the latest message
- [ ] Donot allow the same user to open 2 tabs simultaneously
- [x] Also due to inactivity the free render server spins down, hence the web socket connection takes time to switch the protocols, hence add a loader for that [4b1f219](https://github.com/Aditya-138-12/CSE-Department-Student-Faculty-Visualization-Tool/commit/4b1f2199b5992d1137e6bd83051c7c04be7f5fb8)
- [ ] Chat options, like react/report etc
- [ ] Private messaging to a user
- [ ] Replying to a message
- [ ] Live voice calling if supported?
- [ ] Be able to send attachements like Media/Docs etc
- [ ] Record and send audio
- [ ] New message indicator if message not seen
- [ ] Message deliverd/Seen indicator if possible
- [ ] Also i think we need to include a long text input, also a `
` to render the message
- [x] Chats should be selectable [3ed05e6](https://github.com/Aditya-138-12/CSE-Department-Student-Faculty-Visualization-Tool/commit/3ed05e655f93a4513987dc4f5c7378a6b9d827a7)For now only this much features would be enough.
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Direção de pesquisa
Start by splitting the unchecked chat requests into separate scopes and tracing the existing message-box and web-socket flow; the issue names no files or tests. Use the mentioned k6 scenario to measure the typing-emission problem, and define done separately for each selected feature before implementation.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- javascript
- Domínio
- full-stack, networking
- Tipo de issue
- Funcionalidade
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Status de atividade
- Estagnada
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 20/100