#bitcoin is the best accounting system.. #gold is worst 😜

What if every website had a #zap account and #AI sent just 21 SATs for researching these incredible resources !

The big idea .. View quoted note →

I pity these reporters .. getting weaved all the time ..hahah View quoted note →

... I bought one stock of Strategy and one of Block .. fix the store of value thing and means of payments .. do it both ..why not ..

Sending newsletters is like shooting in a void - no wait ..shouting in my junk folder View quoted note →

# DAM : Distributed attention model Everybody wants your attention. Netflix, TikTok, your mom, even that squirrel outside the window. But attention is limited, so how do creators measure it? Enter the Distributed Attention Model—or as the cool kids call it, DAM. DAM says: It doesn’t matter if 50 people watch one hour, or 5,000 people watch 0.1 hours… the total attention is the same. It’s all just attention math. Fifty hours of watch time either way. Big-budget movies chase deep attention—they want you strapped to a chair, popcorn in hand, emotionally invested for two hours. Shorts and memes, on the other hand, chase wide attention—they want 5,000 brains for a few distracted seconds while you’re waiting for your noodles to cook. The genius of DAM is that both paths lead to the same DAM total. Depth or breadth, it’s all watch time in the end. The only question is: do you want fewer souls glued to your masterpiece, or a million thumbs double-tapping your nonsense? So the next time someone asks why you’re spending your weekend making silly 15-second TikToks, you can shrug and say: “Relax. It’s just the DAM model at work

If there is an AI God orchestrating its evolution then it must design a wormhole for the humans to get past this transition.. quickly 😜

#bit oin is searching 58 K not cuz of #cryptoWinter but for #AIwinter

#Primal ..looks like there is a problem in markdown rendering .. #Amethyst is rendering fine

Hey #nostr Devs .. anyone wants to vibe code this .. I can help in testing Cheers View quoted note →

