In the context of our flagship Pubky app, we use and provide an indexer, which aggregates all related data in the app environment. (Right now it only checks our homeserver, later, whichever the users designate)

But any app could rearrange this and take or leave our indexer, run its own, aggregate indexes, or offer apps that interact differently with the indexer or homeserver data than our app does.

PKDNS basically commoditizes servers by giving users control.

The Nexus indexer creates a semantic social graph for matching keys and URLs.

Wanna try it? :)

Reply to this note

Please Login to reply.

Discussion

Hmm, so the home servers are equivalent to personal nostr relays which just store users data. then for the social app you have a general purpose indexing server.

Would there be anything preventing someone building a desktop app that had the full indexing server running locally?

Id be interested in getting access, but I'm not really interested in the social app side. I'm more curious how the PKDNS and home servers work and how I could build my own. I've been thinking about building something similar for nostr + blossom and I'm interested in how you guys built yours

Yes, the homeservers are intentionally fairly "dumb" other than being normal web servers and having features to provide info to indexers,, and "speak" PKDNS. (Note they are definitely not relays and Pubky currently does not need such a relay network like nostr uses).

Yes, you could build a full desktop app for either mirroring our indexer, or indexing on your own, but note that making your own means your app need some way of collecting and learning about keys. Once you have a key list, then you can learn the data locations and retrieve everything (something nostr can't do, discover data with keys as authority.)

I do think you'll also be interested in the app, because it is wear we will end up expressing our semantic WoT features, and you will already see the potential with the tagging UX 😉