3bf0c - 2y
Backwards-compatibility is important not because old events can't be lost, but because beginning to write a Nostr app for fun shouldn't also mean a lifelong commitment to always update your app to whatever new breaking changes are introduced by a committee of anointed gurus.
Dan @Dan - 2y
do event types have a concept of versions?
iefan 🕊️ @iefan 🕊️ - 2y
I couldn't agree more.
648c0 - 2y
Aldo historical first events shouldn't be lost
c80b5 - 2y
Nostr is not immutable. No reasonable person building an app for fun should ever expect that it will work forever in the future. This isn’t money, it’s social. If consensus changes haw they speak it’s reasonable that you should too. Optimizing for the future and protecting protocol simplicity are both far more important that backwards compatibility.
eaf1a - 2y
I kinda agree more with #[1] here
They should!
credomax @credomax - 2y
Stability of the protocol rests on backward compatibility, it actually cannot be underestimated, we have already learned this the hard ways, so let’s not do this again.
