Event JSON
{
"id": "172eead68f8d695004094c81bf4f6309353965625530630380152faa51ccadec",
"pubkey": "cada5bcd6774b5459a9223525827b4d2c3ef946e3b5005746f4009d6d68058c6",
"created_at": 1692521297,
"kind": 1,
"tags": [
[
"p",
"41bed0763d2204d2b3a2d2029900489b1cb4ee8a6814ae5e35f87771799970e7",
"wss://relay.mostr.pub"
],
[
"p",
"a8a9f42bfdfbfae090c15f8c5f53a3a331a125de7f34859820aad225aa6605e4",
"wss://relay.mostr.pub"
],
[
"e",
"3a4b6e084bc0dc1b788e8e937ce024831c097c7814ab407c78534e8f86cadde0",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://writing.exchange/users/ianbetteridge/statuses/110921075762251702",
"activitypub"
]
],
"content": "nostr:npub1gxldqa3aygzd9vaz6gpfjqzgnvwtfm52dq22uh34lpmhz7vewrnsp5h23x It's debatable too, because one of the three clauses in that part of the rules is clearly user facing, while two are ambiguous. Usually in legal docs you would make that much more clear, but Apple like ambivalence. Google's rules, fwiw, are clear that block is required as an \"in app feature\", which clearly means it's a user-feature.",
"sig": "811535f3e28b2fa6ea458db57dced0dfb3e09026bf558045a300a9ab8cef946432cbe120f25a1bae06973329e1b61bc13006f0f86af2ff14af9097e159188554"
}