X.KOJIRA.IO
Timeline

david

[email protected]
npub1u5njm6g5h5cpw4wy8xugu62e5s7f6fnysv0sj0z3a8rengt2zqhsxrldq3
epileptologist and freedom tech maxi
Co-Founder @ NosFabrica
🍇 Grapevine, 🧠⚡️Brainstorm, Tapestry
Trust is contextual.

If you follow someone, does that mean you trust that person to hold your money and babysit your kids? No, it does not.

But when you follow someone, you are literally giving that person the ability to select a piece of content, put it in front of your face, jam it through your eyes and into the back of your skull. The act of following equals entrusting that person with a tiny sliver of your time and attention.

So yes, you do trust the people you follow. Not in all the ways, but in at least one.
The prototype brainstorm (which is klunky but we’re rebuilding it) calculates number of verified followers, muters, and reporters, where “verified” means rank score is above some cutoff. Right now nostria is showing just the rank score, but probably in the future nostria will ingest verified reporter count, which we could easily break down into report type, and show that number, and/or a red flag if it’s above some cutoff.

And these are all personalized scores, not global.
Fiat: algos are hidden 🙈👎🏻

Freedom tech: algos are out in plain sight 😄👏🏻

How can we choose our algos if we have no idea how they work?
You can see archives of previous community calls on our WoTathon page, just scroll to the bottom 😊

https://nosfabrica.com/wotathon
Then that’s not what trust is.
That’s true if you build the aforementioned confusion into the definition of trust. Which you don’t have to do.
That’s true if you define “trust” so narrowly as to make the word useless. Or meaningless. Or both.
That’s quite the sweeping statement! Not sure what you mean.
You’re absolutely right about the need for a vast directed graph. Which is why the Brainstorm prototype uses a native graph database (neo4j) to keep track of follows, mutes and reports.

npub1fjqqy4a93z5zs… is incorporating neo4j into his Orly relay. Also check out npub10mtatsat7ph6r… ‘s Banyan relay which uses neo4j and which is a project for the npub1healthsx3swcg… #wotathon:

https://www.kanbanstr.com/#/board/be7bf5de068c1d842ed34a7…
It’s good to think about how centralization can happen and how we can prevent it. Last thing we want is one big centralized WoT Service Provider.

Which is why WoT SPs need to be open source. Ideally, every human being on the planet calculates trust metrics locally. Second best: some people pay a third party WoT SP to calculate metrics. But everyone with sufficient motivation can do it themselves, with the lowest barrier to entry as possible. And ideally, many people will do exactly that, even if it’s not every single nostr user. Similar to running a BTC node: not everyone runs a node personally, but most could, and many do.
These are great questions that Leo raises. First, what are the WoT primitives that we need but haven’t built yet? Second, where does the “trust signal” come from? Follows and mutes are a start but we need more than that if we want to tackle trust in specific contexts. Which raises the next question: who manages the list of “trust contexts”?

My short answers to these questions:
The trust signal comes from anywhere and everywhere we can get it. Follows, mutes, zaps, reactions, attestations, we use it all. How? Via the magic of *interpretation*, which means: write a script that takes some subset of the raw data (follows, reactions, attestations, whatever) and converts that into a format that is convenient for whatever algo you are using. I need to write an to date article on interpretation — I have an old one but it’s not very well fleshed out.

And who determines the lists of contexts? Who crafts the attestations? The fiat answer: the dev team of some big centralized platform. The freedom tech answer: your WoT. How can that work?

I strongly believe that Decentralized Lists is going to prove itself as one of the primitives for WoT. My WoT will help me
maintain a list of trust contexts, a list of attestations, the list of fields for any given attestation, etc.

It’s hard to envision the role that decentralized lists will play when it’s still just an abstract idea. Which is why one of my great hopes for this #wotathon is to see apps that implement decentralized list curation. A generic app that can be used for any list would be a great entry for the hackathon. Or maybe an app that manages lists for some focused category, like lists of musicians for npub1h8gzew8am6cez… . Let’s see the teams form up and see what we can build!

nostr:naddr1qqnxgetrv4h8gunpd35h5ety943h2unpw35k7m3ddanz6umfd4cxcefdd35hxarnqythwumn8ghj7erpwe5kgtnwdaehgu339e3k7mf0qgsw2feday2t6vqh2hzrnwywd9v6g0yayejgx8cf83g7n3ue594pqtcrqsqqqa28klas25
Gm Derek! ☕️

Separation of Trust and Client

Web of Trust systems in nostr need to generate trust metrics that are contextual, personalized to the end user, and portable throughout the ecosystem. These requirements, in particular the portability requirement, can only be realized when trust metrics are calculated independen…
I mentioned catallax in this presentation I gave a few days ago about NosFabrica and WoT. Starts at around the 12 or 15 minute mark.

https://weare.dcnh.tv/w/samrGVvVY514sasUi3oLmr
This would be awesome for the upcoming npub1healthsx3swcg… WoT Hackathon. Either a generic decentralized lists app, or use decentralized lists to serve a client-specific purpose, like curated lists of musicians, recipes, etc.

#wotathon

