# Waku v2 dogfooding

## Moved

Moved see [Waku v2 + Communities + Message Reliability Dogfooding](/6RlqxxMdT4yLLejAAMDtCQ)

## Dogfooding sessions - December

~~once we implement [PR#4083](https://github.com/status-im/status-desktop/issues/4083) the desktop team will be asked to use the new release build with a community using the telemetry service for a week.~~

We found & fixed several issues thanks for the telemetry session, the reliability seems to be now at or close to 100% but further testing is needed.

## Dogfooding session - november 10

**partipants:** Anthony, Iuri, Richard

**goals:**
- dogfood a community using waku v2 with 3-4 people for a few days
- test telemetry service

**notes:**
- telemetry service worked
- we did have a case of a single message that wasn't received, however upon restart richard could see the message. in the telemetry service the message seems to have been received so seems to indicate a problem rendering the message in the app, we're not entirely sure if we did checked the telemetry before/after the incident so we're not entirely sure.
- this revealed some painpoints in debugging, so to address we're implementing further improvements to make debugging easier https://github.com/status-im/status-desktop/issues/4083

## Dogfooding session - november 4

**partipants:** Iuri, Richard

**PR to use:** `dogfooding-wakuv2` branch [#4032](https://github.com/status-im/status-desktop/pull/4032)

**goals:**
- test messages are sent/received between desktop and mobile
- retest re-send functionality
- verify again image attachments of various sizes still work
- use a small community for a few days
- use custom store node (setup at `/ip4/157.230.84.160/tcp/60000/p2p/16Uiu2HAmPqnxdF72DWhVVtJqzWxtw6vGEK9MNgdGojS86i581Kc5`)

**notes:**
- client didn't retrieve at first most recent messages, after restarting app the messages appeared. unclear if it's an issue with desktop or status-go
- messages received/sent with mobile and desktop using waku v2
- we tested the light node functionality
- brand new account, fetched correctly historical messages

## Dogfooding session - november 3

**partipants:** Iuri, Richard

We used the `feat/rendezvous` branch in [PR#3751](https://github.com/status-im/status-desktop/pull/3751)

**goals:**
- test real time chat in a public channel
- worked
- test store node message retrieval
- going offline, other sent various messages, going back online after 5 minutes, could retrieve the messages
- test 1 on 1s and sending image attachments, large messages
- at first we had issues with some images not being sent/receive, however upon a hard a reset of the vendor dependency and recompiling status-go the issue went away
- test misc features
- we tested group chats, communities, etc.. all worked as expected

other notes:
- the message re-send functionality did not work
- we found it hard to debug what is happening with the store so the next session we will connect to our own store node so we can see what is happening and debug if necessary