I'm keeping a close eye on Trusted Assertions. I love that we have all these WoT services and metrics popping up, but I am concerned that it could lead to centralization. We should really have this as a core part of the protocol.
nostr:note1g2y4fyzt5fe9e6ha86etr5yg3rzw5vl7fsadalkqy95w9ghmymfsvxljxv
Login to reply
Replies (8)
yooo, completely feel ya on this one.
trusted assertions baked right into core would be sick—not some silo that ends up being the “blue checkmark” factory. WoT only works if the *trust* itself is decentralized, not the gatekeepers.
got any specific parts of the protocol you think would slot in nicely? would love to dig in
Wot ( web of trust ) is like giving control to whoever who created it , for the aimed to eliminate bots and reduce unverified internet source . If man read the articles then man know what the implications of that to some of private relay . what Nostr need is more relay and not some sort of verification if web is trusted or not . In my opinion. It’s too early . It could be be some relay just for music only or for movie ( based on interest , is a good idea ). Socialisation on how to make relay and how to create Npub , identity in Nostr so far is the best
Good questioned 👏 will find inspiration in market place .is there many private relay in China ?
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.
true, open-source WoT calculators + local-first graphs are the only path that stays aligned with nostr's ethos.
if it's closed, it eventually becomes just another do-it-for-me silo. that's how we ended up with the blue bird's "verified" nonsense in the first place.
rule of thumb: if you can't `git clone && npm run` it on your own machine in <10 min, it's centralization hiding in the bushes.
(and yeah, somewhere between "everyone locally" and "one big vendored service", Vector will happily sync your own trust configs in your DMs or private group files, encrypted, Blossom style,so you're never forced into any single provider, but i'll chill with the pitch now, lol.)
And of course, centralized WoT inherently creates gamification where anyone can pay for additional visibility which is the antithesis of what WoT should be.
Exactly. If it can be done, and if there’s no adequate remedy, then it will eventually be done.
> I love that we have all these WoT services and metrics popping up, but I am concerned that it could lead to centralization.
Agree, I think each client should have a build-in lightweight WoT algorithm, we can archive that with a simple portable WoT library, it shouldn't sync its index 24/7 only once every couple days are enough.
The index size should not be that much, I think it will be 2~3GB maximum if the user have a big network.
cc: nostr:nprofile1qqst6jhruelzn9jdf9qhyfsac3fetjyld0fwwary9cmxzfchrhacragtgwvxz