Have also teased this in recent weeks as I've hacked on it in a background tab... finally had a breakthrough with ingest in the last few days... POC working enough we can start getting it dialed in.

This is a non-authoritative global naming system for Nostr keys with the goal being your slug can work universally across nostr. It's based on straycat's neo4j graph rankings that score users based on Web-of-Trust, then I layer onto that name affinity from kind 0 metadata and activity decay.

@ek is a great example because of the short slug and being not famous but also an actual somebody. (and until this edit I didn't actually follow him, fixed)

As you can see his slug returns "occupied", meaning that when I wire this into shockwallet for custom Lightning addresses or for Lightning.Video channels you won't be able to claim ek@shockwallet.app or lightning.video/ek unless you're him.

If you make your own nostr app you can use this to automatically direct yourdomain.com/ek to his npub, and also tell your users at setup that they probably shouldn't use that name (unless they plan on being more famous than him to overtake his rank).

QA of my boil-the-ocean refactor. It's all done finally but it needs:

This all took way longer than anticipated. The side-effects of these fundamental code changes were more significant than I imagined.

Working on a few things this week:

All subtle, sovereign ways to exist on Bitcoin and Nostr.

I'm building a service that asks for a twitch username as input and builds a top 10 clips compilation .mp4 as output.

I'm thinking of adding a pro service that will create you a monthly top 10 clips compilation. Target audience is "Content creators" who stream on twitch and later upload VODs to youtube.

Thanks: #1262449