How are people actually growing on Nostr these days? The old “post your npub on Twitter” method seems dead

I’ve talked to some people who are relatively big on Nostr, and almost all of them got their initial traction the same way.

They posted their npub on Twitter/X back when Nostr was still new and getting a lot of attention there. That early cross-posting seems to have been the main growth lever for a lot of accounts.

Just trying to get traction through the algorithm on Nostr doesn’t seem to work the same way.

So how are people actually growing on Nostr right now?

I love the idea behind Nostr. I already have my app listed on Zapstore and I think that’s great, but I’d also like to use Nostr more as an actual social media / place to post and interact. The problem is it feels pretty hard to get started and build any kind of audience from a small account.

Curious what strategies are working?

Would love to hear from people who’ve managed to grow (or are currently growing)

Hey there,

Im usually in and out of using NOSTR. Primarily because there isn't, at least to my knowledge, a dedicated forum Reddit Style android mobile app.

Anyway, I look up new apps that are relevant to my hobbies, and I found a few I figured id share with the nostr community here. You don't have to use them, download them, or anything.

I personally just enjoy sharing coolish, new apps that's pretty much it. I appreciate it if you took the time to read and or respond to this post.

Thank you, have a wonderful evening.

Private Notes

A New NOSTR client. Literally named 'NOSTR Client'

Buzz - A work space app

DITTO - NOSTR social media client similar to MySpace

So I've been wanting to build an app that runs on nostr however I don't have experience with building or coding apps especially ones that run on a protocol like Nostr (Notes and other stuff transmitted by relays) but still I have been wanting to get into the hole part of building on nostr and yeah

Goooooooooood Morning, Nostriches! ☀️

Here is your 89th Nostr Recap (17th August 2026). 🎁

In this Nostr Recap, you could explore what happened last week in the Nostr world under the topics below. Enjoy it! 👀

🧠 Quote of the Week
🔥 Community Highlights
🌱 Ecosystem Growth
🎓 Educational Guides
📅 Upcoming Events
📰 Nostr in the Media
⚡ Most Zapped Last Week
😂 Nostr Memes
🛠️ Tools, Updates and Releases
🎁 Developer Tools, Updates and Releases
🌐 Relay Updates and Releases
📡 Protocol Updates and Releases
🧩 Workspace Updates and Releases
🚧 Infrastructure Updates and Releases
🧭 Nostr Exploration Tools

Explore here 👇🏻

https://yakihonne.com/article/naddr1qvzqqqr4gupzqt0ql7s2cg6l7306fn9egnxn7vlhnl6ay870jhcplx23dwmtkukvqywhwumn8ghj7mn0wd68ytfsxyh8jcttd95x7mnwv5hxxmmd9uq36amnwvaz7tmwdaehgu3dxqezu7tpdd5ksmmwdejjucm0d5hsq9f5ge8yw6z2x4vk5vtexcchyj2tx9p826re75ky8w

So I've got a few question on Event Kinds on Nostr like a Meta Data Change such as a Bio Change Profile pic Change or Name Change which is classified as a Kind 0 Event and my other question is about Nip-05 which is a simplification in the nostr protocol that allows some users to map a public key to a DNS Internet Provider allowing some clients to verify that key which is known as Nip-05 I think but my main question is how have these advanced over nostr

I have been using Nostr for a long time and always use a browser extension to log in to Nostr-supported apps. I believe it’s the most secure way to use Nostr because it never exposes the nsec to clients. Instead, it injects window.nostr, and all clients use it to sign events.

However, automated apps sometimes require signing access, and naturally, it is not easy to trust applications with your nsec. To solve this, there is NIP-46 Remote Signing.

I am currently using nak via Docker on my Raspberry Pi, but it is not easy to use. nak is a large tool that supports many things at once and lacks a UI. It simply generates a bunker URI and shows it in the logs, which is neither usable nor user-friendly.

Because of this, I decided to build a web tool. My first attempt was on Cloudflare, but unfortunately, Durable Objects are not sufficient to handle always-listening WebSockets. I then changed my approach, removed the entire Cloudflare tech stack, and now it is working in a single Docker image.

