John, still not the best scenario, right? This kind of solution is more like a workaround than a real solution — we call it “gambiarra” here in Brazil, there’s no english word to express this kind of trick to get to a state that is not exactly a solution and might cover some cases, some not.
It says to literally confuse the end user with a not-so-accurate label so they must pay attention that you might insert the Linkedin profile where you read Link, or a person Name were it’s read Title. Not very good, I guess.
A simple toggle on clone field that allows the new cloned fields to be renamed would be simply amazing.
Thanks to ACF integration with Gutenberg, this use case has decreased a lot on last months, but when I need this, I keep creating two (or more) visually and semantically identical field groups :/
