@julian it’s not a “must”, but it keeps data localized to where it will be used.
-
@julian it’s not a “must”, but it keeps data localized to where it will be used. the forum at B needs to keep at least a cached copy of P1. if A goes down, the cached copy at B still lives.
the user account at B can be logged into in potentially multiple ways; what matters for “fragmentation” is that anyone can tell when two resources are the “same”, i.e. they must be able to tell when two identities are equivalent. post P1 has url R1a and R1b and is attributed to Ua==Ub
-
@julian it’s not a “must”, but it keeps data localized to where it will be used. the forum at B needs to keep at least a cached copy of P1. if A goes down, the cached copy at B still lives.
the user account at B can be logged into in potentially multiple ways; what matters for “fragmentation” is that anyone can tell when two resources are the “same”, i.e. they must be able to tell when two identities are equivalent. post P1 has url R1a and R1b and is attributed to Ua==Ub
@julian i recognize we are not there yet, but i do think we need to broadly move toward an architecture where a server going down isn’t as catastrophic as it currently is.
