Muting many Nostr developers and many active and passionate users doesn't look like working together to solve a problem to me. Doing so and posting about it is attention grabbing. This is the second time in two notes that I'm going to make a comparison to Shitcoiners here. There's a better way nostr:nprofile1qqsgeksa4tajm7x673gq2v7t56dkgkh6pjhhzdhrgxlpke4za8jmmkqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgjwaehxw309ac82unsd3jhqct89ejhxqgkwaehxw309aex2mrp0yhxummnw3ezucnpdejqetk0p4. You know this is true.

nostr:nevent1qqs0zv42eyqtf6uyy4chkr9j0lunrvsztdwvghppm4hfpzt4u0mgcjcpzdmhxue69uhhwmm59e6hg7r09ehkuef0qgsgeksa4tajm7x673gq2v7t56dkgkh6pjhhzdhrgxlpke4za8jmmkqrqsqqqqqppe7x97

Reply to this note

Please Login to reply.

Discussion

You're usually on the list too fwiw.

The list is based on my interactions, nothing more.

I don't really read my nostr feeds, I just respond.

I'm sure I'll make my way back there 😜

But for now, I'm content trying to figure out how Pubky (you) and Nostr and join forces, if that's even possible, to win. Otherwise, this is all just a waste of time, money, and an incredible amount of effort.

Well let's start from the extreme:

Just use Pubky tech and build that out instead.

"HAHAHA john so arrogant and crazy blah blah"

Let's skip that part this time?

I know this will never fly, but it is useful to start at the extremes.

I think it is a rational suggestion because anything I would edit about Nostr to fix it would be to make it more like Pubky.

To earnestly vet this would require researching Pubky and understanding the differences clearly.

... but i know this will never happen in a million years due to social and VC reasons.

But what if that really is what is best? What would you do if you were me and you knew that?

I can confidently describe how Pubky fixes every Nostr problem, and then adds more powers. Can a Nostr person confidently refute that?

Absurd! Right?

Well, what I learned is that "interoperability" is just everyone using the same thing, so either we compete or capitulate.

These aren't bad arguments, I just don't have an understanding because I don't know enough about Pubky. This is by my choice and on purpose. I don't want distractions.

I need a previous post or video or something explaining why Pubky is better from your perspective.

Can I use Pubky today? Can I run a client and a server? I could do this in December 2022 with Nostr.

I'm sure you have said all of this before and I'm sorry I wasn't ready to listen then.

I am leaving for the day here in about 30 mins so I'll have to dive in later tonight, but I promise I will.

If you want we can organize a spaces or something and you can ask me or my devs anything you want.

The docs are okay, but it is a different paradigm in some aspects, so requires some recalibration.

I'm willing to learn more.

An honest nostr to pubky comparison video would be the superior approach. Something shareable that anyone in nostr can easily relate to.

Coming here to bitch about how awful nostr is, is not.

Regardless of technical merits, your energy is negative and that doesn't help persuading.

Pubkey is dyndns, and you serve content from your "home server". This is laughably censorable by any man-in-the-middle or casual DoS attack

How is that not just another form of centralization?

If it's true, then it wouldn't be very resilient.

DOA.

So your data only exists on your own server? I can't publish my data elsewhere?

Maybe you can? The main pitch is for "home servers", and the DHT only stores your key's current IP address

We're not going to have 8 billion home servers out there, so hopefully that isn't the case.

Yeah that sums up my take

Great job not learning anything boys, grats on not even trying.

Sorry, you seem more interested in proving a solution than finding one 🤷🏻‍♂️

Why would i look for something i already found?

It's not

Please just read about it instead of associative guessing together.

It is normal dns format, but key-based dns, you can have mirrors, fallbacks, whatever setup you want.

The cool part is you have a definitive place to declare your endpoints, that no one can censor.

We set ours up assuming a primary homeserver, because this obsoletes the need for the relay model entirely.

I want to learn and I will spend some time reading and also we'll have a chat as you suggested.

Bro, nostr uses http and icann dns... just read this

https://medium.com/pubky/mainline-dht-censorship-explained-b62763db39cb

Yeah, and we should do something about it. But without signing events and distributing them you aren't anything approaching censorship resistant

Once you understand the design you will understanding why signing everything is not needed (but you could still do that if you wanted anyway...)

I designed distributed session management for the NYSE. I know *something* about whether signing everything is needed

Then i trust your learning will continue with Pubky.

"Smugky"

Call it what you want as long as you get in here :)

No, nostr is where I am

Let me know when I can post to pubky over Polaroid photo https://github.com/nostr-protocol/nips/pull/1500

Which side of the "Worse is Better" argument are you on, John?

Nobstr (Berkeley) vs Pubeky (MIT)...the right or best thing doesn't always seem to win.

Gimme an invite anyway 😬

What are the nostr problems that pubky fixes?

who you talking to bro? 🤷‍♂️

You have me muted for saying we should fix spam filtering so hashtags could work when you were saying hashtags worked perfectly.

You later said hashtags can never work. You've still never apologized or un-muted me, let alone joined me in trying to make nostr work.

You're worse than John Carvalho by far.

You can just ignore things. 👌

Adult humans can't, due to being an "intelligent species"

We’ve seen this level of arrogance before. It reminds me a lot of a guy named Roger who loved big blocks.

I feel like a loser for not making the list.