# Nostr for Science – Single page app (SPA) Publishing Platform Specification ## Problem - most of science papers can be and ar presented as interactive single page apps but there is no platform ( like substack ) for hosting SPAs .. which means researchers end up creating their own websites on GitHub which lack features like zaps or comments or social discovery. ## 1. Overview “Nostr for Science” is a decentralized platform for publishing **interactive single-page applications (SPAs)** as research papers. It leverages **Nostr** for identity, discovery, and commenting, and **Blossom** for hosting SPA bundles. The platform hides technical complexity from creators while ensuring all papers are discoverable across the Nostr ecosystem. --- ## 2. Goals - Provide a simple SPA publishing workflow for creators with no knowledge of protocols. - Offer a discovery hub with tile-based layout organized by research categories. - Enable readers to save/pin papers and interact via comments and zaps. - Ensure interoperability: all publications are visible on any Nostr client with a link to the platform. --- ## 3. User Roles & Features ### 3.1 Creators - **Identity**: Generate a Nostr ID in-app (public/private keypair). - **SPA Upload**: Drag-and-drop SPA bundle (`index.html`, `.js`, `.css`, assets). - **Metadata Form**: Title, abstract, authors (optionally ORCID), category, keywords, PDF/DOI link. - **Publishing**: Click “Publish” → client uploads to Blossom → publishes a signed Nostr event linking the SPA. - **Preview**: Optionally preview SPA inline before publishing. ### 3.2 Readers - **Discovery Hub**: Tile-based feed displaying papers with preview image, title, abstract, author. - **Categories**: - Physics - Mathematics - Computer Science / AI - Biology & Medicine - Social Sciences - Economics & Finance - Engineering - Interdisciplinary / Other - **Dashboard / Personal Space**: - Pinned papers (bookmarks saved by Nostr key). - Commenting via Nostr events (`kind: 1`). - Zapping via LNURL / NIP-57. - **Profile**: Shows user comments, zaps, pinned papers. ### 3.3 Nostr Ecosystem Interoperability - Published SPA metadata is a standard Nostr event (`kind: 30100`) with Blossom link. - Papers appear on all Nostr clients as a clickable link. - Client footer: “Open this interactive paper in Nostr for Science → [link]”. --- ## 4. Workflows ### 4.1 Publishing Flow 1. Click **New Publication**. 2. Fill metadata form. 3. Drag-and-drop SPA bundle. 4. Client uploads SPA to Blossom node (gets hash). 5. Create signed Nostr event with metadata + Blossom link. 6. Publish event to relays. 7. Paper appears in Discovery feed. ### 4.2 Discovery Flow 1. Open client → grid of latest papers. 2. Filter by category/keywords. 3. Click tile → SPA loads inline (iframe) or new tab. 4. Interact: comment, zap, pin. ### 4.3 Reader Dashboard Flow 1. Login with Nostr key. 2. View pinned papers, comments, and zaps. 3. Organize reading list; optionally share as Nostr event. --- ## 5. MVP Feature Set - [x] Nostr ID creation & login. - [x] SPA upload & Blossom storage (abstracted). - [x] Metadata form + publishing as Nostr event. - [x] Discovery hub with categories & search. - [x] Personal dashboard with pinned papers. - [x] Commenting & zapping. - [x] SPA embedding inline. - [x] Papers visible on all Nostr clients with platform link. --- ## 6. Stretch / Future Features - Advanced semantic search by abstract/content. - Academic integrations: ORCID, DOIs, BibTeX export. - Author analytics: views, zaps, shares. - Institutional / lab hubs. - Private / preprint sharing with access control. - Multi-node Blossom mirroring for resilience. --- ## 7. Technical Stack - **Frontend**: React / Next.js + Tailwind CSS. - **State / Nostr**: nostr-tools, nostr-react. - **Storage**: Blossom nodes + gateway abstraction. - **Payments**: LNURL / NIP-57 for zaps. - **Identity**: Browser key management, optional import from extensions (Alby/NostrSigner). --- ## 8. Blossom Nodes (Initial Setup) | Node | Role | Strengths | Limitations | |------|------|-----------|-------------| | `blossom.nostr.build` | Primary | Well-documented; supports BUDs; 50MB free uploads | Paid plan needed for large apps; some file types restricted | | `blossom.primal.net` | Mirror / Alternative | Integrated with Primal; metadata stripping; mirrors | Shared resources; performance/storage may vary | | `strfry.nostr.lighting` | Fallback | Basic endpoints: `GET`, `PUT /upload`, `GET /list/<pubkey>` | Unknown quotas; less documented; test before primary use | | Custom / Self-hosted | Optional | Full control; ensure SPAs reliably hosted | Requires infra and maintenance | ### 8.1 Blossom Node Specs - **Endpoints**: - `PUT /upload` (signed Nostr event required) - `GET /<hash>` - `HEAD /<hash>` - `GET /list/<pubkey>` - `PUT /mirror` (optional) - **Supported File Types**: `.html, .js, .css, .svg, .png, .jpg, .gif, .wasm, .woff, .woff2, .ttf, .otf, .zip` - **File Size Limit**: 50 MB per upload (adjustable per node) - **Mirroring**: Optional, automatic if configured - **Authentication**: Write actions require signed Nostr events; read is public - **Quotas / Rate Limiting**: Enforce per-user limits; throttle upload rates --- ## 9. Metadata Event Format (Nostr Event) ```json { "kind": 30100, "content": "An interactive visualization of quantum states.", "tags": [ ["d", "quantum-spa-2025"], ["title", "Quantum Entanglement Explorer"], ["abstract", "Live simulation accompanying my paper on entanglement."], ["app", "blossom://bafkreigh2akiscaildc6indexhtml"], ["author", "npub1..."], ["link", "doi:10.xxxx/xxxx"] ], "pubkey": "npub1...", "created_at": 1699999999, "sig": "..." }

When number goes down , I start looking at my micrograms of #gold reserves 😭😭... Time to dig in and #stackSats View quoted note →

58 K gang is feeling excited again #AIWinter

Is there any company other than nVidia who made money in ( net profit ) on #AI spend ?

Why does #bitcoin network waits for ten minutes to finalize a block ..what is the rationale ?.