Subnostr

So… Speaking of implementing for interoperability…

I’d really like to see end users be able to “subscribe” to and “share” content filters and follow suggestions from their relays. As it is… WoT filters are implemented ad-hoc across clients. This mostly leaves users “in the dark” and “without options”.

Without users being in control (finding and sharing the best content filters), nostr will be overrun with bots and bad actors. The clients alone won’t be able to keep up.

What you’ve made for nostr wine (apis and AI classifications) is a step toward this goal of “Sovereign WoT” that I’ve been pushing for weeks now.

I’m just a know nothing nobody with a big mouth and crazy ideas. I’d really like to wrap my head around actually what is possible and what is being done in this space.

Maybe you have some time for a brainstorm session to get me on track?

Mazin 1y ago

Sorry for slow response on this…

I don’t think we will ever get a protocol-wide spec for WoT or consensus over how to apply it and where. Some feel strongly that it should only be on the client side, others (myself included) think relays are way better suited for these types of tasks (with some centralization costs). Others feel it should be separate from both in the form of DVMs.

I think it’s inevitable we see several different approaches and it’s apart of embracing the chaos.

Reply to this note

Please Login to reply.

Discussion

ManiMe 1y ago

Thank you. Diversity of solutions is great. But you and I are of the same perspective re: “one way to do it”. I want to strengthen this perspective by developing standards and implementations for others to follow. This will promote adoption, and (more importantly) WoT interoperability for end users.

Regardless of the controversial opinions (all technical or philosophical in nature) the reality is that bots and bad actors will overwhelm content unless nostr cracks the decentralized “moderation” nut. While still unsolved, we know (by the “decentralized” nature of the problem) that any scalable solution MUST allow a “free market” of content filters. So, really, the space of possible solutions is limited more by interoperability than ideology.

Sorry for the long wind. I just think this is an important enough challenge to warrant the extra effort of cooperating to find a solution.