search

Crypton / statusapp

A status application for small groups to keep each other in the loop
Mozilla Public License 2.0
16 stars 4 forks source link

Timeline update wonkiness #198

Open xpkoala opened 8 years ago

xpkoala commented 8 years ago

I currently do not have much documentation on the issue.

At certain junctures of the day I will receive old messages that had not previously generated on my timeline. There is some overlap from the two reports. This behaviour has happened in the past but I have no current ideas on how to reproduce or monitor for the behaviour since one must rely on other users posting to the timeline.

iphone 5s 9.0.1

What was seen when I viewed my Kloak timeline at ~12:15pm

Post from David 11:14am Post from David 11:15am Post from David 12:10pm

What was seen when I viewed my Kloak timeline at ~1:15pm

Post from David 11:14am Post from David 11:15am Post from Almafeta 11:30am Post from David 12:10pm

What was seen when I viewed my Kloak timeline at ~1:15pm

Post from Almafeta 11:30am Post from David 12:10pm Post from Almafeta 1:13pm

What was seen when I viewed my Kloak timeline at ~2:30pm

Post from Almafeta 11:30am Post from David 12:10pm Post from ExplodingSoul 12:52pm Post from Almafeta 1:13pm

bytex64 commented 8 years ago

FWIW, I've seen it, too. It's like some updates don't get included until the second refresh, or perhaps that they are somehow not in the scope of whatever refresh happens the first time, but are the second time.

daviddahl commented 8 years ago

I have known about his and have tinkered with some ideas around adding a Timeline API that returns ciphertext instead of a tight loop that does the decryption. SJCL has a synchronous API for decryption but does not produce plain text very well in a looped operation like the current timelineAPIs.

daviddahl commented 8 years ago

We need to pass off each decryption operation to a worker, it will still render the timeline "asynchronously", but you will see each post just about as it happens. This will also partly solve the "notify user of messages falling on deaf ears" as you will see posts you cannot decrypt as you have not scanned the other user's card - but you will see the other user's handle. Naturally, this feature will also require blocking as someone could spam you with ciphertext:)