I remember in the mid-2000’s we had to stop using master/slave in reference to LDAP and database servers, and (I forget now whether it was IDE or SCSI) the switches on hard drives. The replacement was primary/secondary, which I felt somewhat obfuscated the intended meaning.
I suppose I'll just start using definitions instead: e.g., "the list of allowed IPs". Good luck googling that...
That's pretty verbose. How about acceptlist and denylist (or blocklist)?
For "master/slave" maybe "boss/worker" would be a good substitute?
Lots of words have synonyms, so that's not a real problem. Sooner or later the search results will catch up, and in the mean time it's always an option for a junior developer to ask a question or figure things out themselves by looking at the implementation.
EDIT nope I’m confused, but leaving comment for completeness
EDIT2 what about andlist and nandlist?
primary / replica
Orchestrator / Executor
Even master / minion would be better imo, the I prefer the others already mentioned
But taking a step back, we have decades of lore giving us a sense of what "master/slave", in the technology sense, means. Ditching that for a few seconds of PC glory is madness.