Amethyst will start automatically updating relays that are sending old versions of replaceables or events that have been deleted.

This will help fix many race conditions and simply get rid of old information out there. Some pubkeys have 40 different metadata versions in separate relays.

If your relays start to receive many insertions with dates in the past related to a batch of events the relay just sent out, that's why.

Consider removing rate limits for deletions and updates of older replaceables the relay already has. You can put those in a slower processing queue, but they should be processed and not just discarded.


:catDance:


Isso te fará feliz, certo nostr:npub1vxd0dfst8ljvwva2egrpc53ve8ru78v8aaxfpravchkexmfmmu3sqnrs50 ?!


:RedHeart:


:fire:


The reason I am doing this nostr:nevent1qqsy6yr4sk2dsy3a96uu86cl42ztfc9368a7hwutq2xgv7hl50jtq7qpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tczyprqcf0xst760qet2tglytfay2e3wmvh9asdehpjztkceyh0s5r9cqcyqqqqqqgzm7rzp


This is good. Drives me nuts how many versions of articles are out there or how I have to delete things 50 times and they're still there.


No sure which client you're on about, but there is a broadcast button on Amethyst. Vitor also said recently that:

nostr:nevent1qqsy6yr4sk2dsy3a96uu86cl42ztfc9368a7hwutq2xgv7hl50jtq7qpz9mhxue69uhkummnw3ezuamfdejj7q3qgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqxpqqqqqqz5zepwq