Re: About linked data integrity issues: protecting from updates

On 2025-09-23 14:46, a wrote:
> if you want to refer to information that you don't want to change, 
> then you should include that information as it was presented at the time.
I think embedding the whole document (which may be a very long 
`Article`) can be problematic in terms of copyright and privacy.

Using hashes as suggested by Ben sounds more viable in that regard:

On 2025-09-23 19:55, Benjamin Goering wrote:
> tl;dr keep calm and add some hashes. append a hashlink 
> <https://datatracker.ietf.org/doc/html/draft-sporny-hashlink> or ni 
> <https://www.rfc-editor.org/rfc/rfc6920>

But still, there is a problem that an object's content (and hence its 
hash) can change without its author explicitly revising it, due to side 
effects. It would be impractical if a `Like` activity gets invalidated 
every time its `object.replies.totalItems` changes. So you probably want 
a mechanism more sophisticated than just hashing the whole document.

I have discussed the same problem on Fediverse Ideas before (still 
unresolved): <https://codeberg.org/fediverse/fediverse-ideas/issues/45>.

-- 
Daiki "tesaguri" Mizukami
<mailto:tesaguriguma@gmail.com>
OpenPGP primary key: <openpgp4fpr:f706f9bbb8f63cde5f40298fdf5eb02be5c2542e>
Preferred encryption subkey: <openpgp4fpr:070890df2d99c08fd4de0904331a46f78b53c8a5>
Fediverse: @tesaguri@fedibird.com<https://fedibird.com/@tesaguri>
Matrix: @tesaguri:matrix.org<https://matrix.to/#/@tesaguri:matrix.org>
GitHub:<https://github.com/tesaguri>
Keybase:<https://keybase.io/tesaguri>