It sounds way less offensive to those who decry the original terminology’s problematic roots but still keeps its meaning intact.

  • BearOfaTime@lemm.ee
    link
    fedilink
    arrow-up
    79
    arrow-down
    19
    ·
    3 months ago

    Or just use the existing terms. People will find issues with just abuut anything.

    • osaerisxero@kbin.melroy.org
      link
      fedilink
      arrow-up
      63
      arrow-down
      14
      ·
      3 months ago

      Leaving aside the problematic nature of the existing terms, the result was that people actually thought a little more about the relationships the things had and started using better/more precise terminology for the relationships: primary/secondary, active/hot/cold, parent/child, etc.

      Net positive all round.

      • Mellow@lemmy.world
        link
        fedilink
        English
        arrow-up
        35
        arrow-down
        5
        ·
        3 months ago

        Woah there. You’re using about 25% more of your brain than the rest of the internet. We’re gonna need you to tone that reasonability down a bit.

        I look forward to setting up my next polyamorous network connection. I can wait for the commands nmcli con choke me daddy ens1 thrupple0

      • fruitycoder@sh.itjust.works
        link
        fedilink
        arrow-up
        16
        arrow-down
        2
        ·
        3 months ago

        This exactly. M/S ment nothing to me messing with HDDs as a kid.

        It arguably only makes sense in a control node/ worker node context, but worker is obvious enough in that context.

    • BarrierWithAshes@fedia.io
      link
      fedilink
      arrow-up
      3
      arrow-down
      15
      ·
      3 months ago

      Yeah this will just piss off the anti-porn/right-wing/tradcath(?) types instead of leftist/neolib/anti-racist types.