Ooohhhh, that's super interesting.
Gonna spin up a new travel key-pair now and I can then figure out how to backfill content later.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub1jutptdc2m8kgjmudtws095qk2tcale0eemvp4j2xnjnl4nh6669slrf04x nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz - any thoughts from a client and relay perspective?
Some relays have a limit on how old of an event they will accept. Strfry for example uses this default (3 years).
rejectEventsOlderThanSeconds = 94608000
Some relay operators will make this more strict to protect disk space/query speed from being dragged down by very old events that (almost) nobody is accessing.
Archive relay will be required then.
