npub1ma…yn9tn on Nostr: Assuming that the solution for surfacing valuable “information” from Nostr will ...

Assuming that the solution for surfacing valuable “information” from Nostr will necessarily evolve from a “webs of trust” style mapping of interactions relative to each user …

The pertinent question to explore for each implementation (like NostrHub below) seems to be “what algos” to use and and “who computes” these recommendations …

I would disagree.

Any freedom respecting solution, must allow useful algos (for each client use case) to emerge from each user’s own network. This will require that the algos themselves (their configs and output) are interoperable across clients and compute providers.

While the questions of “what algos” and “who computes” is still relevant (for each client use case), these are most likely to provide “algo templates” and “useful defaults” that can propagate and be discovered alongside user generated algo configs and service generated output.

TSM is a protocol for exactly this. It’s not perfect (yet), but it’s currently Nostr’s only attempt at standardizing these IO primitives for interoperable recommendation and discovery.

TSM will unleash Nostr’s superpower. Once established, decentralized content curation (with instant propagation of “Nostr’s best” algos) will outperform app centered moderation and recommendation in every metric of user satisfaction as well as cost savings.

#weshouldtalk
Team Soapbox (npub10qd…arpj) MK Fain (npub1jvn…89sc) Alex Gleason (npub1q3s…d26p)

MVP demo is live
https://TrustR.ing

quoting
nevent1q…cu9g

We need to form a strategy around how we're gonna make Nostr win. First we need to surface the information. These are the things I'm thinking about ask I'm working towards the next NostrHub.