nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z Curious what paid relays are actually doing this? As far as I know there are very few subscription paid relays - most are just a one time admission fee so they shouldn’t have to address this concern.
There are some public relays that have changed to paid relays in recent months. Perhaps that could be a cause?
I don't remember, but I saw nostr:npub17u5dneh8qjp43ecfxr6u5e9sjamsmxyuekrg2nlxrrk6nj9rsyrqywt4tp's old metadata (old ln address) in many relays from nostrs.watch . I made a script to update them to the new one but many rejected the new event. :(
You means you broadcast this event to other relay and sometimes they reject it?
Yep
Maybe this event has an old enough created_at field ?
These days i am thinking about that we can't believe the field created_at in the nostr system. Due to many relay don't check the created_at field. Usually we can create a past event. But in many scene, for example a todo system, the created_field is very important.
Even if the created at is old, the relay should replace if whatever it has is older than the new one
