Hi @WPCrafter.com WordPress For Non-Techies - plugin author here!First of, I feel honored being featured, great video all around.A few minor additions, details, or corrections:1 - There is no need for a main site, or "mothership" as you put it. It can help to set up the sync between sites like you described, but in actuality each website is its own "mothership" so to speak. This allows for a whole lot more flexibility. Whenever a sync occurs, the receiving websites know they are being synced up, and won't propagate the sync further to avoid loops.This means, in the case all sites need to be synced, for example with site A, B, C:- site A has sync settings with B and C- site B has sync settings with A and C- site C has sync settings with A and C- when an action is performed on a user on site A (depending on site A's sync settings), site B and C get notified of the change (and react accordingly depending on their incoming settings for site A, but it stops here, B and C do not propagate further)- when an action is performed on a user on site B (depending on site B's sync settings), site A and C get notified of the change (and react accordingly depending on their incoming settings for site B, but it stops here, A and C do not propagate further)- when an action is performed on a user on site C (depending on site C's sync settings), site A and B get notified of the change (and react accordingly depending on their incoming settings for site C, but it stops here, A and B do not propagate further)This is the lengthy illustrated explanation for "There is no “Master Website”: each site is working independently, firing and receiving actions depending on each site’s configuration." in the "How does it work?" section of the FAQ. 2 - Regarding the test buttons, it can be useful to test them all, because each outgoing action must have its sister incoming action checked on the remote site for it to actually happen. Similarly, another person would not be able to connect to your site even if they knew the secret, signature etc, because they would have been able to add their own site with incoming/outgoing actions in your site configuration first, to create this matching incoming/outgoing action pair between the 2 sites ; the IP whitelist is their to ensure there is no man-in-the-middle attack at a lower level on the network itself.3 - About the URLs to use in the settings, you are spot on: it has to match the WordPress configuration. A word of caution: some other plugins may alter this URL under the hood in an intrusive manner (some https plugins do that). If that's the case, it might be necessary to update the URL directly in the wp_options table in the database, or simply use a plugin that's not intrusively manipulating the URL.4 - Regarding IP Whitelist: it is recommended to use the IP in the result of the test log, and not the one from the control panel, because it is possible that between the 2 sites a proxy changes the IP address received by the remote site, and the one in the hosting control panel would therefore not be recognized.In any case, a great video, and I am very thankful for it! This plugin is forever free, and your video is a great way to give back to the community.