Mirror features have been added 3-4 years ago and, to my knowledge, it hasn't really been used until now.
When we stop using the Fuseki WAC extension, every resource will have its own graph. So it won't be possible anymore to store mirror data in a special http://semapps.org/mirror graph.
SemApps offer a lot of tools to sync data. We use these extensively in ActivityPods, for example to aggregate public data in Pods. If at some point a server want to mirror another one, it won't be difficult to do so. But IMO having this as a core SemApps feature was a mistake, because it makes the code more complex (also on the data provider, which executes complex SPARQL queries to find mirror data).
So instead of refactoring the whole mirror feature, I suggest to remove it.
Mirror features have been added 3-4 years ago and, to my knowledge, it hasn't really been used until now.
When we stop using the Fuseki WAC extension, every resource will have its own graph. So it won't be possible anymore to store mirror data in a special
http://semapps.org/mirrorgraph.SemApps offer a lot of tools to sync data. We use these extensively in ActivityPods, for example to aggregate public data in Pods. If at some point a server want to mirror another one, it won't be difficult to do so. But IMO having this as a core SemApps feature was a mistake, because it makes the code more complex (also on the data provider, which executes complex SPARQL queries to find mirror data).
So instead of refactoring the whole mirror feature, I suggest to remove it.