What's that local AI text to voice app I saw on nostr a while back? Anyone remember?

GM. I wish this was a quote from my book, but alas I am not that good of a writer

"chicken? do you have anything more... exotic?" "let me look in the back, sir, just a moment"

inflation

sometimes I just comb through the group chat meme archive. It's all gold 😂

I have finalized NIP-FF-3 as a potential successor to NIP-03. It's fully implementable now and @Fanfares will be implementing it shortly. NIP-03 allowed a nostr identity to attest to an event at a block height. NIP-FF-3 allows a nostr identity to attest to **content** at a block height, and minor edits to that content won't necessarily invalidate the OpenTimestamp proof. It's great for not only proving the time something was created, but also for proving originality and weeding out plagiarism at a protocol-level. You can REQ for events that have plagiarized yours via the X tag; obviously this depends on clients to opt in, but it's so easy that the primary reason not to is TREACHERY and RAPSCALLIONISM 😜 Check it out:

NostrHub — Build Nostr Together

NostrHub is where the developer community collaborates on building the Nostr protocol — discover, draft, and discuss NIPs together.

@Constant @npub1ej49...ndrm @fiatjaf

Computerosis. Kainz, 1993. Nearly 100 years before and 700 years after. #ifm

GM

absolutely unhinged crumpet jockeys View quoted note →

GM guys! It's Monday! Let's be nice to each other! 😅

I should mention that this enables plagiarism detection at protocol-level in nostr, which is great for people and clients who care about content authenticity! View quoted note →

GM. Here is the draft @Fanfares spec for edit-durable OpenTimestamp attestations for content, a successor to NIP-03:

NostrHub — Build Nostr Together

NostrHub is where the developer community collaborates on building the Nostr protocol — discover, draft, and discuss NIPs together.

an LLM that gradually uses more and more emdashes until the output is only emdashes

cooking the next NIP-03