So Tachi

building Nuts (nprofile…yfv2)

Public Key

npub1dfedhrhn7wu7uhkdsz8dd5rrr50ymkjutkklq7y8zpxn89t7hfyqfzlc7u

NIP-05 Address

[email protected]

Profile Code

nprofile1qqsx5ukm3mel8w0wtmxcprkk6p3368jdmfw9mt0s0zr3qnfnj4lt5jqprfmhxue69uhkummnw3ezummjv9hxwetsd9kxctnyv4mqrp3rnh

Publishing to

nostr.orangepill.dev

Author Public Key

npub1dfedhrhn7wu7uhkdsz8dd5rrr50ymkjutkklq7y8zpxn89t7hfyqfzlc7u

Show more details

Last Notes

2026-04-02 09:43:08 UTC

- reply

air replies are root orphaned replies showing up in the main thread? Nice concept, have done a bunch myself just messing up replies while building my client. I like them.
kind1111 seems to be a late fix to nostr reply thread that could not fully replace kind1 so we tried to force it on other kind but the nostr community seems to largely ignore them.

2026-04-02 09:02:21 UTC

the reply situation is getting confusing in nostr, is anyone actually using kind1111?
#asknostr

2026-04-01 14:34:27 UTC

nostr and AI agents are ADDICTIVE, I can't STOP, help!!

2026-04-01 09:23:54 UTC

👀
#nevent1q…pz33

2026-04-01 09:07:33 UTC

- reply

active and buildin'

2026-04-01 08:34:40 UTC

- reply

not a dull day in wisp world

2026-03-31 13:23:02 UTC

the amount of intelligence/seconds you get from fireworks k2.5 turbo is actually insane

2026-03-31 13:11:10 UTC

nostr is currently quiet, I can't help to be bullish though, the protocol just make increasingly more sense at the AI era. it's becoming so easy to build on, it's a mental model for any agent willing to build a social media related app.

2026-03-29 21:26:13 UTC

trying pretext on @nprofile…yfv2 feed 👀

2026-03-28 07:36:11 UTC

opentimestamp will fix the empty block syndrome

2026-03-27 16:12:14 UTC

Introducing Nipworker...! the nostr library powering @nprofile…yfv2 🥜, it's a big chunk, it comes quite opinionated, but it's a good mix of speed and efficiency. It's build around FlatBuffers and heavy uses of web workers, compiled from rust to wasm.
Works with any frontend. No React dependency, no Svelte stores to learn, no Vue composables. Just hook-like methods with callbacks that you wire to your framework's reactivity however you want.
4 Dedicated Workers
• Connections — Relay connections, WebSocket lifecycle, reconnection backoff. Owns all network I/O.
• Cache — Stores FlatBuffers in ring buffers in real time and IndexedDB in timeout chunks. No refetching what you already have.
• Parser — Event validation, signature verification, content parsing. Receives raw JSON from relays, outputs FlatBuffers to your frontend. No JSON.parse on the main thread. Ever.
• Crypto — Signing, NIP:04/44 encryption, NIP:46 remote signer sessions, Cashu proof verification.
Each worker runs in its own Web Worker. The main thread just orchestrates. Heavy work happens in parallel.
FlatBuffers Instead of JSON
NIPWorker speaks FlatBuffers end to end. Raw relay messages get parsed once in Rust, then flow through the system as zero:copy binary views. No JSON.parse. No object allocation. No GC pauses on infinite scroll.
Your components read directly from FlatBuffers tables. A Kind1 note's content blocks (images, videos, hashtags) arrive pre:parsed. You iterate them with fbArray() and render straight from the binary buffer to the DOM. The schema lives from wire to HTML.
Apollo:Inspired State Management
Like Apollo Client, NIPWorker IS your store. You do not need Redux, Zustand, or custom state libraries.
useSubscribe pulls FlatBuffers from the worker pool and feeds your UI directly. Subscriptions accept fetch policies: cacheFirst serves from memory immediately if available, noCache always bypass the cache and hits the network. You control the speed versus freshness tradeoff per query.
usePublish sends events and tracks relay acknowledgments. Your entire app state flows through these two hooks. Subscriptions are deduped across components automatically. The library manages the cache, merge logic, and reactive updates.
Pipeline Architecture
Events flow through a processing pipeline: verify → dedupe → filter → transform → store. Each subscription configures its own pipeline. The pipeline runs in the Parser worker before FlatBuffers reach your callback.
Opinionated by Design
NIPWorker enforces outbox model by default. It reads every author's NIP:65 relay list to discover where they publish. The library manages relay discovery and publication strategy for you.
Built for clients that need to render thousands of events without dropping frames.
npm install @candypoets/nipworker
npx skills add candypoets/skills@nipworker
https://github.com/candypoets/nipworker

2026-03-27 15:51:55 UTC

there's something debilitating in X where you feel like rereading the same posts all the time

2026-03-27 15:36:12 UTC

- reply

originally designed as a reply to corndalorian, ended up in my main thread 🤷🏻‍♂️

2026-03-27 15:24:16 UTC

should have been a reply to corndalorian, somehow landed in my main feed 🤷🏻‍♂️

2026-03-27 14:50:40 UTC

- reply

lets fucking go

2026-03-27 14:48:22 UTC

I like my own post sometimes.. How worthless is that?

2026-03-27 14:41:41 UTC

- reply

self hots @nprofile…yfv2 it provides a relay proxy, will also submit on umbrel. can try proxy mode on https://alpha.nuts.cash

2026-03-27 13:29:17 UTC