We should unify our efforts.
A handful of NIPs to spec out APIs to talk to WoT Service Providers.
I suggest:
1. Nostr WoT Connect — Vitor’s suggestion. This allows users to adjust their preferences, eg select algos, adjust parameters, etc. It would include new user sign up. The idea is clients like amethyst can build the front end for users to adjust their preferences, and users see their preferences take effect everywhere they go, which means no need to change WoT prefs over and over again with each new client.
2. WoT Service Provider Management API. This would be for operators of the WoT Service Provider to manage the service. nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h suggested this and can perhaps take the lead.
3. Maybe a third NIP that describes an API to fetch trust metrics. This is similar in purpose as nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9 ‘s WoT DVM NIP which Vertex uses, but this would not use DVMs. I am guessing a heated discussion can be had over DVMs, one that we won’t resolve in the next week, so let’s just give the community a choice: fetch metrics by this vanilla API NIP or via WoT DVM.
We need some way to come together on these NIPs, and asap as the WoTathon looms near. We can help organize this at nostr:npub1healthsx3swcgtknff7zwpg8aj2q7h49zecul5rz490f6z2zp59qnfvp8p. We should have input from every WoT service provider: Brainstorm, relatr, Vertex. (Others?) But we also need to take into account the perspective of the other side of these APIs, the clients, a perspective that nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z understands well.
nostr:npub176p7sup477k5738qhxx0hk2n0cty2k5je5uvalzvkvwmw4tltmeqw7vgup
nostr:npub17plqkxhsv66g8quxxc9p5t9mxazzn20m426exqnl8lxnh5a4cdns7jezx0
nostr:npub1qe3e5wrvnsgpggtkytxteaqfprz0rgxr8c3l34kk3a9t7e2l3acslezefe