nostr:naddr1qqnxgetrv4h8gunpd35h5ety943h2unpw35k7m3ddanz6umfd4cxcefdd35hxarnqythwumn8ghj7erpwe5kgtnwdaehgu339e3k7mf0qgsw2feday2t6vqh2hzrnwywd9v6g0yayejgx8cf83g7n3ue594pqtcrqsqqqa28klas25
btw I like the idea of a hybrid solution. Brainstorm is essentially a hybrid, with strfry and neo4j on a single server.
Who makes the categories? Excellent question. Ok for you as dev to make them for starters, but the only answer that will work in the long run is that your WoT needs to manage the categories.

Which is why I authored this Decentralized Lists custom NIP:

nostr:naddr1qvzqqqr4gupzpef89h53f0fsza2ugwdc3e54nfpun5nxfqclpy79r6w8nxsk5yp0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0qqc8xetjwe5kxefdwpex7anfv3jhyuedvehhyttsv4e8xmmwv9kxj7n9vskhgun4wd6z6mt9w3exjcmn6a2pm6
The main challenge as I see it is to ingest a high volume of events in real time. I’d love to see a general purpose nostr graph db relay, although I don’t think it will ever be as performant as non-graph relays for routine relay functionality.

Did you ever have any difficulties with real time data ingestion? Could you process them one at a time or did you need to batch them together at regular intervals? Or perhaps there was never a high enough volume of DVMs for this to be an issue?
The primary goal of our upcoming #wotathon is to establish an ecosystem of Service Providers for personalized trust metrics, as described in the article below. As a user, I don’t want to see one Trust Score for Alice on Primal, another one on Amethyst, and another one on each new client I visit. I want to see the same personalized metrics on EVERY client I visit. Which means the clients will not be the ones calculating them (for the most part).

What will Primal do once nostr moves in this direction? My hope, and my expectation, is that Primal will either incorporate personalized trust metrics calculated outside of Primal, or will make their own internal service provider which makes personalized metrics available everywhere, internally but also *outside* Primal. In other words, they’d make their own competitor to other Service Providers. They already keep track of lots of data so building a standalone Primal Personalized Trust Metric Service should be doable — just gotta decide what metrics to calculate.

One of the effects of Service Providers is going to be to take power out of the hands of clients. It is valid to be concerned that Primal is on the road to becoming just another Twitter, but the rise of Personalized Trust Service Providers may be how we prevent this from happening.

nostr:naddr1qqc8xetjwe5kxefdwpex7anfv3jhyuedvehhyttsv4e8xmmwv9kxj7n9vskhgun4wd6z6mt9w3exjcmnqyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0qgsw2feday2t6vqh2hzrnwywd9v6g0yayejgx8cf83g7n3ue594pqtcrqsqqqa28dx3qra
This is awesome! Custom hashtag feeds, using #graperank to mitigate spam. 💪🏻🍇
I want to take a step back and consider a bigger question. It’s related and I don’t know the answer.

Currently, a wiki entry or nip nip can be edited by the event author. So how can we enable the community to edit an existing NIP?

One way would be something like git versioning, where your WoT decides what gets merged, but idk if that can work and even if it can, we’re far from ready to implement it.

So here’s another idea. Take NIP-73 as an example. Take the existing version and express it using the nip nip. But we don’t copy the whole thing verbatim. Instead, we replace the table of Supported ID Types with a Decentralized List, one for each type. Each list item adds a row to the table and maybe also includes a corresponding explanation and example.

So when it comes time for you to propose support for NIPs, you simply add another item to the list of supported types.

The complexity would be we’d need a script to ingest the curated list and spit out a markdown file. We’d have to figure out how to make that work.

And we will need to implement vanilla list curation first.
Is this what people will use to manage their relay settings and relay tools account? Or more general purpose than that?
By two event kinds you mean as a wiki entry or using npub1q3sle0kvfsehg… ‘s NIP NIP. For now, the NIP NIP has advantages over the wiki entry method, like a specialized way to list all event kinds used by the NIP.

Are the NIPs at the top of NostrHub pulled directly from GitHub or are they wiki events?
not appropriate?

If Alice writes some piece of content that is a parameterized replaceable event, Bob likes the content, and then Alice updates it, I may want to know whether Bob liked the current version or a previous version.

Suppose Alice turns out to be a bad actor. She vibe coded a good NIP, got some likes, then swapped it out for spam. If Bob endorses spam I’ll be inclined to think maybe he’s a bad actor too, but how do I know whether he liked the spammy version or a previous (non spammy) version?

You’ll point out that the old event will be discarded, so we won’t be able to find the old version, so we won’t know what he liked. If so, we’ll at least know whether Bob liked the current version or some previous (no longer existing) version, information which may be useful even if it doesn’t tell the whole story. And there’s also the possibility that older versions of parameterized content get stored by design for some particular set of use cases, even if that’s not the usual practice.
Is this a relay on android or an android app that talks to a remote relay tools server?
Here’s a question: how should we go about transferring existing NIPs from the old system to the new? Would we like original authors to do it, since they’re replaceable events?

Which just now makes me wonder: when we like or dislike a NIP, should the kind 7 event have both an a tag and an e tag? And leave it up to users to decide whether to pay attention to one or the other or both?
4:20:69
This is awesome 💪🏻
Brainstorm sends 10040 events to Brainstorm relays ( nip85.brainstorm.world and straycat.brainstorm.social/relay ) but also primal, damus, nostr.band, maybe 1 or 2 others
older →