diff options
| author | Mike Dilger <mike@mikedilger.com> | 2022-12-11 08:02:41 +1300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2022-12-10 21:38:19 -0300 |
| commit | 2fa78a8097745139be5299c9f6117049f7d4a074 (patch) | |
| tree | 322828f23f5a89420d379b22ea19993055d1a70d | |
| parent | 67c021ae9718e423f1ac6ba691dc277440096e65 (diff) | |
Note on nip-22 about moving old posts to a new relay
| -rw-r--r-- | 22.md | 3 |
1 files changed, 3 insertions, 0 deletions
| @@ -26,6 +26,9 @@ The event `created_at` field is just a unix timestamp and can be set to a time i | |||
| 26 | 26 | ||
| 27 | A wide adoption of this nip could create a better user experience as it would decrease the amount of events that appear wildly out of order or even from impossible dates in the distant past or future. | 27 | A wide adoption of this nip could create a better user experience as it would decrease the amount of events that appear wildly out of order or even from impossible dates in the distant past or future. |
| 28 | 28 | ||
| 29 | Keep in mind that there is a use case where a user migrates their old posts onto a new relay. If a relay rejects events that were not recently created, it cannot serve this use case. | ||
| 30 | |||
| 31 | |||
| 29 | Python Example | 32 | Python Example |
| 30 | -------------- | 33 | -------------- |
| 31 | 34 | ||