Yes, you should absolutely use whatever is your regular clie...

Raw JSON

{
  "kind": 1,
  "id": "d4074c2079c59ff4653406e144372e14555a37197ea20ae6875b659e17fa8a05",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1788342078,
  "tags": [
    [
      "e",
      "b7645e3eaa6911028414a79d8522b3fc9915f150c58e9bf14f3b007c1884925f",
      "wss://relay.primal.net/",
      "root",
      "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
    ],
    [
      "e",
      "949ef560e68e541fc34992bf83c02f39cfcca98a193e1a8d79a0ebdbf356a0c1",
      "wss://relay.inkan.cc/",
      "reply",
      "199f12c94fe6a2903908c46efcb91190d9993b7380886c98321b59c513dca973"
    ],
    [
      "p",
      "199f12c94fe6a2903908c46efcb91190d9993b7380886c98321b59c513dca973"
    ]
  ],
  "content": "Yes, you should absolutely use whatever is your regular client. 👍\n\nSome fine print 📜 (I think you already know this):\n\n1. You must ensure that your events get OTS-timestamped shortly after their created_at. You can do this by including wss://relay.inkan.cc among your write relays since that relay includes a timestamping service. Or alternatively you can point a timestamping service to some other relay (including your own). The point is that your events need OTS timestamps shortly after their creation. Otherwise Inkan will treat them as not having been validly \"signed and dated\" and will refuse to display them later.\n\n2. You must also ensure that the OTS timestamps are periodically fetched from the timestamping service, packaged into 31045 events, and distributed to relays for storage and retrieval. The Inkan client does this automatically for you when you are logged in. So if you don't log into www.inkan.cc for a while, the timestamps for your recent events may not get distributed to relays and, being unable to find these timestamps, the Inkan client will refuse to display your events. You can correct this situation by logging into the client later and having it catch up on the retrieval and distribution of the timestamps. However, it's better practice to retrieve the timestamps from the timestamping service sooner rather than later, so that you don't have to trust the service over a long period of time to keep your timestamps safe. FYI, you can also ask *another* pubkey to perform this retrieval and distribution of the timestamps on your behalf.\n\n3. It's good practice to periodically retrieve your own 31045 timestamp events from relays so that you can store a backup copy of the timestamps, just as you may want to store a backup copy of your regular Nostr events. The Inkan client has a menu for doing this under \"Inkan Settings.\"\n\n4. You can use amethyst for *posting*, but to *view* the activity of your master identity, you need to go to a delegation-aware client, currently www.inkan.cc. FYI, you no longer need to log into the client to see your identity. Just open the \"Explore\" menu and meta should be listed there. Or you can just click https://www.inkan.cc/users/npub1u280zakdwcv23nqpgatsmz8lw6aj22aa6gjjlx0d50lqr8m8xucq7kf93q , share that profile link with anyone, etc.",
  "sig": "3c5482c5f2547f8b16541ab8803f89dfa060ff0a38de5fe07efa4f260fed68d2c5e50a416a1b2d4e6be0bb7fb6696100962396d53268c4d297820fd64214d0c4"
}