Event JSON
{
"id": "b18b89e97c7f1df4d0d4fabd4a317832ccf8d2877989092c6c17d59624add49a",
"pubkey": "6d91e7b056ab18986298e04a8b278a5e070a726487fd30a599427c79db9070e9",
"created_at": 1735315703,
"kind": 1,
"tags": [
[
"p",
"99dbdc7e8bf7854db94dfced0af101c53b1f9c12c36c69d91f3b67bac721b86c",
"wss://relay.mostr.pub"
],
[
"p",
"3a05994d5a655b12f676fa46033b3839b5a77cf318e89ef5f4b5fbd1aa5fa9ae",
"wss://relay.mostr.pub"
],
[
"e",
"3a16969482f0187d1b11dc6478abd026d6bf365d109ec1a64030655a7db2eef1",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://fosstodon.org/users/galdor/statuses/113725649975002153",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqn8dacl5t77z5mw2dlnks4ugpc5a3l8qjcdkxnkgl8dnm43ephpkq0d579c In YAML, the status code is an optional entry that defaults to 200. With the new configuration, I cannot really have the same thing, it's either \"reply \u003cstatus\u003e\" or \"reply \u003cstatus\u003e \u003cbody\u003e\".\n\nI can also support a short version (single entry \"reply \u003cstatus\u003e \u003cbody\u003e\") and a detailed one:\n\nreply {\n status \u003cstatus\u003e\n reply \u003cbody\u003e\n}\n\nIn which case status would be optional.\n\nLanguage design is hard.",
"sig": "77e92e0de0547cd43c7f1cdd07eabba7a50d74c70a86af74e6e6c7c680f1167be0ec275b652da457ee368cabf7a07743089a6b4490e7c279a1b09bd9e21eed69"
}