Is there a way to use Nostr Connect on Iris when it is a PWA? The option disappears on iOS when I add it to the Home Screen nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk
> Not everything that people like is a scam.
Woah now
We should rebalance our priorities to favor relays more.
Relays being transparent is a mistake for long-term sustainability. Relays should be communities. Relays should be invite only for posting, or have some membership requirements. Clients should obviously display which relay a note was from, and you should select destination relays when you make a post. Clients should also offer optional filters by relay to allow users to delve down into more specific communities.
The goal here is to be more like IRC, which maintains infrastructure for free for decades by being more “community-like” with regard to relays and making sure power users have a stake in the relay.
We should not be as siloed as IRC, however. Client integration with multiple relays should find a balance between making the seams between relays obvious but not a hindrance to UX. We should maintain the look and feel of global feeds while fostering per-relay communities.
“Pretty please stop killing innocent people, but don’t worry, we won’t do anything at all if you don’t stop.”
There's a new, separate repo for Nomen specifications, and it's modeled after NIPs. They're called NOMs. I have opened a PR for a new NOM that allows indexers to publish their name data to relays, so that clients don't need to make external (or potentially proprietary) API calls to query names.
I would love feedback if any of you have interest in Nomen development: https://github.com/ursuscamp/noms/pull/1
It’s an extra output on top of any transaction. The size depends on the length of the name, but it’s quite small.
If you choose a 4 byte name “owen” then it would be 42 vbytes in total to register. That’s 4200 sats fee, or $1.54 at current prices + the cost for the rest of the transaction (it can be any transaction as I said).
Me and my entire family are heavily invested into the Apple ecosystem and not one single other person would change if I asked them too. Lol
If fees stay the same, should I implement Liquid support into Nomen? This thing will die if it can’t even get properly started because no one will buy a name because of fees!
The ordinals enjoyers seem to want me to step up my timeline for Liquid names for Nomen… 
What has blown me away are the sheer number of people that just absolutely do not care/excuse mass slaughter of innocent people, using the most paper thin of excuses.
I am attempting to bring global, unique names to Nostr via an open protocol.
I wanted to explain the new release of the protocol (and reference implementation), and why it needed a backward-compatible upgrade. nostr:note1r8s9ack6xmjv8x4vc7ucsgn9vzu9c3kt3eky3pj7nupx70crz9xq90ancn
Nomen Gets A Protocol Upgrade: https://ursus.camp/nomen/2023/11/08/nomen-protocol-upgrade.html
That terror attack likely took them a year or two to plan and execute, and required Israel being historically negligent on their border security (to protect West Bank settlers). Hamas could not repeat it again if they wanted to.
Hamas is not an existential threat to Israel. This campaign is about revenge, pure and simple.
What is existential to Israel is bombing the population of Gaza to oblivion, committing non-stop terror and violence against the citizens of the West Bank, and uniting the entire Muslim world against them. THAT is an existential threat to Israel, and they have brought it on themselves.
Released 0.2.0 of the Nomen Explorer today. Disabled transfers temporarily. Transfers in protocol v0 were broken, they will be fixed soon and released with v1 of the protocol.
Fixed the issue that double-indexed nostr:npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r name 😉
I don’t suppose you would be willing to provide the PSBT so I can open a bug ticket? If not, can you provide an alternative PSBT which generated the error?
It worked! Niiiice
I miss zapping posts
nostr:note1zxetaehzyvvgzjsyj2nxhx5wtns3v2wcv2vutyk3xq74tn7dtk5qtluxpr