Did the force quite on phone A, same situation.

After that force quite on B and C, same situation.

It's like an umbrella and a raincoat. You can have both, but if the umbrella is big enough then most people would probably ditch the raincoat.

Well on pubky you've got both options, atomic (signed notes) and non-atomic (signed space). So you pick the trade-off you want.

If you choose the atomic option on pubky then it'd be no different to nostr in terms of everything being a signed event, and the trust involved.

On nostr you only have the atomic option. Nostr one option, Pubky two options.

No you wouldn't have to give it up.

On Pubky you can have future plausible deniability, which can be quite empowering for some people. BUT if you don’t want future plausible deniability then you can just sign all your events with your private key nostr style (assuming someone builds out such a client). That's totally an option on the protocol. You have keys at your disposal for whatever you want, same as nostr, want a client that's fully atomic then just a matter of building it.

But it does feel pretty empowering to have that plausible deniability. You want to be able to say it wasn’t me if it actually wasn’t you (your account was hacked) and sometimes you want to be able to say it wasn’t me when it actually was you.

You don't understand how pubky works. I dunno what to tell you. Read the docs.

Depends if you mean a read-restricted relay you run or one that you don't.

In both cases though, it's different because anyone with access to this read-restricted relay can copy the notes, and those notes are cryptographically linked to you, and depending on who you are you might not want that. (And in various other ways too.)

You might want the cryptographic link to be between you and your space, as opposed to between you and your notes.

Works better but still hit and miss. I have 3 phones, all in the same NIP29 group.

If I post a message on Phone A, it appears on Phones A, B and C.

If I post a message on Phone B, it appears only on Phone B and Phone C

If I post a message on Phone C, it also appears only on Phone B and Phone C

If on Phone A I back-arrow out and then go back in, I then see the messages posted by Phones B and C.

On Pubky you have control in the sense that only what's found on your home-server can be considered yours, as in cryptographically linked to you. And you can edit and delete stuff on your home-server at anytime. (Unless you use some future client that signs every note nostr style, but that's not the default way of going about things.)

In terms of read access to your stuff you certainly could control that on Pubky, since the place where things are being read from is your homeserver, not some relay outside of your grasp.

Pubky offers both strong censorship resistance and a high degree control, the trade off is that it didn't emerge from the same sort of quantum soup as nostr, so it's much more managed, at least for now.

Great I'll give it a try now.

Yes, I'm sure the "oh it's a bitcoin thing" accounts for over 90% of the bounce rate.

That's cool. I agree the smart contract side is interesting.

Also to see people stretch zkproofs to the very limit in an effort to graft some sort of smart contract modality onto the non-Turing complete Bitcoin chain is a bit of a head-scratcher to me. I do get the security allure, but it's not as if eth is at risk of a 51% attack or something.

Good for the zkproof industry though.

I don’t see how anyone who doesn’t think bitcoin is a good thing for the world could be made to feel welcome on nostr.

I also don’t see how anyone who thinks bitcoin is fine, and also that eth and solana and usdt are fine in their own ways too, could be made to feel welcome on nostr.

If there are people here that think bitcoin is bad for the world, or that eth and sol are kind of just fine, then I'd love to know what's kept you around?

#asknostr

> companies will not want this information broadcast either, if it links to the company. the users directory events, though, are perfectly fine to be pushed and pulled from company relays if they decide to

All of that is perfectly achievable on PKDNS/PKARR/PUBKY though.

Thanks! I guess you’re in my timezone, Im in Saigon.

If exiting out and then going back to the invite message and then back in again, it will let the new person in, but it will show as a group with only the new person. And then on the device of the person that created the group it will show the group with both people. Same group ID. And messages don’t sync.

Great. Another one is when I invite someone to a nip29 closed group, they get the invitation then they tap on it then it says request to join group, they enter the reason, and then it says duplicate already a member and no way to enter.

Thanks. Im also having an issue with nip29 groups, testing with three phones, when I send a message on one phone it doesn’t show on the other two unless I back arrow out of the group then jump back in, and then it’s there

Got it! What if one group contains the same members as another group plus one or two more?

Ah, thanks!

npub10td4yrp6cl9kmjp9x5yd7r8pm96a5j07lk5mtj2kw39qf8frpt8qm9x2wl seems when you create a new nip17 group and add someone who exists in an old nip17 group with you it just renames the old group instead of creating a new one.

Ah okay see where you're coming from

I tried White Noise on a few phones at once but it failed on a number of very basic things. Feels like Keychat is a year ahead at least, just in terms of stable operation for the chat app basics.

What do you think? nostr:nevent1qvzqqqqqqypzpwgv8jm36e358cq3qn2unt0hmvzaxejnk9mqrlum9m464qd7v7prqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgwwaehxw309ahx7uewd3hkctcqyzu2jpq2wslrqq5vesh39napu3qgyphzemnvr5xjdp3em2l2eg7mqmljl7l

