Is it over yet? Who won?

It would be unhealthy to think of all new tech as "competition" to Nostr.

Nostr is not Bitcoin, it isn't an investment that will mature and make you rich (unless you get funded by Jack?).

Nostr is derivative networking protocol tech that builds on the ideas of many people before it (including my own, believe it or not). It is tech that already has been improved upon in various ways, both inside and outside the Nostr community.

Pubky is a strict improvement to Nostr and if that makes you uncomfortable, the cure is to learn more, not to attack it like it is some sort of virus or scam.

I have dedicated the past 12 years of my life to Bitcoin and freedom technology, and the Synonym team has similar stories. Do you really want to just ignore us and discredit us out of spite?

Is that what you want this community to represent, some sort of tribe with taboos and strict allegiances?

That is not how to compete with Bluesky and Big Tech.

Anyway, we will keep doing what we do regardless of any hate, and we will be ready for you and accepting when you arrive to our ideas.

Thank you for your consideration.

nostr:note1lfyj6eehkuyg20878azf9c6p3c8v330uh7wkfxz4f7f2k9fgew2q63ypcv

i mean the code that I can run myself, not someone else's node.

do you know what they're running?

Is there a Cashu mint implementation that supports EUR (or USD, but I am more interested in EUR) tokens and has a callback for hedging for mint and melt operations (minting through Bitcoin of course) and can get an exchange rate somehow?

Bonus points if there would be a way to swap BTC and EUR balances (basically a eur-side melt paying another mint invoice for sats denominated mint).

Of course asking for a friend, I only do testnet EUR.

give me a bazaar any day over a cathederal

pompous cardinals granted their reign by God, i mean the pope

nope, the solution is relays that talk to each other and share events, that forward queries to each other and use each other as second level databases

I will add another dimension to this.

Whatever is possible in Nostr is possible in Pubky.

Not everything possible in Pubky is possible in Nostr.

Whatever schemes you deploy to achieve the features of Pubky won't be simpler or as resistant, but we could easily add signed event-based data and ofc we will have tools for syncing and mirroring.

Just change Nostr to PKARR, then we can fight about the data format later, man!

regarding #2: Pkarr is like DNS it in itself doesn't store data.

but users can point their Pkarr to where their hosting providers are. We also propose a specific API for and HTTP server not too different from WebDav to enable writing arbitrary files in users data stores. So typically a user will sign up to a homeserver, just like they sign up to Google drive for example, and point their pkarr to it. If the hosting provider is misbehaving, the user can point to another hosting provider since they have control over the keys.

Regarding #1 the demo app sends the signed packet to a relay that relays it to a large network of distributed hash table DHT. the only reason you send it to the relay, is because browsers don't support UDP, if you are using native app, that relay is not needed. But even in browser it is still better than Nostr relays, because all pkarr relays are equal, even if you run your own unknown pkarr relay, people will still find your data, because you all eventually publish the data to and query it from the DHT which is what is common and connect everyone, no need for both of us to write and read from common Nostr relays, so Pkarr relays are not cause for centralisation at all, they just support browsers temporarily until they eventually support Pkarr.

as for #3, the format is DNS packet encoding, we didn't reinvent this wheel, it is a very good encoding and very apt for this use case and allows us to leverage all DNS semantics and existing parsers in any language.

Where do you think we are?

UTespresso

Looks very good. Fills many gaps. Works out-of-the-box with nostr.

Sure, but how are you going to sign and broadcast transactions?