ExploreTrendingAnalytics
Nostr Archives
ExploreTrendingAnalytics
inkan6d ago
There is currently no explainer, but it's constructed so that the underlying logic is made transparent / self-explanatory during use. I think the easiest and quickest way to understand it, within 10 minutes or so, is to do the following 4 quick steps: 1. Log in with NIP-7 / nos2x. 2. Do a quick check that you are connected to the backend. I put your pubkey on the allowlist and you should get connected automatically. (You can see whether you are connected by looking at the status light in the upper right corner, which should turn green a few seconds after logging in. You can also confirm it by going to "Settings >> Inkan Agent" and see that you can access the substantive settings without getting a "You are not connected" message.) 3. Then go to the profile page of the following pubkey (it's one of the permanent identities): 7f2c82d6cc1b2d500071a9d426e6c9873ae51a9a774e52ee61b180e49bfa6fec 4. Look at the notes appearing on that pubkey's profile page. You'll see green "D"s on the avatars. Click on one of these green "D"s and read the explanations. Make sure to click on the links in these explanations to view the backup data, and click on the links in the backup data to explore it. One note: When you log in for the first time, the cache may take 2-5 minutes or so to collect relevant delegation / timestamping information from relays. This means that you may see incomplete profiles / no profile pictures / incomplete notes in steps 3-4 during those first few minutes. Everything should start working smoothly after the initial warmup. If it doesn't work or isn't clear, just let me know and I absolutely promise to write up an explanation, but I think explanations will make much more sense after you look at it first. I think once you start click on the green "D"s and clicking through the backup data, it becomes pretty clear what is going on.
💬 1 replies

Thread context

Root: 0000c130b638…

Replying to: e4f2406db1c1…

Replies (1)

fiatjaf6d ago
I've done it. The only thing that is clear is that you're doing some delegation stuff on top of Nostr. What isn't clear: 1. Why on top of Nostr? I thought this was a different protocol. Is Inkan defined as Nostr+delegation? 2. Where is the delegation path downloaded from? What is this "cache"? 3. What is this "hub" thing? What is an Inkan Agent? Are these two the same? 4. Why do I need to be authorized? Sorry for the negativity, but based on all the dozens of different ideas I've seen for delegation on Nostr I realized that it's not possible to do decentralized delegation. So I assume you have a variant of one of those Nostr schemes that is either too cumbersome to be practical at scale and would probably yield piles of complexity, slowness and non-obvious holes in the security model, or you have a centralized point of failure, or, most likely, a bit of both.
000
0 sats