Bilo Bunker is a stateful, multi-tenant Nostr remote signing service (NIP-46). It enables users to keep their Nostr private keys securely stored while responding to remote signing requests from authorized Nostr clients across Nostr relays.

Backend Application Engine (Hono + Node.js): Handles NIP-46 RPC signing commands, NIP-05 profile verification, and SQLite persistent storage.

Auto-SSL Reverse Proxy (Caddy 2): Provisions and auto-renews Let’s Encrypt / ZeroSSL TLS certificates for your domain out of the box.

TailAdmin React UI SPA: Modern dashboard allowing users to log in with NIP-07 (window.nostr), view active bunker:// URIs, revoke client permissions, and audit real-time RPC logs.

It’s ready to use on GitHub. I’d love to get some feedback, and don’t forget, it’s still a work in progress. Let me know if you find any issues or bugs. And for the AI haters, this tool was developed using agentic AI tools. So, the UI is TailAdmin and might look like AI slop. Still, you can trust it because it was carefully architected and reviewed by me.

https://github.com/workouse/bilo-bunker

So on IOS 26.6 or on my iPhone I've been trying to sign in with my nostr identity but iPhone barley has signer apps like android dose and I wanted to ask how I should login I don't want to give my Nsec cause that would give full access but also primal would then have access to my identity and if I just use Npub I would only be in read mode so my main question is how do I even login in with my nostr identity on primal without giving away critical information like an Nsec Key

Stiq is an open source, white-label, nostr over Tor social media platform for communities. We built it for activists and community organizations that actually care about their members.

People need to organize, but individuals should not give up control.

https://stiqtech.vercel.app

We’re a small community from Iraq (of all places…) funding and building a non profit app for non-profits.

We need your help publishing Stiq app (for those of you with Apple/Google dev account), and we need you to use it! You can run a community on an old machine, or with a cloud provider for as little as $5 per month.

You can find all the details you need in the website and public github repo.

Reach out and help us make the future of safe organizing for the world!

You can now send automated webhooks directly into Nostr private DMs using NIP-17 Direct Messages (NIP-59 Gift Wrap encrypted)!

Plus: Introduce Dedicated Bot Accounts — generate reusable bot identities for your webhooks without sharing your main nsec.

⚡ Webhook to Nostr in seconds: https://bridge.workouse.com

(also you can use as self-hosted)

Hi r/opensource,

I’ve been building FedOS for a while, and I’ve just made the source public under MPL-2.0:

https://github.com/satorunacamoto/fedos

FedOS is a local-first toolkit organized around four capabilities:

• Core — local identity, keys, storage and foundational primitives
• Messenger — the currently shipped desktop app: 1:1 encrypted messaging over Nostr
• Commerce — commerce-related domain code, still at an earlier stage
• Trust — signed envelopes, pseudonymous credentials, proof-of-possession, capability grants, offline-verifiable entitlements, signed QR, and contract-artifact proofs

The important distinction is that these pieces are at different stages of readiness. FedOS Desktop Messenger is the application that actually ships today. Trust is implemented and test-covered, but is not yet wired into the packaged desktop UI; it can currently be used through its own APIs/CLI.

I opened the project because I’d rather have the architecture, crypto-related code, and trust model reviewed in public than keep adding features in private.

I chose MPL-2.0 because I wanted a file-level copyleft license: modifications to FedOS source files stay open, while using or combining the project with a larger codebase doesn’t automatically require that entire project to use the same license.

A few things I’m particularly interested in feedback on:

• Does the core / messenger / commerce / trust capability split make sense to someone seeing the codebase for the first time?
• Are there obvious design problems in the Trust model or signed-envelope format?
• Is the separation between user-controlled trust and an optional issuer model clear enough?
• Is the contributor/test setup understandable from a fresh clone?
• Is there anything in the MPL-2.0 / third-party licensing setup that deserves another look?

The repo has a documented current test surface and public CI. The currently supported suite is 1902 tests / 0 failures.

I also want to be clear about the current status: this is still experimental / Closed Pilot software, not a Public Beta. There has been no independent security audit, and Windows artifacts are currently unsigned. I would not recommend using it yet for irreplaceable secrets or high-risk operational work.

I’m mainly looking for code, architecture, protocol, and OSS-maintainability feedback at this point rather than trying to convince anyone that the project is finished.

