reply on: Turtle mode in Robosats? \ stacker news ~bitcoin

pull down to refresh

21 sats \ 5 replies \ @ama 4h \ on: Turtle mode in Robosats? bitcoin

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.

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.

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.

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.

0 sats \ 0 replies \ @john_doe OP 33m

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.

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