This looks rad, and it's done in a way that ensures reputation is available to anyone without a centralized chokepoint. Now I just need to figure out how to run an instance... nostr:nprofile1qyv8wumn8ghj7enfd36x2u3wdehhxarj9emkjmn99uq3samnwvaz7tmrv4kxcctj9ehx7um5wgh8w6twv5hszyrhwden5te0v5hxummn9ekx7mp0qy2hwumn8ghj7erfw36x7tnsw43z7un9d3shjqg4waehxw309ask2emfwvh82arcduhx7mn99uqzqun2rcnpe3j8ge6ws2z789gm8wcnn056wu734n6fmjrgmwrp58q3x5kwlg are self-hosting docs forthcoming?
Discussion
Is it right that this is basically a 3rd party reputation service? Almost like a security firm that gives background checks and approves people?
Cool I guess that multiple of these could compete with each other.
Thanks! Eventually yes. Not a top priority, but ask if you need help!
It might be simple — I didn't see a main.go. Is there a single binary for relay + dvm, or separate ones? Are the files in cmd the entry points? If the latter, how would I configure the relay and dvm to talk to each other?