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.
Vitor Pamplona
npub1gc…fnj5z
2024-07-11 15:15:39
Author Public Key
npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5zPublished at
2024-07-11 15:15:39Event JSON
{
"id": "4d10758594d8123d2eb9c3eb1faa84b4e0b1d1fbebbb8b028c867affa3e4b078",
"pubkey": "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"created_at": 1720710939,
"kind": 1,
"tags": [],
"content": "Amethyst will start automatically updating relays that are sending old versions of replaceables or events that have been deleted. \n\nThis 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. \n\nIf 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. \n\nConsider 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.",
"sig": "ecb9692cdf7a4db24dde33888ce4f5b4c8e74028bd37e01842ddf12cc731f605cbf72cdd2353efdedd65a9f22fe8cc12120004bc6ad514806b3037fc8287f243"
}