dtonon on Nostr: As fiatjaf pointed out some time ago, Airbnb and Amazon URLs are worse. They have ...
As fiatjaf (nprofile…7nd4) pointed out some time ago, Airbnb and Amazon URLs are worse. They have only one little advantage, they are more resilient, since a random truncation usually doesn't break the full visualization.
I know that our URL are not pretty and highly usable, but if we want to pursuit a real decentralization we have to embrace trade-offs.
The URL is long because it contains useful and necessary data.
If we add a shortening feature to njump and tomorrow it goes down or is somehow captured, every link would become useless.
A shortening service powered by Nostr is possible, it already exist, but it adds complexity and some centralization weakness, and makes accessing the content more fragile.
The only pseudo-solution I can think of is adding a fallback to the entity parsers, so if the entity misses some chars at the end, we can however extract the note1/npub1, maybe with one or two relays. I think it should be possible with bech32.
I know that our URL are not pretty and highly usable, but if we want to pursuit a real decentralization we have to embrace trade-offs.
The URL is long because it contains useful and necessary data.
If we add a shortening feature to njump and tomorrow it goes down or is somehow captured, every link would become useless.
A shortening service powered by Nostr is possible, it already exist, but it adds complexity and some centralization weakness, and makes accessing the content more fragile.
The only pseudo-solution I can think of is adding a fallback to the entity parsers, so if the entity misses some chars at the end, we can however extract the note1/npub1, maybe with one or two relays. I think it should be possible with bech32.