Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@M1sf3t what girl? 😂
(I didn’t forget about her but the conversation is so hard to follow because all her messages appeared to come from the future and all my replies shows up BEFORE hers... so now I have to wait for my timeline to catch up to hers before I reply just for the message to show up correctly on both side lol) -
@Wabby UTC is one thing, but using server time for all incoming messages is a must,m. never trust the times on client devices
-
@williamli correct. All messages need to be in UTC aswell as the server, using the servers time for receipt. Then just handle the clients timezone and badabing badaboom.
-
@irene because “we are not there yet”
-
@williamli lol. We are not there yet🤣🤣
So I was using Coffee Meet Bagel to talk to a girl who is currently travelling. We noticed that the messages were sorted out of orders with incorrect time due to the different time zone we are in.
So naturally, I sent them a big report.
Their support team replied by telling me to do the usual. Restart, update, reinstall, delete everything etc (it’s their default answer!!).
I told them I have done those.
They then rephrased my bug report and told me this is expected as the chat was between two parties with a different time so the messages are sorted out of order due to the time difference.
I guess most developer will get ticked off by that... so I sent them a few pseudo code on how chat across different time zones should have been dealt with...
Life of a developer. Debugging and coding even when on a dating app... 🤷🏽♂️
rant