Event JSON
{
"id": "0a3490182c3bd8edfb27c4e5e9c562c5536718580816cb7fb503b85b2183b0c2",
"pubkey": "3b5cfa5901da20cbdde156de05d924297910d9a5d791f6693cce48072cd611a5",
"created_at": 1709732707,
"kind": 1,
"tags": [
[
"p",
"29d67b21c0ec2851b37345c586cf5618ae6b86c45ab6ba47354160d9cbd58405",
"wss://relay.mostr.pub"
],
[
"p",
"774d614ebcf8fa1536805ff86bdbe7763f4f933e21608f14b43c2b1916f38403",
"wss://relay.mostr.pub"
],
[
"e",
"e692e43537b950c6a25cfe7d2b350ebe8fb8ec3f9b865c5ff8c40662613614b9",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://c.im/users/TimWardCam/statuses/112049042702960733",
"activitypub"
]
],
"content": "nostr:npub198t8kgwqas59rvmnghzcdn6krzhxhpkyt2mt53e4g9sdnj74sszss5hasj I think it might be possible to write software that *cannot* be used (in a practical cost-efficient way) in a GDPR compliant manner, however. Look for example at some of the horrible bodges that have been added to some big data databases to allow deletion, which wasn't in the original design, so that the software can be sold to users who care about GDPR.",
"sig": "43bb7fc0a56643583c84485b9868f34207d0c1be36221ef401bd65f18560f90c593cf741f20e621392d552c333b508befd3fb9179105bf1da9a3a4ab6a507103"
}
