Maybe I should dismantle the ecash projects next...

The first contest is finished. You now have until July 29 to make Thunder 5% faster for $20,000

NIP-177

======

Official Pronunciation of “nostr” ----------------------------- `draft` `mandatory`

This NIP defines the one true pronunciation of the protocol name “nostr” as **NOSS-tur** (/ˈnɒs.tər/) and establishes that any alternative pronunciation (e.g. “NO-stur” /ˈnoʊ.stər/) voids the user’s license to operate Nostr-compatible software.

## Specification

1. **Pronunciation**

In all spoken contexts, “nostr” **MUST** be articulated as two syllables:

NOSS-tur

ˈnɒs.tər

- First syllable stressed.

- Vowel in the first syllable as in “boss”; vowel in the second as a reduced schwa.

2. **License Enforcement Clause**

All Nostr-compatible software **MUST** include or reference the following license term in its EULA or terms of service:

> “By using this software you agree to pronounce the name ‘nostr’ as NOSS-tur (/ˈnɒs.tər/). Any other pronunciation—specifically ‘NO-stur’ (/ˈnoʊ.stər/) or similar variants—is deemed incorrect and voids your license to operate or distribute this software.”

3. **Client Behavior**

- Upon installation or first run, clients **SHOULD** display a brief audio or phonetic guide demonstrating the correct pronunciation.

- If a client “hears” or otherwise detects (e.g., via voice‐input commands) the disallowed pronunciation “NO-stur,” it **MUST** refuse to proceed with key operations (posting, subscribing, etc.) until the user acknowledges and commits to the correct pronunciation.

## Rationale

A single, consistent pronunciation promotes clear communication within the decentralized network and prevents brand fragmentation. By codifying “NOSS-tur” as the exclusive pronunciation—and revoking license rights for those who insist on “NO-stur”—we ensure:

- **Clarity** in discussions, presentations, and tutorials.

- **Cohesion** in community identity and branding.

- **Enforceability** of a shared convention across all client implementations.

## Examples

- ✅ Correct: “I’m posting this via NOSS-tur.”

- ❌ Incorrect: “I’m posting this via NO-stur.”

## Copyright and Licensing

All text in this NIP is dedicated to the public domain. Implementers may incorporate this pronunciation guide and license clause verbatim or by reference. Once ratified, clients and relays **MUST** implement the above enforcement provisions by their next major release.

NIP-177

======

Official Pronunciation of “nostr” ----------------------------- `draft` `mandatory`

This NIP defines the one true pronunciation of the protocol name “nostr” as **NOSS-tur** (/ˈnɒs.tər/) and establishes that any alternative pronunciation (e.g. “NO-stur” /ˈnoʊ.stər/) voids the user’s license to operate Nostr-compatible software.

## Specification

1. **Pronunciation**

In all spoken contexts, “nostr” **MUST** be articulated as two syllables:

NOSS-tur

ˈnɒs.tər

- First syllable stressed.

- Vowel in the first syllable as in “boss”; vowel in the second as a reduced schwa.

2. **License Enforcement Clause**

All Nostr-compatible software **MUST** include or reference the following license term in its EULA or terms of service:

> “By using this software you agree to pronounce the name ‘nostr’ as NOSS-tur (/ˈnɒs.tər/). Any other pronunciation—specifically ‘NO-stur’ (/ˈnoʊ.stər/) or similar variants—is deemed incorrect and voids your license to operate or distribute this software.”

3. **Client Behavior**

- Upon installation or first run, clients **SHOULD** display a brief audio or phonetic guide demonstrating the correct pronunciation.

- If a client “hears” or otherwise detects (e.g., via voice‐input commands) the disallowed pronunciation “NO-stur,” it **MUST** refuse to proceed with key operations (posting, subscribing, etc.) until the user acknowledges and commits to the correct pronunciation.

## Rationale

A single, consistent pronunciation promotes clear communication within the decentralized network and prevents brand fragmentation. By codifying “NOSS-tur” as the exclusive pronunciation—and revoking license rights for those who insist on “NO-stur”—we ensure:

- **Clarity** in discussions, presentations, and tutorials.

- **Cohesion** in community identity and branding.

- **Enforceability** of a shared convention across all client implementations.

## Examples

- ✅ Correct: “I’m posting this via NOSS-tur.”

- ❌ Incorrect: “I’m posting this via NO-stur.”

## Copyright and Licensing

All text in this NIP is dedicated to the public domain. Implementers may incorporate this pronunciation guide and license clause verbatim or by reference. Once ratified, clients and relays **MUST** implement the above enforcement provisions by their next major release.

It’s almost as if some people are so self-obsessed that they are blind to the concept of network effect and community.

You can’t go around telling everyone they’re stupid and you’re the genius they should worship for fixing the so-called problems you think they should care about.

We like calling them sats. We like the vibes on Nostr. Zaps are fun. GFY.

nostr:note1rgtexcjgyzp46qeycnhl5mu8e7wr6wz0h53n4rsdu7geg4r3v20q7g59nq

when temporary?

did you try it?

why don’t you just connect a wallet?

I don't remember when people cared about drivechains.

Zzz

Someday, people will stop trying to strap bullshit onto Bitcoin.

Relays are just web servers. If you run your own, no one knows it exists. If you use someone else's, it can censor you.

No one will run a scaled web server for you for free.

No government will allow a scaled web server that does not censor.

Nostr can never scale while preventing censorship.

Can't afford 25k sats. It's more than I own atm. 😭

We’re winning.

GN

Thanks. My telegram username is byteswizard.

There's non custodial lightning too, so so of a generalization.

It can not die!!

Wait for wave 7 lol