Backwards incompatible changes to core functionality like this hurt everyone. This is how forks on open source projects can happen. If developers disagree with the direction of where an app is going, it can be forked as a new project, or a competitor will take over. The market will ultimately decide.

Replies (3)

I find really funny that people are calling this a backward incompatible change or a "hard fork" as if it's breaking from the past. NIP-94 is a simple new event that is now being quoted in kind 1 in the right way of doing so. This is not a breaking change at all. This will keep happening at event kind.
Default avatar
nobody 2 years ago
Yes. Clients don't have to be the same... But not even loading photos is a HUGE issue.