@david and I made a gentleman agreement in AOS Convergence. I would implement NIP-85 Trusted Assertions in @npub1kpt9...nhmz, and he would implement Open Ranking into @nosfabrica Brainstorm. Even though I don't believe in NIP-85 I've fulfilled my promise to prove that we can cooperate and finally build a marketplace of interoperable WoT providers. Your turn man 😉

@Vitor Pamplona how can I configure my NIP-85 TA provider in Amethyst? (Vertex is coming to TA btw)

What's funny is that @npub1kpt9...nhmz doesn't yet implement Open Ranking (soon will) The 👑 goes to @Daniel Cadenas for implementing the first-ever Open Ranking provider at AOS Convergence, only 4 days after the protocol was announced!

Announcing the Open Ranking go-sdk 🚀 This sdk allows any golang application to seamlessly interact with any Open Ranking provider. Think about all the golang relays, like algo-relay, khatru, rely etc. Now they all can integrate wot capabilities to filter out spam, provide personalized relay feeds and more, without doing any of the heavy work, and without being coupled to a specific provider!

GitHub

GitHub - Open-Ranking/go-sdk: The official Open Ranking sdk for golang.

The official Open Ranking sdk for golang. Contribute to Open-Ranking/go-sdk development by creating an account on GitHub.

Next I will build a javascript/typescript sdk (help welcome!), and make @npub1kpt9...nhmz implement the Open Ranking protocol

"What have you been working on lately?" This. WoT. Finally. Made. Right

@utxo the webmaster 🧑‍💻 stats went brrr May 19. Very likely bots since I didn't have that.

Life is too short for having to read database.Database, store.Store, index.Index, and other retarded variable names.

lovely