Event JSON
{
"id": "162583f91e67000070e76a8872c7e1e9a084871af722de03a5cbd7c795d85b68",
"pubkey": "0ddebc86c6a4795b5b9079c6034f5790262765f70c72e96bc3cf722148aa3599",
"created_at": 1716317636,
"kind": 1,
"tags": [
[
"p",
"0ddebc86c6a4795b5b9079c6034f5790262765f70c72e96bc3cf722148aa3599"
],
[
"e",
"0ac8f7980d8fbad15d4a5c5354c3e3f7120a49a15550040fee333d2a9c23a73e",
"",
"reply"
],
[
"e",
"b4dd94e6ab9e203e69bbc1ceb28c97747a5c5de53d46a4f415a3b121284bf50d",
"",
"root"
],
[
"proxy",
"https://infosec.exchange/@munin/112480592607154358",
"web"
],
[
"proxy",
"https://infosec.exchange/users/munin/statuses/112480592607154358",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://infosec.exchange/users/munin/statuses/112480592607154358",
"pink.momostr"
]
],
"content": "How -do- you fix this?\n\nYou do not put the capability to automate screen-scraping into the OS as a canonized feature. \n\nYes, this does not stop screen scraping from being possible - it's been around for years.\n\nDisallowing it from the canonical image -of- the OS, however, means that there is an increased barrier in the way of implementing this: an abuser will need to learn how to implement this, and will need to rely on third-party software not integrated into the OS as expected functionality.\n\nThis in turn means that abuse victims are able to rely on tools already in-use to remove third-party software from the computer in order to have more assurance of private operation.\n\nYes, no single measure is capable of ensuring safety. \n\nThis is why it's a security -system- and not a security -item-; systemic effects require an understanding of the entire context in order to evaluate the safety or unsafety of the system.",
"sig": "acd58dda4230615dad8c9c1db277405f479f7b71e91927c34498e1bce3527ce50725816a91fdc74985dfeadf664ec01caa5bf82130a34cc95ec4282bf60e05a8"
}