'remote/local' sounds good to me. -- /gc
On Jul 14 06:57 AM, Roman Bolshakov wrote:
I'm not a fan of the renaming movement solely for sake of virtual signalling but here it makes sense. - remote / local Better carries the semantics and it’s short. I have such piece of config for all my mailboxes since I started using mbsync: [...] Channel work Master :work-remote: Slave :work-local: [...] So, it's natural if it becomes: [...] Channel work Remote :work-remote: Local :work-local: [...] Thanks, Roman вт, 14 июля 2020 г. в 01:41, Mehul Sanghvi <mehul.sang...@gmail.com>:> On Jul 13, 2020, at 15:06 , Oswald Buddenhagen < oswald.buddenha...@gmx.de> wrote: > > with all the recent commotion also in the tech world, i'm revisiting the idea to deprecate 'slave' terminology ('master' is much less problematic, but would probably go as well for symmetry). > > i never really liked it anyway once i started to think about it (obviously, quite a while after i introduced it ...), because it suggests a strict hierarchy that isn't really there, as bi-directional synchronization is supported. > the problem is that this equally applies to many potential replacements, like 'replica'. maybe 'clone' is better, as it's more easily associated with having its own life, and git already established the term. but what to put opposite of it? 'origin' again suggests directionality quite strongly. > similarly, 'primary' vs 'secondary' sounds way too hierarchical. > so i came up with just 'first' and 'second'. the problem is that these aren't nouns, so one has to be more verbose to not make it awkward. > 'one' and 'two' would also be weird without context. > then i thought of 'upstream' and 'downstream', but i don't like the long > common part, and these are also directions, not only locations, so somewhat confusing. > so i thought more about polar opposites, and came up with 'north' and 'south'. short, "non-judgmental", and even has a vague positional association with how the typical server-client setup would be typically visualized. otoh, it seems really out of place and therefore kinda silly. > > so, what does everyone else think? bikeshedding season is open! :-D > > > > _______________________________________________ > isync-devel mailing list > isync-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/isync-devel I would go with one of the following: - remote / local - upstream / downstream - source / stream (where a river begins is called a source) It mostly depends on the context and purpose of what you’re doing. Twitter published something related to this, I think last week. Maybe some of their stuff might help ? cheers, mehul _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
