Revert "rename "parameterized replaceable event" to "addressable event""

[fernandolguevara]

Reverts #1418, as addressable concept means that something is specifically identified in a system, event id is applied as this for any event in nostr.
We should keep the old definition until we come up with a new one

[jb55]

nack

[kehiy]

I think we need to make a final decision here. at the moment there are places where we used both of these names. this concept is confusing enough itself.

[bezysoftware]

I find the renaming to "addressable" to make no sense. Now the NIPs, including 01, are polluted with stuff like
a (maybe parameterized) replaceable event and "normal replaceable events"

Bring back "replaceable" and "parametrized replaceable", stop this madness.

[vitorpamplona]

I don't mind either way, but "normal replaceable" is indeed weird.

Maybe it should be just replaceable then. Or just remove the world replaceable and make everything addressable (since "normal replaceables" are also addressable with d="")

[fiatjaf]

The real madness is "parameterized replaceable", that is not a reasonable name. Come up with a better name, or a better set of names, instead, I'm all for that.

"Parameterized replaceable" is not descriptive, like what is the "parameter" that determines its replaceability, or what the hell all that means? "Addressable" matches naddr and "a" tags, that's it. Everything is just convention and getting used to.

But sure I'll clean the NIPs from these broken references, changes that should have gone in that other PR.

[bezysoftware]

@fiatjaf still not a fan, but much better, thx