MISSION IS THE SAME

HEAD DOWN

STAY HUMBLE

STACK SATS

SHITPOST ON NOSTR

ZAP FAT SATS

nostr:note1p6ncg2yrcw7gkp3zxvjkq7w8nd3pjx3f5w0fayx7demtlx3smzssu58qmv

GOOD MORNING NOSTR.

LIVE FREE. 🫡

Stone Ridge's annual comments on #Bitcoin are always worth paying attention to:

"Those who excel at delaying gratification, and mentally managing the associated uncertainty along the way, end up accumulating the vast majority of capital and enjoying the vast majority of health and prosperity. Low time preference is the most reliable source of life inequality. This means stay humble, stack sats, and HODL an uncomfortable amount of bitcoin for an uncomfortably long time. Low time preference is the most potent device ever invented for transferring wealth from the impatient to the patient. Be patient."

#Bitcoin is a game of delayed gratification.

My 2024 review and high-level report. Let's start with some stats for the nostr.build:

- 720 Million media requests served

- 650 TiB of bandwidth consumed

- 8 Million unique visitors

- 85% average cache hit rate

- Improved median CPU time per request from 200 down to 2 milliseconds per request

- 20 requests per second are served on average

- 99.994% uptime for the hosted media

- 98% uptime for the website and uploading servers

- 2.5K daily free uploads on average

Some improvements for the free uploads:

- Increased free upload size from 10MiB to 50MiB

- Increased image resolution from 1980px to 3840px

- Increased per server RAM from 1GiB to 4GiB

- Added full mirror of all uploaded media to the additional vendor (backup)

- Implemented moderation headers (can be used to hide NSFW content if desired)

Now some of the stats of my dev work for the nostr.build:

- 1,333 git commits

- 42 repositories with my contributions

- 10k+ lines of code written, or changed

Some features and completed projects:

- Rewritten nostr.build account page (AI, stats, nostr share, drag-n-drop, variaty of sizes, poster for video, etc.)

- Added AI Studio, onboarded multiple models from SD and Flux.

- Added media statistics

- Rewritten media serving front-end (dropping CPU utilization by 100x) and improving TTFB as well as cache hit rate (from 50%+ to 85%+ on average)

- Implemented variaty of the spam, and other illegal media upload prevention mechanisms (automated AI media scanner, PhotoDNA scanner, etc.)

- Implemented AI Moderation API that is shareable with other nostr media hosts (e.g., nostrcheck.me)

- Implemented upload of pdf, zip, etc., with full virus scanning.

- Various improvements to the PHP code, bug fixes and optimizations.

- Implemented e.nostr.build to allow easy embedding and sharing of the video/audio files for the account holders

- Referal links and account credits

- Onboarded more nostr clients for uploads (e.g., YakiHonne)

Some of the prototyping I've done for nostr.build:

- Semantic search of the media (ML based), multilingual

- Basic search for media using AI Vision

- Video transcoding using serverless and server-based setups

- Video transcoding to DASH/HLS (CMAF)

- Multi-party audio/video chat

Some of the in-flight projects that I'll have to complete in 2025:

- Seamless implementation of the Blossom protocol (70% done)

- Rewrite of the post-upload scanning to utilize workflows (50% done)

- New video upload and transcoding experience, HLS, DASH, VBR video/audio (10% done)

- New NoSQL based data-plane backend with the new API (50% done)

- Full rewrite of the Accounts page (5% done, blocked by new API and data-plane)

- Additional models for the AI Studio (90% done)

- (25% done)

I am sure I am forgetting a bunch, and this is only done from my memory.

Epic conditions skiing with family and friends in the BC interior today.

#bitcoin

GOOD MORNING NOSTR.

LIVE FREE. 🫡

Primal clients read from the caching service and write directly to the user’s relays. We chose a set of tradeoffs based on what we are trying to accomplish: best UX possible. We’ve been very transparent about it from Day 1. See my blog post from March 13, 2023 - the day we launched Primal. I still think that caching services are not only great for UX, but also a legitimate way to help scale Nostr once we hit millions of users. They could even improve censorship resistance, since anyone can stand them up and create more copies of Nostr events.

Having said all that, the Primal stack is evolving and becoming more capable on the client as well. One can imagine peer-to-peer transfers between clients that have client-side databases, like Primal for Android. I think Nostr will have it all: relays, indexers, caching services, client p2p transfers. It will be very hard to stop.

Claiming that there is only one way to properly build Nostr clients and that everyone must choose exactly the same set of tradeoffs is silly. For example, gossip/outbox purists might take issue with how Damus works.

Everything we build at Primal is open sourced under the most permissive MIT license. I believe we offer the only open source indexer for Nostr (someone please correct me if I’m wrong). Anyone can stand up and run their own caching instance. Other projects have done so in the past. Primal users hold their keys and can move to another client at any time if they don’t like how our product evolves.

On a personal note Will, you constantly fud Primal. You tried to cancel us before, joining semisol’s cEnSoRsHiP nonsense campaign. Your latest initiative - trying to impose rules on what can be called a Nostr client - is also an attempt at cancelling. I don’t know what to make of it because you are always very friendly in person. We spent a considerable amount of time together, and you never raised these issues with me face-to-face. Why not? On the contrary, you always seem to have kind words for Primal when we talk.

I’ve never said a bad word about Damus or any other project. I want to be on good terms with all Nostr builders, but you are making it hard with posts like this.