Going forward, nostrfy will take a more proactive approach to phasing out features that have been deprecated by Nostr NIPs, by putting them behind flags that default to false.
Letting outdated features stick around indefinitely can hinder the evolution of Nostr. When old relays remain unmaintained, client developers also struggle to maintain compatibility with them.
This may come with some pain, but I want relay-side developers to take the initiative and help everyone thrive on a newer, more modern foundation.
If we don’t take responsibility for this, who will? As a relay-side developer, I want to take responsibility and do my part in moving the ecosystem forward.
Letting outdated features stick around indefinitely can hinder the evolution of Nostr. When old relays remain unmaintained, client developers also struggle to maintain compatibility with them.
This may come with some pain, but I want relay-side developers to take the initiative and help everyone thrive on a newer, more modern foundation.
If we don’t take responsibility for this, who will? As a relay-side developer, I want to take responsibility and do my part in moving the ecosystem forward.