Event JSON
{
"id": "6c4b91027d327fd2c7ad28f3b5a3d71aee02f3fa40f33ffb1f952159b616fbaf",
"pubkey": "ea01c28d25fdebef270fb11977d88794eaa6e04210af4e9f0d45d2ca4df3e28e",
"created_at": 1742161848,
"kind": 1,
"tags": [
[
"p",
"5756e48c151a59e483a3ee9028206897ac79a32e17e93142baea1c430aefcaa8",
"wss://relay.mostr.pub"
],
[
"p",
"02a0f2cd76233181ace57dc1bcc8c69d14efd1b973613d49e6e28b2cb89aee30",
"wss://relay.mostr.pub"
],
[
"e",
"95c7e280ff7091f3c7ed8109aa24eb030752b79c89bea20a244e39a03c8f9eb8",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://chaos.social/users/koz/statuses/114174318894990261",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq2atwfrq4rfv7fqara6gzsgrgj7k8ngewzl5nzs46agwyxzh0e25q6726sn Now, why the Tap? I'm a known skeptic, but basically, I've gotten _extremely_ sick of dealing with Z-offset adjustments. This is perhaps _less_ of a problem on a machine like a Trident, but in my particular case, the combination of the DB mount and the Klicky was losing me _very_ nontrivial amounts of Y travel. I was getting 235, whereas I'm _supposed_ to have 250.",
"sig": "bf9e72e7babcc68c16d6fedf526eb2b229bbf7c6040f0ae9f3f023fc7f419eac4eff7e819165edfc3c5fc80d4bb03ff2563fb1abaf81d01c21df17e6232a05d9"
}