I feel like you've grown distant since then.

Also "you need to be authentic".

Nah, you're 100% right, and you're building stuff that makes sense. Don't let the positivity slop get to you.

How large do you think NIP-29 groups can get while maintaining a half-decent UX?

Relays or clients, user-set client filters or hard-coded client filters, it all leads to a quantum soup one way or the other. Nostr just doesn't do consistency. And the whole point of a poll is that everyone is 100% sure everyone else is seeing the exact same numbers. Otherwise it's not a poll, it's an interpretation generator.

Could work for NIP-29 groups though.

I'm not sure though what Nostr is without clients, devs, relays and users (the components subject to the law).

At that point Nostr is just words in a readme, and the question of freedom versus restriction is kind of irrelevant no?

I don't really get these takes to be honest. UK law is UK law, as a company or an individual doing UK stuff you have to follow it, including companies and individuals doing UK stuff on nostr. This idea that Nostr somehow offers worldwide diplomatic immunity to all associated clients, dev and users is goofballs.

Sure but Im not talking about resistance to being shut down by an instance admin . Im talking about resistance to being shut down by pure economic reality. In that department at least AP is far ahead of Nostr

Yup good debate.

>NOSTR is NOT doing naming just fine. It relies on DNS and ICANN. That’s centralized and fragile. Spaces Protocol solves this by creating decentralized unique names without gatekeepers.

Nostr does not rely on ICANN for my public key, nor does it rely on ICANN for nostr:npub1hyxredcavc6ruqgsf4wf4hmakpwnvefmzaspl7dja6a2sxlx0q3sxwtqnx my handle, or my description, or my web of trust, on and on. That all taken together is enough to represent me on Nostr.

Nostr of course does rely on ICANN for my NIP05, but that's pretty useless to me, so I made it a joke NIP05. (If Primal takes it away tomorrow I could care less.) Nostr also relies on ICANN for relays, which are things and not people. If SpacesProtocol could resolve relay IPs that'd be welcome, but to do so would require communicating with a trusted node, TLS fingerprints, and all sorts of other things SpacesProtocol doesn't do.

>Humans value naming, we’ve built systems to enforce uniqueness (first, last names, SSN’s, drivers licenses, passports, etc.).

First and last name combos are not unique.

SSNs are not human-readable.

You only get both if you have an enforcer.

>You yourself have a name, a picture, and a centralized zap address. Why aren’t you using your npub? Spaces Protocol mirrors this reality as a tiny permissionless layer on bitcoin.

The only reason I have a zap address showing on my profile is because I can't hide it. I don't need it shown at all. People can zap my posts and I'll get the sats no problem. Whether my zap address shows in my profile or not is irrelevant to zapping. People can also zap my profile without caring about my zap address. If my zap address were a long string of numbers it'd all still work fine.

>Spaces Protocol isn’t about control, it’s about providing the coherence users desire without central authorities. Protocols scale in layers, Bitcoin will scale in layers, Spaces Protocol is the Bitcoin identity layer.

It is about establishing a court of law. Let's say I go and inscribe curious@bitcoin on a Satoshi (very easy, I could do it today). Now curious@bitcoin exists on the bitcoin chain, forever, in two places. You'll tell me your curious@bitcoin is the "right one". But you can't argue it's the "right one" because it's "on bitcoin". My curious@bitcoin is on bitcoin too. Mine is also newer. All you can do is point people to the judge, in this case SpacesProtocol, and ask the judge to affirm your case and dismiss mine.

This, Routstr, Chorus, Olas, etc., all so fragile right now when in NIP60. The native wallet concept is so promising yet it feels like two or three years away from a scalable user experience

Nostr/ActivityPub forbidden love child on the way?

https://techcrunch.com/2025/07/16/jack-dorsey-backs-nonprofit-and-other-stuff-experimenting-with-open-social-tools-like-nostr/

50 shades of relay.

Use of a CDN is pretty much unavoidable for a video creator, self hosting or not. That's to say if you do self host and avoid a CDN but still have those view numbers then it'll end up costing you a lot more than if you did use a CDN like Cloudflare.(It's still hosting). It just moves the costs around. And also makes the viewing experience worse. So it's pointless.

Blossom doesn't change any of this. With those view numbers I quoted *someone* is on the line for $50,000 or more per year, whether you self host or not, whether you use blossom or not, all the same. This is core infra, like electricity grid layer.

Your second point is bang on. Though "We have no audience so you won't have to worry about CDN costs" isn't a great sales pitch for creators.

Really good, thanks. The article is a bit of a mess but that totally fits given its key assertion that we ourselves are a bit of a mess!

>provided they take advantage of this flexibility

Key caveat there I think.

And imagine NOSTR loving it.