If you're working with Elm or some other cool language/technology I'm sure strategy A would fare much better.
I've done a lot of hiring and we use a "cool" language (Kotlin). We don't mention the language to recruits although it's not a secret (discussed on our website), because we want to hire people with many different platform backgrounds.
As a series A company it was hard to get purist to focus on shipping and we started weeding candidates out that gave off a ‘I just want to work in Clojure’ vibe. Eventually new stuff got written in Java and we migrated off of it due to the hiring pipeline mostly but when we told candidates some honestly dropped out because they were excited to work in Clojure.
I cannot be bothered to create Elm, Haskell, OCaml, F#, Kotlin, Scala, Clojure, Rust, Go, Swift, Angular, React, VueJS, Flutter, Dart .... github repositories, after work on evenings and weekends, just for the tiny chance of getting around the next round.
As if almost 30 year of experience across multiple business domains are worthless.
A) Write "we use PHP4" in the job description. In this case, 98 candidates will nope out when they read this (say 2% won't notice PHP4 or will be desperate) and 10% out of the remaining 2 gives you 0.2 people on average.
B) Be as vague as possible. Write that you use modern tooling and technologies, don't give any details. Now 80 candidates proceed to the next stage. If you only convince 10% of them, you still end up with 8 instead of 0.2.
It's similar to spam - even though >99% people will delete it without even reading, as long as there is a tiniest chance of someone actually buying the advertised product, the spammers will be in the black.