Nostr Web Client

Yes Coracle, and I updated the field.

Weird, I will try again later.

I tried again and Coracle now generated the kind:10063, but it didn't push it to all my write relays, chronicle.dtonon.com in particular.

I found that chronicle didn't have the read and write flags in Coracle, only the DM one (weird, I didn't update my 10002 in a long time).

So I enabled them in Coracle, but inspecting the sent event, I can see that it added the "read" flag (should be empty).

I deactivated/activated the write/read flags again to force an update, that was correct. Then I updated again the Blossom list, that was now pushed to all my write relays.

Reply to this note

Please Login to reply.

Discussion

hodlbod 5mo ago

Thanks, sounds like something is up, I'll take a look

hodlbod 5mo ago

There was some goofiness with the relay read/write flags related to second-granularity timestamps (if you clicked too fast coracle kept the old version of the event). I've fixed this in the next release.

daniele 5mo ago

Good catch 👍

I don't know the current logic based on timestamps, could make sense using a setTimeout strategy to buffer the updates and wait a little (e. g 2 secs) before firing the final event?

hodlbod 5mo ago

I do that elsewhere, but I use the repository to keep the UI responsive. I might have to do something more though to ensure updates take properly.