Isn't that just the BSD license with (or perhaps without) extra steps
To quote
wikipedia:
This happens to present the same dilemma about forcing users to use specific licenses when redistributing.
So to answer your question, it's effectively
without extra steps. There
are no steps for users except to enjoy the stuff freely given to them. Or they can hate it; it's their choice. I'm not their mama. I'm not nearly fat enough.
Just wanted to quickly follow this up with some new info I came across: There are some permissive license variants like
0-clause BSD and also notably the
MIT No Attribution License that are considered to be effectively public domain.
In my experience, the main distinction between permissive and public domain licenses basically everywhere (Creative Commons versions vs CC0, for example) is attribution to the original author. In fact, of the common CC license types, CC0 is the only Creative Commons license variant that doesn't include attribution—though I'm sure you could create some weird hybrid most sites won't support properly like with music.

Along with this, there are often copyleft elements that retain an arguably heavy level of control over the copyright of the work (and thus, its users). Controlling how it may be used and distributed, exercising a degree of control over users to the questionable net-benefit of all. This, in essence, is the original distinction I made between Unlicense and BSD in the quotes.
Edit:
BSD-3-Clause-No-Nuclear-Warranty is a fun one—no use in nuclear facilities. But if you can somehow use
sockchat or
firebird to make nukes, all the power to you.
Edit 2: The
Anyone But Stefan Esser (ABSE) License is another fun one with an interesting and lengthy history. See
here,
here, and
here (
archive)—iirc it first appeared a while before Todesco's use here.

Forgive the weird overflowing text here. The site's CSS is done in a wacky way and I needed to fit all content on screen without a scrollbar (a scrollbar that remains regardless of window size

).
The iOS jailbreaking community and the wider computer security scene's issues with Stefan Esser (i0n1c) are > a decade old and could make for decent thread content. I don't remember enough to do it justice in a summary rn, but it's textbook Internet drama.