I have just started running nostr:nprofile1qqsp2k6lqqqw5uyaeaaeayjd22yu9rymg9ntqsu66kplcc9uu75khtgpzamhxue69uhkxetvd3shytnwdaehgu3wwa5kuegpzfmhxue69uhk7enxvd5xz6tw9ec82cspz3mhxue69uhhyetvv9ujumn0wd68ytnzvuawauwv and timestamping all events published to pyramid.fiatjaf.com with NIP-03 (OpenTimestamps). The timestamp events, kind 1040, are published to nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz's cellar.nostr.wine which is not going to delete them -- and to some other relays.
Somehow this will protect the humanity against the AI takeover in the future, so I recommend other people to do the same with other events. The source code is at https://git.fiatjaf.com/ots_nbot and you can customize the relays, kinds and authors it tries to timestamp, among other things, via environment variables.
If you don't understand how such a simple gesture has such immense powers, listen to Antihashed Podcast episode where this is explained, or ask nostr:npub1t6jxfqz9hv0lygn9thwndekuahwyxkgvycyscjrtauuw73gd5k7sqvksrw.
14 hours later, 229 timestamps published, 76 pending, now alternating between the 4 public calendar servers to alleviate the (enormous) load.
One thing I don't get is how I can send 2 ids for timestamping at the same time and one goes in the next batch, the other only on the following batch many hours later.
1527 timestamps published, 47 pending.
