This is a discussion on whether or not it is better to use it to announce new domain names post-suspension than Wikipedia, not if it can sustain petabytes of data.
Given the archives use of BT, probably better to just use BEP-44 on mainline DHT if you want to store an arbitrary address somewhere - or use something like IPNS, or .onion as others have mentioned.
As nostr relies on gossip, there is no guarantee you will have access to latest address.
I am unaware of an app that sees present day use for communicating short messages that uses BEP-44 or mainline DHT. Nostr works today for millions of people. These services have normal people using them, not Hacker News commentators that are extremely sophisticated -- imagine telling someone who only knows how to use normal web services and apps they install from the app store to "just retrieve a BEP-44 message from the DHT".
I’m not aware of any laypeople who use nostr either.
But if you are going to build some nostr-based “resolver” into a browser you could instead use any of the other protocols - 2 of which are designed specifically for resolution, and the other already having a robust resolver implementation built on top of it?
I quite like nostr, but let’s not pretend it solves every problem.
As nostr relies on gossip, there is no guarantee you will have access to latest address.