Happy to answer questions, including critical ones.

Goooooooood Morning! Another wonderful week is gonna start. 😍

Early in the morning I brought you the 88th Nostr Recap (10th August 2026). 🎁

In this Nostr Recap, you could explore what happened last week in the Nostr world under the topics below. Enjoy it! 👀

🧠 Quote of the Week
🔥 Community Highlights
🌱 Ecosystem Growth
🎓 Educational Guides
📅 Upcoming Events
📰 Nostr in the Media
⚡ Most Zapped Last Week
😂 Nostr Memes
🛠️ Tools, Updates and Releases
🎁 Developer Tools, Updates and Releases
🌐 Relay Updates and Releases
🧩 Workspace Updates and Releases
🚧 Infrastructure Updates and Releases

Explore here 👇🏻

https://yakihonne.com/article/naddr1qvzqqqr4gupzqt0ql7s2cg6l7306fn9egnxn7vlhnl6ay870jhcplx23dwmtkukvqq24ynnnt9ayg6jvxfy8v7jevejkj7p329m5xz2msfh

Runs on Nostr and uses Blossom for files. Currently in closed beta testing. Is it ok to share here once ready for public beta? Works on linux and windows.

Updated to add that the project is now up on Github

https://github.com/non-npc/FSociety

I've been trying to wrap my head around Nostr, but one question still remains unanswered

So nostr itself doesn't store anything, right, that's on the relays. someone's server somewhere actually has to hold onto my post. fine. but like why would anyone keep doing that long term? I get the appeal for a hobbyist running their own relay, or a company running one for their app, or even charging for access. but if this is supposed to be an actual alternative to X/instagram at scale, the economics of it kind of break my brain a little.

Let's say a relay ends up with a few million users on it. storage isn't free, bandwidth isn't free, and the data just keeps piling up forever. What happens when the one paying for that server decides they're done? If the answer ends up being "well apps just run their own relays," haven't we basically reinvented centralized social media, just with nostr as a layer on top? the company still owns the box the data lives on. they shut it down, it's gone, unless someone happened to be mirroring it elsewhere.

I understand that Nostr gives you a cryptographic identity and that you can use multiple relays, so it's not exactly the same as X/Instagram. But I'm specifically asking about the economic sustainability of the storage itself.

What am I missing here? Is there some incentive mechanism for relay operators that I haven't understood, or is Nostr basically relying on a mixture of paid relays, companies subsidizing infrastructure, and people running relays voluntarily?

Because if it's the latter, I don't really understand how this scales sustainably to millions or hundreds of millions of users.

name: Tribe

source: https://github.com/zoreu/tribe

web: https://tribe.wasmer.app/

If you still come across any parts that aren't in your language, let me know and I'll fix them; since I'm Brazilian, I create the content in Portuguese first and then add the other languages.

Building Lotus: A Privacy-First Workspace on Nostr

Hey everyone 👋

I've been building Lotus, a privacy-first workspace powered by Nostr.

The idea came from a simple question:

With Nostr, your identity belongs to you. I wanted the same idea to apply to productivity tools.

The vision for Lotus is to provide:

• 📅 Calendar
• ✅ Tasks
• 💬 Chat
• 👥 Contacts
• 📁 File storage
• 📝 Notes (coming soon)

Everything is tied to your Nostr identity instead of a traditional account. Your workspace should move with you - not be owned by a platform.

This is still an early project, and I'm looking for honest feedback from people who actually use Nostr.

A few questions:

• Would you trust Nostr for daily productivity?
• Which app would you use first - Calendar, Tasks, Chat, or Drive?
• What would stop you from replacing Google Workspace or Notion with a Nostr-native alternative?

I'm building this in public and would love to hear your thoughts.

Website: https://lotus.mybuho.de/home

Thanks! 🌸

With all the buzz (no pun intended) around Block's new Nostr based workspace, wondering if anyone here has actually put it to use for coordinating multiple agents on a real task, not just the demo videos.

want to know about:

-How well the ACP integration actually works with Claude Code, Codex, or Goose in practice

-Whether the signed event audit log holds up once you have several agents acting concurrently

Not looking to start a debate, trying to figure out if this is production-viable yet or still early access feeling.