|
Top-level
 Users asserting licensing terms (eg CC) or data protection objection etc info in bios, or in post metadata? The former is easy, so even if of questionable value, perhaps worth considering? The latter requires changes and ongoing support in fedi servers and clients, so harder. Would it achieve the goal? I guess that’s the key question: what is the goal of this? What does success look like, and at what cost? 3 comments
 @neil #AuthorizedFetch does nothing to protect from the dissemination of personal data in at least two very common cases: @neil I’m left thinking that the only way of making legally enforceable terms and conditions work in a federation context (beyond an allowlist or defederating known bad actors) would involve some form of machine-readable terms of use format. Which sounds like something that must’ve been tried so often before with little success (along the lines of P3P for example) and very fragile with so many AP servers running different software and software versions… |
Gregory's Server
I wonder how much of this is rendered moot by enabling authorized_fetch (https://docs.joinmastodon.org/admin/config/#authorized_fetch) or the fedi service equivalent?
Or more use of locked accounts and follower-only posts? (For those who are most concerned.)
I enabled authorized_fetch here a couple of months back, and haven’t noticed any issues.
#lawfedi