miljan
· 2w
Had a long conversation with nostr:nprofile1qyghwumn8ghj7vf5xqhxvdm69e5k7tcprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsqg86np9a0kajstc8u9h846rmy6320wdepdeydfz8w8cv7kh9sqv02gjtfg8w this morning. At on...
Scale of 1 to 10 IMO:
1: 1
2: 10
3: 1
4: 8
Narrative in stream-of-consiousness form:
There isn't much protocol that weaves Nostr. I see it kind of like Bitcoin, which has slightly more protocol, at least at the origination: Nostr NIP-01 and the Bitcoin Whitepaper, not what people have built it into with hype, extensible flurries and tweaks. With Bitcoin, for instance, it isn't *really* some magical tech (getting leading 0s on a hash chain nonce and a timestamp server, and distributed network of nodes for both mining and validating Merkle chains), it is the network, which brings us to 2 for Nostr (and Bitcoin). Anybody who has attempted 2 with a distributed social network has big problems with the original attempt at protocol. For WebID with FOAF stuff circa 2010 or so, you had to get servers that would do the bounce for auth (TLS client cert and then validation based on x.509 entries ... kind of like app layer npub filters for Nostr). Like Nostr, there were issues with scale, but my point here in bold is that the biggest asset is the network of relays, *not* the protocol. For Nostr this is even more obvious than Bitcoin, as the protocol is signed JSON with a very simple handshake. The HTTP specification has much more too it. There was a similar deal with early Fediverse; however, the design of Activity pub worked more like pure federation of walled islands. As long as I'm at it atproto, from what I've seen is the best of both worlds... the problem is the protocol is *too* complicated. This leads to a lack of hitting 2, which is my most important aspect here. 3 is good and bad. It gives developers something to do (extending the protocol which is trivial). With a simple protocol it is like a blank piece of canvas. You can do anything with little invested. Plus there are no real barriers. You don't need to know that ins and outs of decades of IETF, W3C, etc., you can just start building and presenting. Likely, too, there is an intersect with 2, I imagine, as you ensure you have some relays. But, in my mind this is a dog/tail horse/cart deal. The number of relays running and networked together is the real gem. Note that there are tons of fun and interesting things to do beyond NIP-01. Sometimes I toy with the idea of NIP-KISS, which strips stuff out like NIP-07 for a simple set of must-haves. (I fucking *love* NIP-07, particularly since I struggled with client certs in web browsers to get WebID to work right fully distributed back in the day.) So... 3 is not a reason, but it might be the motivation to get to 2, so let the devs form their funding cabals, jet to conferences to show off their ideas (or a low key fun event like swamp Nostr with alligators). I'm not really part of this subculture, so not attacking here, just the truth as I see it. There are some incredibly smart folks here with some engineering chops. I don't want to minimize that... just that 3 is much less important than 2. Quite likely this is related to the fact that Bitcoin folks run nodes, and like that ecosystem, the nodes are the real power. And 4 is pretty high as well. Having a dynamic, thriving set of users on your distributed network is key. I think a bit of the US expat in Australia and his protocol that varied from Activity pub... MacGervin (I can't even remember his name right now, nor can find his projects... I imagine he still has a couple hundred users... plus, eventually he federated with Activity pub and Diaspora). But, it was just one dev, and you can feel the grind, as well as his stubborn vision, which I did like... but it was *the users* that kept the thing going.
Well there ya go... stream of consciousness. I have little interest I'm promoting here. I don't do zaps. Sure, stuff is interrelated. Can you have one aspect without another less important one? Well... I wrote enough this morning...
❤️1