fix: hide signal messages in chats

[S-FrontendDev]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
adamant-im	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 27, 2025 4:37pm

[github-actions]

Deployed to https://msg-adamant-pr-701.surge.sh 🚀

[S-FrontendDev]

Bug: Showing Signal messages in chats

[bludnic]

I think the issue is that we push the message locally to the chat, so if you refresh the page, the Signal Message will disappear. This means that the nodes don't return Signal Messages neither via WS or REST.

@yoxira can you confirm that these endpoints don't return Signal Messages?

• WS socket('newMessage', (transaction) => {})
• GET /api/chats/get

[yoxira]

@bludnic

• /api/chats/get doesn't return signal messages unless you directly use ?type=3 parameter. Note: because the endpoint always return chat message transactions, type parameter means asset.chat.type
• Node doesn't emit newMessage event. It's a client event (See https://github.com/Adamant-im/adamant-im/blob/dev/src/lib/sockets.js#L152). newTrans event does return all transactions by default, including signal messages.

[github-actions]

Successfully tore down https://msg-adamant-pr-701.surge.sh 🥲