Event JSON
{
"id": "379a59b16a0be0e903e1fa8a0c31068a9040ddf6fe5243ac2b371b0864c28df6",
"pubkey": "27712568050f479dd1204aa1126ca6b1917b59ee54b1a8f51f84fea4ec9785e7",
"created_at": 1693662193,
"kind": 1,
"tags": [
[
"p",
"d82cee3f9b6a7b3411122b824db5ddd1bf3d1109fc9a63c269d98d2543eda760",
"wss://relay.mostr.pub"
],
[
"p",
"803f3ecfc0921ae65a5990d2c963a8699624fdf14b63ba51d2d997b8de65904d",
"wss://relay.mostr.pub"
],
[
"e",
"053685e45af665d5f1a973229c5e1edb828eafdfbbec72876e3d3fa3c0ca5327",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://wandering.shop/users/cstross/statuses/110995845530293065",
"activitypub"
]
],
"content": "nostr:npub1mqkwu0umdfangygj9wpymdwa6xln6ygfljdx8snfmxxj2sld5asqqy8l8c Unknown. The main problem is, a Scriv project is not a file—it's an entire folder. Scriv expects the metadata in the .scriv file *inside* the folder to correspond to the contents. But \"lazy\" syncing only updates individual files on demand, so the files in the project folder may not match what the .scriv file leads Scrivener to expect. If Scriv 4 switches to zipped archives, then fine, but that may slow syncing of large projects ...",
"sig": "2047e208270df22de1d83a533125df1272946985cd5ff7382ace907378dcd34538c76317103ab49f230cce9663f4183fe858a54879d59de4a267b87b77e31fa8"
}