anchor.diff:  %% In your module you need to specify the behavior `syn_event_handler' and implement the callbacks.
   %% All callbacks are optional, so you just need to define the ones you need.
   %%
  -%% All of the callbacks, except for `resolve_registry_conflict/3', are called on all the nodes of the cluster.
  +%% All of the callbacks, except for `resolve_registry_conflict/4', are called on all the nodes of the cluster.
   %% This allows you to receive events for the processes running on nodes that get shut down, or in case of net splits.
   %%
   %% The argument `Reason' in the callbacks can be:
  
positive.code: ) -> any().
  
  -callback resolve_registry_conflict(
      Name :: term(),
      {Pid1 :: pid(), Meta1 :: term(), Time1 :: non_neg_integer()},
      {Pid2 :: pid(), Meta2 :: term(), Time2 :: non_neg_integer()}
  
negative.code: %%      scope process had crashed.</li>
  %% </ul>
  %% While all callbacks do not have a direct effect on Syn (their return value is ignored), a special case is the callback
  %% `resolve_registry_conflict/4'. If specified, this is the method that will be used to resolve registry conflicts when detected.
  %%
  %% In case of net splits or race conditions, a specific name might get registered simultaneously on two different nodes.
  %% When this happens, the cluster experiences a registry naming conflict.
  