Nostr is NOT business friendly. I aim to address this by offering tools and services for building hybrid “Nostr adjacent” clients, allowing businesses to coexist with freedom tech and even thrive together. - Configurable Webs of Trust algos for audiences discovery and conversion. - WoT powered standard APIs for exposing content to Nostr (and other business apps) from within a “black box” business app. - HTTP AUTH integration on ALL business apps, allows users to create local content WITHOUT signatures or private users accounts. - Frost powered “login“ for ALL business apps, allowing users to paste “disposable” nsecs into proprietary clients without fear of it being compromised. - Support for “incremental” (and voluntary) adoption of freedom tech into existing business apps, with easy off-ramps for businesses to transfer more and more siloed data onto the “public” network. These and “other stuff” are on my mind as I read this article by @Alekandar Svetski
Alekandar Svetski's avatar Alekandar Svetski
The last six months have been full of learnings. This most recent essay builds on the last one I wrote (As Nostr as Possible), but focuses specifically on some ‘sacred cows’ in the space whose time for slaying may have arrived. You’ll see very quickly that I’m not shitting on Nostr (far from it). This is about a different perspective and relationship to the protocol. I hope this kicks off a few discussions. https://open.substack.com/pub/futuresocial/p/nostr-unpopular-opinions?
View quoted note →

Replies (20)

I haven't had much time to work on the blocking issues with NVault, but it's purpose (although not explicitly stated yet) is going to be a corporate focused system. Managing credentials and ACls for corporate users and accounts. It will have standard integration with corporate authentication (OIDC only right now, but probably ldap and AD) and allow administrators control over what their employees have access to, which apps, "privacy policy" not filtering, team based keys. Ideally redundant software, hardware and network-based signing device support, all handled from central servers. https://www.vaughnnugent.com/resources/software/modules/nvault
This is great to read, I'm of the mind that unlocking AD in this way will do far, far more for the growth of Nostr as a protocol than any Instagram or Tiktok clone ever could, much respect.
Are any other clients consuming your personalized trust scores using your WoT DVM spec? I really want to see that happen. Do we need to make some noise so devs know this option exists? Talk about it on a pod maybe?
In the back of my mind I’d like to write a long form post on the thought process that everyone in nostr eventually walks down when considering the question: where does the trust signal come from? At first we think follows provides the best signal, then we change our minds and think the best signal should come from explicit trust attestations, then we realize the signal comes from lots of directions and we need to figure out how to interpret it no matter where the signal comes from. Which is much more tractable than it sounds.
i saw a bug
il_lost_'s avatar il_lost_
Top Reputable Followers are the same in npub dot wordl, this means top, but one expects there to be more than 6. so if you look at the profile of a top 6, you don't go out of the structure. Example if you search the "Fiatjaf"
View quoted note →
Chip, as you describe, nvault solves yet another real world need for business interacting with Nostr. Adding to my list above : - secure usage of “master” business nsecs, in an environment where “authorized” use of such keys will change over time. 👀
We do. It’s called GrapeRank. It has a pluggable architecture to normalize “interpretations” of content and users from any source. Pluggable interpretations is the plan! 💯
It's using Global Pagerank because it's public, signed out access. If you tried Personalized Pagerank via DVMs you'd see the world from your own perspective. Also, Vertex has a recommendation DVM you can use to find new people (high rank profiles you don't follow)
The idea is that we have no choice but to use the data that is available to us. We go where the signal is. Different people will have different ideas on that. Example: if you trust zaps more than anything else, someone (a dev) will need to write a (relatively simple) script that transforms zaps into a format that is ready to be consumed by your GrapeRank calculation engine. Perhaps unsurprisingly, that format resembles an explicit trust attestation; it has a rating, a confidence, and a context. The format that my WoT engine employs may or may not be identical to the format that yours employs. I’m not sure what you mean by sentiment analysis, but whatever it is, you or some other dev would write a script to consume raw data (nostr events) and spit out data ready to be utilized by GrapeRank. If it’s a good signal then you could share the “interpretation” script with other users. Hopefully that makes sense … let me know if it doesn’t!
when will you be able to log in then, is this something you've been thinking about doing? Or is there somewhere else you can use like datamachine or dvmdash in the future. I don't know why you used new kind, 5313 could be 5301, 5315 can be 5303