You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had an issue yesterday in user testing where messages were not being delivered between me and another peer. Restarting fixed the problem, but this issue was difficult to diagnose, because I couldn't see whether we were connected or not, or whether my client was trying to connect to his or vice versa. We should make this more transparent to the user.
PROPOSAL:
User should see a list titled "People" in the left sidebar.
We should use the "online status circles" style from previous iterations of the app to show connected status. empty circle = not connected. green circle = connected. (This is fine for now because we're connecting to every peer in the current phase of the app. Someday we will add separate status for "appears to be online" vs "directly connected" but we don't need to worry about it now.)
We should sort the list by alphabetical order.
One classy touch would be to add a highlight on hover and a tooltip that appears when you hover or click on a user that says "Direct messages coming soon..." or "DMs coming soon..."
The connection status should update as it changes, as close to real time as possible. We should have solid test coverage for this that can manipulate the online status and confirm that the connection updates. We should test cases where the client disconnects cleanly and cases where it the connection is "unplugged".
If we cannot get adequate connection status from libp2p, we should create an issue for ipfs. For this reason I think we should build the backend first and confirm it works with tests before bothering with the frontend. It might be that we won't have what we need to make an adequately informative feature.
The text was updated successfully, but these errors were encountered:
holmesworcester
changed the title
User should be able to see what users they are connected to, and when connection attempts are happening
User should be able to see what users they are connected to
May 12, 2022
BACKGROUND:
I had an issue yesterday in user testing where messages were not being delivered between me and another peer. Restarting fixed the problem, but this issue was difficult to diagnose, because I couldn't see whether we were connected or not, or whether my client was trying to connect to his or vice versa. We should make this more transparent to the user.
PROPOSAL:
The connection status should update as it changes, as close to real time as possible. We should have solid test coverage for this that can manipulate the online status and confirm that the connection updates. We should test cases where the client disconnects cleanly and cases where it the connection is "unplugged".
If we cannot get adequate connection status from libp2p, we should create an issue for ipfs. For this reason I think we should build the backend first and confirm it works with tests before bothering with the frontend. It might be that we won't have what we need to make an adequately informative feature.
The text was updated successfully, but these errors were encountered: