Chat History on web client

[imzenreally]

Chats doesn't retain history on the web client - I'd think designating a SQLite or something to live on a as card would be easy but I'm no dev

Is this being worked on?

[TechMindsYT]

I second this.. I use web gui for my home install thats on wifi. Would be nice to have the messages retained somehow.

[wojtasie]

+1 on this

[ianmcorvidae]

Looks to be the same issue as #23

(I agree, for the record. either IndexedDB or LocalStorage might be usable for this)

[bmatic385]

+1 on this

[ayysasha]

mega +1

[machineshopuk]

+1

[GiovanniMoretti]

+1 Also.

A related issue is that there's no "recent messages" tab on the web client. On Android you can see the most recent message for each conversation in the Messages (leftmost) Tab but on the web client you have to click on each node to see if there's any new messages from that sender. This is impractical with dozens of visible nodes.

Having a Chat History tab where clicking on a message shortname takes you to that conversation would really make the web client usable as a day-to-day client.

[wesker-albert]

This seems like a no-brainer, and would take the web client from a novelty to regularly usable.

[Hunter275]

The web client currently does not have any way to store messages and the devices do not have enough memory to keep a large amount of message history.

The iOS and Android apps use the phone's storage for message history. There is no such database on the web.

We are looking into possible client-side storage solutions.

[andrewheadricke]

As others have said, IndexedDb or LocalStorage would be a relatively quick and easy solution to get started. Would probably have enough storage to keep all but the longest of conversations.

I started messing around with a PoC the other day, it should be pretty straight forward although I did run out of time.

[andrewheadricke]

Here's a basic chat history implementation using localStorage. Plus unread notification icons. Could do with some tidying up but it basically works.

#342

[blaknite]

I've been inspired by @andrewheadricke's work and fleshed out a localStorage solution in #346

[ToeiRei]

I am starting to think that in the end something like a 'proxy' in the middle would make the most sense for static stations - something where a client can pull chat history from.

[andrewheadricke]

Liam Cottle built something similar to that but for all radio packets not just messages. https://github.com/liamcottle/meshtastic-websocket-proxy

Adding a middleware process would work well for the more tech savvy, but for a quick and easy web UI I think the localStorage is a good compromise. I've been using it daily for the past week, works great.