pull down to refresh

Turtle mode in Robosats?
255 sats \ 9 comments \ @john_doe 5h bitcoin
Hello,
While interacting with a peer on Robosats I noticed a blue sky button with a wave shape and an exclamation mark, on top of the screen where we chat. I pushed it but didn't understand its use. Not sure also if Bitcoin territory is the right one for this question...
It seems that it is in this part of the code: https://github.com/RoboSats/robosats/blob/main/frontend/src/components/TradeBox/EncryptedChat/ChatHeader/index.tsx
So it seems to be in the ChatHeader component. Have you tried it? If you understand how we use it, do you know what it does? And finally if you do know, where did you get your source (e.g.: a guide, the official doc, etc) and possibly put the link if you have?
write
preview
related posts
0 replies \ @john_doe OP 5h
Let me add, the icon was the Wifi tethering icon: https://materialui.co/icon/wifi-tethering-error-rounded
reply
31 sats \ 1 reply \ @Scroogey 5h
https://github.com/RoboSats/robosats/issues/1293
There seem to be two different ways to chat with the peer (either HTTP API or websockets). Turtle mode switches between them. If you have trouble chatting with the peer, try switching. The default should be more reliable (for the average user), and it shouldn't depend on the peer (only on your setup) which is more reliable for you. If you have no trouble chatting with peers, you can safely ignore the feature. If you're curious, try it, it's harmless.
At least that's my understanding.
reply
0 sats \ 0 replies \ @john_doe OP 4h
Ah I see, thanks! So according to your link the mobile app had a limitation the desktop version didn't have (HTTP or Websocket choice for desktop VS HTTP only for mobile). And in this case since I used the mobile app, that is why I didn't see any change.
reply
21 sats \ 5 replies \ @ama 4h
As far as I understand, in slow mode the chat connection is optimized when your connection is unstable or intermittent, like on mobile data when you have low coverage.
reply
21 sats \ 3 replies \ @ama 4h
It seems that messages are sent via POST to a REST endpoint, they're then kept on the server and forwarder via WebSockets to the receiver.
Receiving your messages is done via GET sent every 30 seconds.
Encryption is maintained at all times.
reply
0 sats \ 2 replies \ @john_doe OP 2h
I see, thanks. 30 seconds is good to know. Although I guess this is the worst case scenario when the client has a connection which becomes unresponsive, like for a retry? Most of the time I notice also a delay like some other users but currently with my connection between 50mbps and 100mbps I am pretty sure it is quicker than 30 seconds, more like 1-2 seconds.
reply
21 sats \ 1 reply \ @ama 2h
I've never had any trouble on cable or my own wifi.
When using data on my phone, I always (probably not necessary) select the slow mode and it seems to go always well, also.
reply
0 sats \ 0 replies \ @john_doe OP 21m
I see, thank you for the feedback. According to the GitHub issue provided by @Scroogey however you use by default the "slow" mode if you use Robosats on your phone (unless it changed since May 2024). Indeed in the GitHub issue it says: "The Android app uses the HTTP API of the chatroom. On browser, we use Websockets for instant messaging, but the HTTP API is also available (under the name "Turtle mode" the small icon between the two chat status indicators)."
But I am like you, in "slow" mode it works just fine for me as well.
reply
0 sats \ 0 replies \ @john_doe OP 4h
I see, thanks. According to the link of @Scroogey it wouldn't have make any difference for the mobile app apparently. Button pushed or not, HTTP is the protocol used as far as I understand the GitHub issue
reply