I feel like I'm betraying Nostr by using other social media platforms 😔

DiVine I downloaded it from Zapstore. It’s actually good and has users. Bringing TikTok features here could be great. There’s a need for a TikTok alternative on Nostr

Yesterday, 20,728 people entered Nostr.

There are 40 million people on Bluesky, and it’s not perfect. If Nostr has 3 million users, this user experience is actually normal. It would be great if there were 100 million users.

The idea of Zapstore is brilliant. I downloaded it on my phone.

All of Nostr’s apps are terribly designed to get any interaction. I swear, I have to force myself to click the buttons. It's like they were designed not to get any interaction.

As crypto grows, it becomes more vulnerable to attacks. That's why we need to grow a crypto-native platform like Nostr. But what should we do? How will we grow it?

JUST IN: OpenAI co-founder Andrej Karpathy joins Anthropic

Gemini 3.5 Flash has landed #9 for Text and Code Arena: Frontend. Code Arena: Frontend evaluates models on agentic frontend coding tasks from real users building apps and websites (HTML and React). Scoring 1507, this is a significant +70 point improvement over Gemini-3 Flash. Sub-category highlights: - #7 Content Creation Tools - #8 Gaming - #8 Consumer Product - #9 Data & Analytics - #10 Reference-Based Design In Text Arena: #9 overall. Gemini 3.5 Flash also moves the price–performance frontier as the new top Arena score in its price tier.

OnlyFans is the most revenue-efficient company in the world 🚨 $NVDA needs to step it up 😂

BREAKING: The US 30Y Note Yield rises to 5.18%, its highest level since July 2007.

Notifications are arriving but not showing up. I'm posting but the button isn't working. Even if people came, they wouldn't use Nostr. I'm serious, who's going to fix these problems?

JUST IN: 🇯🇵 Japan officially recognizes foreign-issued crypto stablecoins as legal electronic payment methods starting June 1

On Nostr, I would prefer to see one perfectly functioning TikTok, one Instagram, and one Twitter clone instead of 10 different Twitters.

The Core Thesis Every existing platform has the same economic model: the platform captures value, creators get a small cut, users get nothing. Nostr + Lightning inverts this. Value flows directly between participants. The platform takes nothing because there is no platform — just protocol. This is the killer differentiator. Not the decentralization. Not the censorship resistance. The money. Rethinking the Economic Layer Zaps are just the beginning Most Nostr apps treat zaps as a tip feature. That's thinking too small. The full economic surface looks like this: Per-video zaps — direct payment to creator per view or interaction, already exists in Nostr Split zaps (NIP-75) — a single zap automatically splits between creator, collaborator, and curator. A video with a featured musician splits revenue between the videographer and the musician automatically at the protocol level Zap goals (NIP-75) — crowdfunding targets embedded in content. A creator posts a video with a funding goal attached; viewers zap toward it Value4Value streaming — while a video plays, micropayments stream automatically per second watched (WebLN + LNURL). The longer you watch, the more the creator earns. Watch time becomes a direct payment signal, not just an algorithm input Curators earn too — whoever surfaces a video (shares, reposts) can receive a percentage of downstream zaps. This incentivizes quality curation over engagement farming

https://stats.andotherstuff.org/ Nostr Stats is broken and of course nobody noticed. 🙄

Nostr is evolving, but adaptation is slow. This is because you need to do extremely radical things to suddenly change the dynamics of social media. TikTok and Instagram have excellent algorithms.

I opened a BitChat . I'm in #sw location.

Nostr's Biggest Problem Isn't Keys. It's Speed. Everyone talks about the learning curve — seed phrases, key management, finding clients. But once you're past that, a quieter problem hits you immediately: everything feels slow. Posting lags. Notifications arrive late or out of order. Feeds refresh sluggishly. If you're coming from Twitter or any mainstream social app, the friction is hard to ignore. This isn't a bug. It's architecture. Why Nostr Is Slow by Design On Twitter, when you post something, it goes to one place — a massive, optimized server that processes it instantly and pushes it to your followers. There's a single source of truth, and it's engineered for speed at scale. Nostr has no such server. When you post, your client pushes your event to every relay you're connected to, one by one, over WebSocket connections. When you check notifications, your client opens concurrent streams to multiple relays simultaneously, pulling events and deduplicating them in real time. Every action that takes one network round-trip on Twitter takes N round-trips on Nostr. Add to this the fact that most major relays are located in the US or Western Europe. If you're connecting from Turkey, Southeast Asia, or anywhere outside those hubs, you're adding geographic latency on top of the architectural overhead. There's no CDN layer, no edge caching, no pre-computed feed waiting for you. The slowness is the price of censorship resistance. Your data lives on relays you choose, not on a platform that can delete you. That's a real and meaningful tradeoff — but it needs to be named honestly, especially when we're trying to bring regular users onto the protocol. Can It Be Fixed? Yes. And the tools already exist. The first piece is the Outbox Model (NIP-65). Instead of every client blasting events to every relay and hoping for the best, users publish which relays they write to. Clients then fetch from the right relay for each person, rather than polling everything everywhere. This alone cuts redundant traffic significantly and is probably the single most impactful improvement available today. Adoption is still incomplete, but it's growing. The second piece is indexer and caching layers. This is where it gets philosophically interesting. A server that ingests Nostr events, indexes them, and serves pre-built feeds via API can make the experience feel as fast as any centralized app. Primal does exactly this. It breaks the pure relay model, but here's the key insight: your data remains portable. Even if Primal's cache disappears tomorrow, your events still live on your relays and any other client can read them. The indexer optimizes reads — it doesn't own your identity or your social graph. This is the distinction that matters: portability is not the same as decentralization at runtime. A fast Nostr client backed by a caching server is still fundamentally different from Twitter, because you can leave. You can take your follows, your notes, your identity — and move to any other client. That's impossible on any centralized platform. What Regular Users Actually Need Regular users will not wait. They have no patience for relay philosophy, and they shouldn't need to. If the experience is slower than what they're used to, they leave. This is the largest real adoption blocker Nostr faces right now — not keys, not complexity, but perceived performance. The path forward is clear even if it makes some people uncomfortable: Broader NIP-65 adoption so clients fetch smarter, not harder More geographically distributed relay infrastructure — there are almost no relays serving the Middle East, Africa, or Southeast Asia Clients that use intelligent relay selection and connection pooling Indexer layers that make feeds feel instant, without compromising data portability Nostr doesn't have to choose between speed and sovereignty. It can have both — but only if the ecosystem builds the middle layer that bridges them. The protocol is sound. The values are right. The infrastructure just needs to catch up.

In Primal, I receive notifications and I have to wait at least 2 minutes to see them.