Quick thoughts on NIP-95 in no particular order:

- There isn’t anything anyone can do to prevent someone from putting files on a nostr relay. It doesn’t matter what you think of the idea.

- NIP-95 does not belong on the majority of relays (perhaps all) that exist today. If it is ever adopted it will be by specialized relays (likely operated by existing http image hosts) who are willing to give up efficiency for some interoperability gain. I think it is naive to write off the entire spec because it doesn’t fit in to our idea of nostr today.

- Relay operators deserve notice before something like this is released in a major client. I know that won’t be possible forever, but while our ecosystem is still small it wouldn’t take much to get the word out. I think a lot of the reason for the controversy (client rendering aside) is that files were “forced” upon relay operators before most of them even knew NIP-95 had been proposed.

- Open source relay implementations should probably be a bit more selective about the type of events they accept with how quickly nostr is evolving. There may be plenty of other event kinds in the future that you also do not want to store for one reason or another.