Deprecates NIP-31 alts

[vitorpamplona]

Main reason:

• Relying on the writing client to create a text that will look good in all types of receiving clients is the wrong solution. It's impossible to do a good job given the variety of clients today.

Other Reasons:

1. Nobody is displaying this
2. Current alts are generally not descriptive enough and don't really help the user.
3. Clients still need to allow users to easily open the event in a separate client (or njump) to see what it is about.
4. Alts have exposed private information (mostly metadata) before
5. It leads devs towards unsatisfactory levels of interoperability

[staab]

I agree, nip 89 is a better approach

[fiatjaf]

Instead of deprecating we should do something like this instead: #1828

[fiatjaf]

Also njump.me is displaying the alts, and sometimes they are very useful.

I do agree, however, that relying on client developers to write the alts for the events they emit is very bad.

[vitorpamplona]

I am against changing the NIP (as in #1828) and for deprecating existing NIPs and moving to new NIPs. In that way, we don't rug pull devs by changing the spec. Small changes are fine, big changes no.

[fiatjaf]

I don't get it. The change doesn't break anything or rug pull any devs. It keeps the same spirit of the old NIP but adds a new, more scalable, way to implement it.

Anyway, that's irrelevant, what matters is if we're going to have some way to display something for event kinds not nateively supported in apps.

[alexgleason]

I think alt tags are useful and important. nip89 can be spammed. alt tags are simple.