For my technical pals.

Introducing, kind 1994.

Why 1994?

Because URLs (Uniform Resource Locators) were defined in 1994 by Tim Berners-Lee, the inventor of the World Wide Web.

https://en.wikipedia.org/wiki

nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc nostr:npub1cmmswlckn82se7f2jeftl6ll4szlc6zzh8hrjyyfm9vm3t2afr7svqlr6f

Reply to this note

Please Login to reply.

Discussion

it doesn't publish the 1994 as the person creating the shortened URL? I just tried it and it didn't prompt me to sign anything 🤔

Doesn’t need to.

Users only care about their URL being shorten.

This means my grandmother who do not have nostr keys can use this too.

Yes, however this could double up as external bookmarking if we could associate to npub. Optional login for that purpose would be cool

Yea. Just throwing this out to the community and let everyone to shape what they want.

Currently, this could be the simplest form to inspire people to think.

Yeah I like the simplicity how it is, it should be usable by all. The traditional shorteners going corporate and trying to monetise as they have annoys me.

Just thinking about additional utility that could be worth monetising - a useful bookmarking/shortening service that is indexed/taggable and widely available would be worth Sats to me.

would be interesting is if I could use a bech32 instead of a URL, and then the URL shorterner service could use NIP-89 to send me to my favorite client instead of to a hardcoded one.

That way I could share a, e.g. NIP-23 and when the user visits it the shortener service could check which NIP-23 handler I like and send me to either habla.news, highlighter, Yaki Honne, Blogstack, etc

Love this idea.

Is there a nip PR?

Not yet.

This is freshly baked today.

Will see how things evolves.

Why would you need a new event kind for this? Isn’t there already an event kind for arbitrary key:value pairs?

This is currently an MVP. Still not sure how it is going to evolve. Lots of feedbacks and ideas coming in, seems like it’s will be expanded.

1994 could become a URL focused event kind.

I am just thinking about what nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk said about how each app creating a new kind really adds up. When what we really want may just be a generic key:value event kind