https://tim-bouma.npub.pro/tag/nip05/ https://tim-bouma.npub.pro/tag/nip05/rss/ episodic Thu, 25 Jul 2024 13:29:47 GMT Thu, 25 Jul 2024 13:29:47 GMT https://tim-bouma.npub.pro/tag/nip05/ https://raw.githubusercontent.com/trbouma/assets/main/profile_pic_crop.png Thu, 25 Jul 2024 13:29:47 GMT https://tim-bouma.npub.pro/post/note137xuxcpwv2m2a4ex06hm79wu5ynfm6xus8e4y9ndumvvhq84jevs56s6t7/ https://tim-bouma.npub.pro/post/note137xuxcpwv2m2a4ex06hm79wu5ynfm6xus8e4y9ndumvvhq84jevs56s6t7/ note137xuxcpwv2m2a4ex06hm79wu5ynfm6xus8e4y9ndumvvhq84jevs56s6t7 nostr note137xuxcpwv2m2a4ex06hm79wu5ynfm6xus8e4y9ndumvvhq84jevs56s6t7 npub1q6mcr8tlr3l4gus3sfnw6772s7zae6hqncmw5wj27ejud5wcxf7q0nx7d5 A Key Requirement for All 'Trusted Ecosystems'

The key requirement of any 'trusted ecosystem' is to associated an 'identifier' with a 'managed process'. I use those "quoted" terms very liberally because this pattern can apply across a wide array of "ecosystems" and "contexts".

For example in #nostr , the 'identifier' is the #npub and the 'managed process' is reviewing someone's follow list to see if that #npub maps to a real person or not.

In the traditional word, this requirement of mapping an identifier to a managed process is pretty much an implicit assumption. In the web 2.0 world, mostly everyone by default, trusts "example.com" because they assume that whoever "manages" example.com is the legitimate domain name holder and website operator.

Where am I am going with this?

Npubs are a super innovation because they are self-generated and have an independent existence. But (and that's a big 'but'), if they are to be 'trusted' (i.e., relied on because of a 'managed process'), we need to formalize how this can be expressed. Right now the best option I see is #NIP05 because it is somewhat of a managed process (someone manages the #NIP05 website), and it provides an excellent link to the legacy world of domain names. The trick is, of course, is to leverage domain names, but not make it a dependency for the #nostr ecosystem.

Anyway, more thoughts to come....

]]> A Key Requirement for All 'Trusted Ecosystems'

The key requirement of any 'trusted ecosystem' is to associated an 'identifier' with a 'managed process'. I use those "quoted" terms very liberally because this pattern can apply across a wide array of "ecosystems" and "contexts".

For example in #nostr , the 'identifier' is the #npub and the 'managed process' is reviewing someone's follow list to see if that #npub maps to a real person or not.

In the traditional word, this requirement of mapping an identifier to a managed process is pretty much an implicit assumption. In the web 2.0 world, mostly everyone by default, trusts "example.com" because they assume that whoever "manages" example.com is the legitimate domain name holder and website operator.

Where am I am going with this?

Npubs are a super innovation because they are self-generated and have an independent existence. But (and that's a big 'but'), if they are to be 'trusted' (i.e., relied on because of a 'managed process'), we need to formalize how this can be expressed. Right now the best option I see is #NIP05 because it is somewhat of a managed process (someone manages the #NIP05 website), and it provides an excellent link to the legacy world of domain names. The trick is, of course, is to leverage domain names, but not make it a dependency for the #nostr ecosystem.

Anyway, more thoughts to come....

]]> Sat, 27 Apr 2024 12:31:47 GMT https://tim-bouma.npub.pro/post/note1zdh37zz43u544tpkgn6fmxsd8vq43jd80zt4xsp47wrj8lhpvrgsnma85q/ https://tim-bouma.npub.pro/post/note1zdh37zz43u544tpkgn6fmxsd8vq43jd80zt4xsp47wrj8lhpvrgsnma85q/ note1zdh37zz43u544tpkgn6fmxsd8vq43jd80zt4xsp47wrj8lhpvrgsnma85q NIP05 note1zdh37zz43u544tpkgn6fmxsd8vq43jd80zt4xsp47wrj8lhpvrgsnma85q npub1q6mcr8tlr3l4gus3sfnw6772s7zae6hqncmw5wj27ejud5wcxf7q0nx7d5 Ahoy, folks! I'll be going to SEC-02 soon in Madeira and plan to focus my energy on evolving #NIP05 to provide signed metadata. Why? Because I see this a key bridge between the old world and the new world. The NIP is still a WIP. You can read it here:

https://github.com/trbouma/nips/blob/nip05-metadata/05-signed-metadata.md

]]> Ahoy, folks! I'll be going to SEC-02 soon in Madeira and plan to focus my energy on evolving #NIP05 to provide signed metadata. Why? Because I see this a key bridge between the old world and the new world. The NIP is still a WIP. You can read it here:

https://github.com/trbouma/nips/blob/nip05-metadata/05-signed-metadata.md

]]>