Interesting!

Some quick feedbacks:

- You could assume http(s), if the protocol is omitted;

- The path-code is not deterministic, so we end having a lot of different URLs pointing to the same resource, I don't know if this is a good thing;

About the name/payoff, I would use something like "xxxxxxxx, a URL shortner powered by nostr".

"NOSTR URL Shortener" may mistakenly suggest that the url refers to a nostr resource.

The name: zippp.it ?

Reply to this note

Please Login to reply.

Discussion

Thanks for the feedback.! This is the purpose of releasing this MVP. To get such feedbacks. About different URLs to same resource, I had the same thought. Initially I used UUID hash, but it’s way too long, in order to ensure all strings or all lengths can be hash deterministically. So I chose short ID, like YouTube video ID.

It is all about the possibility of a collision. If you choose a shorten id, that I think is fine, you can however make it deterministic, ex. simply cutting a SHA-256 hash.

PS: check the birthday paradox.

Of cause. Thus I chose 10 characters. Referencing YouTube video ID uses 11. And also based on how mission critical when collision happens, for a free URL shortener, it should be fine too.

I also think that 10 chars are ok. So why don't simply do an SHA-256 and cut it? :)