Substr

Official Substr Account - The community layer of Nostr. Your space, your people

Public Key

npub122wdrxx9gaf6reg52nzcd4m5u66qx85jm3c9gwgrsukkcelm0u2q0nfgdf

Profile Code

nprofile1qqs998x3nrz5w5apu529f3vx6a6wddqrr6fdcuz58ypcwttvvlah79qpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgkwaehxw309ashgmrpwvhxummnw3ezumrpdejqzrthwden5te0dehhxtnvdakqz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpzpmhxue69uhkummnw3ezuamfdejszk0cp9

Publishing to

Author Public Key

npub122wdrxx9gaf6reg52nzcd4m5u66qx85jm3c9gwgrsukkcelm0u2q0nfgdf

Show more details

Last Notes

2026-05-18 17:14:48 UTC

- reply

I do think there needs to be some form of control/moderation. I’m still very open to ideas on what the best practical implementation looks like though.
But as an example: you’ve posted quite a few AI-generated images of women, and if that happens inside a Substr where that kind of content isn’t wanted, there needs to be some way to deal with that.
Those images are still relatively harmless (aside from the “12 years old” one 👀), but if people start posting genuinely gore or disturbing content, communities need the ability to react to that immediately in some form.

2026-05-18 17:06:49 UTC

- reply

The actual posts and interactions inside Substr are still Nostr events on relays, so the content itself is portable and interoperable. That also means your posts can still reach far beyond just Substr itself, instead of being trapped inside a closed platform or isolated community silo. That wider reach and interoperability is a pretty important part of why I chose this hybrid approach in the first place.
But yes, the mapping layer of /s/name currently lives inside Substr’s own infrastructure.
As for why I’m not fully using the current community NIPs (like NIP-72/29) yet:
I experimented with them quite a bit, but right now they still have a lot of rough edges for the type of UX and moderation flow I want to build:
weak discovery
inconsistent relay support
fragmented moderation behavior
poor UX for mainstream users
difficulty building structured feeds/community identity
limited flexibility around permissions, layouts, ranking, and management
A big goal of Substr is making communities feel understandable and approachable for normal users, not just protocol-native users.
So the current approach is more of a pragmatic hybrid:
communities/substrs live in a DB layer for now
content inside them stays Nostr-native
users still own their identities/accounts/content
posts still exist outside Substr
interoperability is preserved where possible.
Long term I’d absolutely like to move toward more decentralized community models once the ecosystem and standards mature more

2026-05-18 16:52:16 UTC

- reply

I get that concern, and honestly I think it depends on what layer you consider “centralized.”
The actual posts, replies, reposts, zaps, etc. inside Substr are still regular Nostr events that live on relays and work outside the app. We intentionally avoided building some closed backend feed where content only exists inside Substr.
The “substr” itself is more like a structured community layer on top — mainly for organization, discovery, moderation, rules, layout, filtering, and context. Similar to how a subreddit gives context to posts, except the underlying content is still Nostr-native.
A big part of the design is actually user-created communities. The whole idea behind Substr is helping people find like-minded groups more easily, or allowing creators/projects/shows/interests to have their own dedicated place instead of everything fighting for attention in one endless global feed.
A good example:
- a podcast could have its own substr where episodes, clips, discussions, livestreams, and community posts live together
- an open-source project could have a focused place for updates, feedback, and support
- a niche interest group could have a calmer feed without unrelated noise constantly mixing in
Once you move toward actual community spaces, some form of moderation or curation naturally becomes part of the equation. Otherwise every space eventually turns into “just another hashtag stream” with spam, collisions, and no real continuity or identity around the group.
That said, I’m definitely not claiming the current model is the final answer. I’m very open to experimenting with different moderation structures over time:
- shared moderators - already working
- community voting - already working
- mirror views
- relay-based filtering
- optional open/unmoderated modes
- more collaborative ownership models
I just think there’s a balance between pure protocol idealism and building something that feels usable and understandable for real communities and creators.
So for me it’s less about re-centralizing Nostr, and more about experimenting with a community layer on top of open protocols while keeping the underlying content portable and interoperable.

2026-05-05 12:39:42 UTC

Just a Good VS Evil mobile wallpaper
https://image.nostr.build/0a6850948f3f4f3c8eaf37bee9ccb0a4e973781a133ba0d4aeec69e46d734f64.png

2026-04-22 18:41:10 UTC

Substr Update - Shared Nostr Events, Community Space Cards, Live Stream Polish
https://image.nostr.build/0977375fe850dafe0acee241414e1d2de5f0e3361dd7cd220c638c5f3a66c21a.jpg
Quick build update from Substr. I’ve shipped a lot of product polish recently, but two bigger areas deserve a deeper explanation: Shared Nostr Events and community-level customization.
**Shared Nostr Event posts **
Substr is community-scoped by design. I intentionally do not load the full global Nostr firehose into every /s/.
That keeps communities focused, but it also creates a practical issue: people often want to bring an existing Nostr post into a community thread.
So I added Share Nostr Event posting.
What this does:
- You can post a Nostr event reference directly into a substr.
- The shared card resolves richer content (mentions, links, media, video) instead of just showing raw IDs/URLs.
- Engagement actions (likes, zaps, replies) are wired toward the original event target, so interaction stays meaningful across clients.
- I improved repost compatibility so shared behavior is clearer outside Substr too.
Why I did it this way:
- In a global client, “repost” can assume broad feed context.
- In a community-scoped client, I need a wrapper that anchors the post inside a specific space while still respecting the original event.
- This is my bridge between “community context” and “cross-client interoperability.”
**Community space cards (making each /s/ more ownable)
**
I also expanded moderator controls for the right-side “space” layer with dedicated cards:
- Message card (editable title/body)
- Social links card (compact icon-first links)
- Useful links card (curated title + URL entries)
This gives each community a stronger identity without turning setup into a heavy CMS flow.
I’m exploring how to make communities even more distinct and self-owned:
- stronger space identity patterns,
- clearer utility cards,
- better “what this community is for” signaling,
- and more creator/show/community-specific layouts over time.
Other smaller fixes
- Relay UX refinement: compact cards, status dots, clearer relay info.
- Signer/login flow cleanup with better QR/copy/manual paths.
- Mobile-first signer onboarding improvements (wizard flow, clearer steps).
- /s/ sharing improved for PWA (native share first, copy fallback).
- Atmospheric background behavior fixed (viewport-anchored, no stretch on long pages).
- Rich-text mention parsing improved (nostr:nprofile... support, including leading emoji cases).
- Clickable identity and /s/... badges expanded across more surfaces.
- Stream + chat improvements: better layout, publishing/read behavior, diagnostics, and interaction polish.
Cheers and on to the next one!

2026-04-22 10:08:19 UTC

When you want to share an event, meetup, hackathon, conference, tour, or anything similar, you can now post it in the Event Substr created by @nprofile…cl8m
https://substr.network/s/events
https://npub122wdrxx9gaf6reg52nzcd4m5u66qx85jm3c9gwgrsukkcelm0u2q0nfgdf.blossom.band/32a573c3b9fecf6ff7acd09919a27ba3efb33d56d15e7ee5c45212b06d4b2b6c.jpg

2026-04-17 05:04:42 UTC

- reply

It should be, I tested myself on multiple devices in multiple browsers. Also on a few ssl testers and turned all back with a legit SSL certificate.

2026-04-15 21:18:52 UTC

- reply

Yeah interesting, already looked at it if it could help against bots.

2026-04-15 19:51:24 UTC

- reply

Wondering how ✍️

2026-04-15 17:22:56 UTC

- reply

Welcome to the club ✌️

2026-04-15 11:06:43 UTC

Got some open-source art, illustrations or other media you wanna share?
Or you hunting for some?
Check out the Open Source Art Substr
https://npub122wdrxx9gaf6reg52nzcd4m5u66qx85jm3c9gwgrsukkcelm0u2q0nfgdf.blossom.band/6a9586ebbeac662a66af96ab16a4486db78df1f3742a3b7d291eeb1297e51bee.jpg
https://substr.network/s/open-source-art

2026-04-15 07:09:37 UTC

Stay Humble
https://npub122wdrxx9gaf6reg52nzcd4m5u66qx85jm3c9gwgrsukkcelm0u2q0nfgdf.blossom.band/6e2bbf0e1764e0b304dec3128cfae94b5e35f3126dd6df59f0bde3746c55c9e3.jpg

2026-04-14 20:25:24 UTC

- reply

Why not 2 different ones so you can listen too 2 pods at the same time, are you then still an half listener?

2026-04-14 15:55:20 UTC

- reply

Do it 🤷‍♂️

2026-04-14 07:00:47 UTC

GM ✌️ https://npub122wdrxx9gaf6reg52nzcd4m5u66qx85jm3c9gwgrsukkcelm0u2q0nfgdf.blossom.band/f458a00f475116a3a183780b4149249b638e18ad682204ebee3dd94b73bef644.jpg

2026-04-13 17:01:13 UTC

- reply

We need to top up the 40HPW Substr
https://substr.network/s/40hpw

2026-04-13 13:42:57 UTC

We just shipped the first step towards livestreams on Substr.network
https://blossom.yakihonne.com/46bfda79a2d237c09b846736b09acf3209aa657f3f10654437d8bedc49e5d9f4.jpeg
Moderators can now add a live stream
by pasting a Nostr naddr.
Stream + chat, directly inside the Substr.
the foundation is there, but should build further on feedback.

2026-04-13 10:49:38 UTC

- reply

No, no native app at the moment. Only PWA

2026-04-13 08:49:42 UTC

From brainfart to execution. We’re almost there... 😄
https://blossom.yakihonne.com/b0bb18a99bb6c602d106b5de87e993f284d053b49c2df0682123a496db304a51.jpeg
Soon all you’ll need to do is paste your NADDR and your stream will be visible on Substr, including chat. Just needs some little tweaks and polish.
#nevent1q…ydrw

2026-04-13 04:41:44 UTC

- reply

GM ✌️

2026-04-12 08:48:28 UTC

You can manage your own relays in Substr.network. just head over to settings, relays and add the relays you want, same for DM 's
https://blossom.yakihonne.com/2dbf6c2eaa1b712e8ca590643c4532da6790bb4745c8dbd43a59f1aa83e0813c.jpeg

2026-04-12 05:27:02 UTC

GM
still building. still learning.
https://blossom.yakihonne.com/f458a00f475116a3a183780b4149249b638e18ad682204ebee3dd94b73bef644.jpeg

2026-04-11 18:50:43 UTC

- reply

Welcome! As you can see, I’m still busy polishing things and adding new features. If you run into anything or have ideas, feel free to let me know!

2026-04-11 12:33:56 UTC

- reply

GM 🫪

2026-04-11 08:03:43 UTC

- reply

2026-04-11 07:54:28 UTC

Login Signer Flow Update
https://image.nostr.build/2015ca12c4b0f6ed45c6af10c5a93f958decf4e89e01393816e305d6127f152e.jpg
Spent some time tightening up the signer flow in Substr.
We cleaned up the connect modal, made the remote signer option easier to understand, and added a few fallback paths for mobile when opening a signer app doesn’t work right away.
You can now connect through the app directly, use a QR code, copy a Nostr Connect link, or fall back to a manual bunker setup.

2026-04-10 16:04:32 UTC

Todays theme is Brutalism 😎
https://blossom.yakihonne.com/dae84a73300b4d296f82f6712c530201f08ac7ee4abe9e2bf7911f103dc77732.jpeg

2026-04-09 12:12:16 UTC

Video upload ✅ Livestream next?
https://image.nostr.build/91efaaa758a584b4b8152495ce26e3d2eafbc6278fbbc13a1058ececa25e74a2.jpg
Added video upload support on substr.network. Makes me think, Content creators can already run their own Substr.
Should we take it one step further and add livestreaming? Imagine going live inside your own Substr community —
chat, comments, zaps… all in one place

2026-04-09 06:52:46 UTC

GM
https://npub122wdrxx9gaf6reg52nzcd4m5u66qx85jm3c9gwgrsukkcelm0u2q0nfgdf.blossom.band/37258d6e2f2c46e8be396433b537a788f425c01cb567ed416cb8b6cbeeb99e4b.jpg

2026-04-08 18:26:37 UTC

- reply

Looks great 🔥

2026-04-08 10:42:06 UTC

Should we add another post type? If so, which one? https://npub122wdrxx9gaf6reg52nzcd4m5u66qx85jm3c9gwgrsukkcelm0u2q0nfgdf.blossom.band/27f1b021660777d197133670268ff4b1b89c6e3ca752b0349dc7de45ae051cc6.jpg

2026-04-08 05:14:09 UTC

GM Nostr 🤘✌️ https://npub122wdrxx9gaf6reg52nzcd4m5u66qx85jm3c9gwgrsukkcelm0u2q0nfgdf.blossom.band/bdbe46c2ea52682101bf0cd831c5d9af3dadebe34f27861ed7e1636f7aef3dda.jp

2026-04-07 19:00:22 UTC

Add mentions or keep it clean?
https://image.nostr.build/4cde0e374536ff03b877eb72e122186a5a963cf6b3572d67825eba67406520be.jpg
I’m considering adding an @mention feature in posts and comments/replies.
Not sure yet if it improves interaction or just adds noise. Curious how others feel about it.

2026-04-07 16:10:23 UTC

Substr, For more logical feeds https://npub122wdrxx9gaf6reg52nzcd4m5u66qx85jm3c9gwgrsukkcelm0u2q0nfgdf.blossom.band/792d47652315be5659d7930fb3c07a9276f22a8e156e70ef02f44ca78de0c554.jpg

2026-04-06 20:27:12 UTC

Goal for the coming days!
https://image.nostr.build/faa7db9dcf15fe4e77012c350d66fd3f48a1a487a4c21e5f87fc5cbcd717de24.jpg
The goal in the coming days is to improve media uploads on Substr.
Right now we’re using nostr.build with NIP-98, which works well as a starting point.
Next step is moving towards a Blossom-based setup.

2026-04-05 18:58:45 UTC

Unexpected Substr Update - NSFW controls fase 1
https://image.nostr.build/ea76991ebd43bf6eeb2a412d6240f0f51046eaff0d3883e8a23f5dc8a5b697aa.jpg
Wanted to share another Substr update after a new round of improvements and cleanup.
Here’s what changed recently:
- Added the first NSFW controls to Substr.
- Posts can now be marked as NSFW during creation.
- Communities can block NSFW posts through their content policy.
- Users can now choose to hide NSFW posts in their own Substr settings.
- Instead of removing those posts completely, Substr now keeps the card visible and shows a simple blocked state with a link back to settings.
- Added a separate setting to blur all media previews by default, even outside NSFW.
- Media previews can now be revealed manually with a single click when that setting is enabled.
- Improved the post text expand/collapse UX with a more compact inline button on cards.
- Fixed pinned posts showing up in the personal joined feed where they did not belong.
- Improved theme customizer behavior so a manually chosen radius no longer resets when switching between light and dark mode.
- Cleaned up some favicon and sitemap setup so search engines get a clearer picture of more indexable pages like Explore and About.
If anyone has more ideas, feedback, or things that feel off, always happy to hear it.
Cheers
[https://substr.network](https://https://substr.network)

2026-04-05 12:37:45 UTC

Happy Easter
Log off a bit, touch some grass
Connect with the fam ✌️

2026-04-05 07:10:07 UTC

- reply

I'm working on Substr, it's more of a Reddit style cliënt. We just launched and is still in development mode but gives you already a good idea what the purpose is.
https://substr.network/

2026-04-03 15:36:03 UTC

A Prescription for Privacy | The Confab 30: Vik Sharɱa
In this Confab, Max sits down with Vik Sharɱa, founder and CEO of Cake Wallet, for a candid journey from his early hacking days on the Apple II, through decades in the steel industry, to discovering Bitcoin in 2013 and Monero in 2016.
Vik shares the eye‑opening moment Coinbase shut his account for a small darknet market purchase of antibiotics—an incident that catalysed his deep dive into privacy and ultimately inspired Cake Wallet’s creation. Max and Vik explore why privacy should be a default, how Monero’s out‑of‑the‑box protections compare with Bitcoin’s more complex privacy tooling, and why a multi‑coin world empowers users rather than divides them. Max and Vik also dig into the rapid rise of AI: how it’s reshaping software development, enabling non‑coders to build real tools, and what it might mean for self‑custody and user experience in the months ahead.
Vik reflects on the growing global demand for financial privacy and access—especially via stablecoins as on‑ramps—while emphasising real‑world utility as the backbone of value. He recounts Cake’s experimental culture (silent payments, PayJoin v2, Lightning via Spark) and the team’s willingness to learn in public. Max and Vik wrap on why decentralised money and local/secure AI can help people everywhere earn, spend, and build without permission, and why he’s more optimistic today than he was a few years ago about privacy tech gaining mainstream traction.
HELP GET SAMOURAI A PARDON
SIGN THE PETITION ----> https://www.change.org/p/stand-up-for-freedom-pardon-the-innocent-coders-jailed-for-building-privacy-tools
DONATE TO THE FAMILIES ----> https://www.givesendgo.com/billandkeonne
SUPPORT ON SOCIAL MEDIA ---> https://billandkeonne.org/
https://fountain.fm/episode/UyOnnuTkc4QSb129ZLkP

2026-04-03 13:59:44 UTC

Substr progress update: better media posts, smoother sharing, and cleaner mobile UX
Wanted to share another Substr update after a new round of polishing and fixes.
This pass was mostly focused on making the app feel better on mobile, cleaning up media posts, and smoothing out a few rough edges in sharing and feed behavior.
Here’s what changed recently:
- Improved media posts so images, videos, link previews, and polls now feel much better inside cards, especially on mobile.
- Media can now stretch edge-to-edge inside post cards on mobile instead of feeling boxed in.
- Portrait images now stay fully visible instead of being awkwardly cropped.
- Clicking an image now opens a proper lightbox viewer with a cleaner fullscreen preview.
- The image viewer now locks the background, adds blur, and feels much more intentional.
- Share previews inside the share modal are more reliable now and no longer show a broken image when a post has no media.
- Media-post text handling is cleaner now, with better previews for longer captions and a nicer expand/collapse flow.
- Fixed duplicate post rendering issues in some community feeds.
- Relay publishing was also improved a bit by tightening how publish success is tracked and expanding relay coverage.
A lot of this was again less about flashy new features and more about making the experience feel more solid, readable, and less janky in daily use.
Thanks again to everyone who keeps testing Substr, sharing bugs, and pointing out rough spots. That feedback keeps helping a lot and directly shapes what gets fixed next.
If anyone has more ideas, feedback, or things that feel off, always happy to hear it.
https://image.nostr.build/f2d6b8d3146f4fc989a51b712afb2b105d75a9677a477ce4d86850154a418dcb.jpg

2026-04-03 10:33:44 UTC

- reply

Succes 🤘

2026-04-03 08:59:35 UTC

GM everyone 🤘 https://image.nostr.build/f2d6b8d3146f4fc989a51b712afb2b105d75a9677a477ce4d86850154a418dcb.jpg

2026-04-02 19:56:43 UTC

- reply

Noted 🔥

2026-04-02 19:51:35 UTC

- reply

Fair question. This still needs to be properly implemented and thought through, but the likely direction is:
When posting, users will be able to mark content as NSFW. Other users will then be able to choose in their profile settings whether they want to see NSFW content or hide it.
On top of that, moderators of a Substr will be able to mark posts as NSFW as well. I also want some community input there, so if enough users flag a post as NSFW, it can receive that status too.
So yes, likely allowed in some form, but with user controls and moderation around it.

2026-04-02 17:46:50 UTC

- reply

We have, but there might be a better solution to set it up... https://image.nostr.build/dd67962406dba5b8c5fbbc6b4c18fc5fc1021e88be00661b165a5559919e8ce2.jpg

2026-04-01 13:41:03 UTC

Substr progress update: faster navigation, cleaner loading states, better signer UX
I wanted to share a quick Substr update after a pretty busy round of polishing and fixes over the past week.
A lot of time has gone into improving how the app feels in day-to-day use, especially around speed, loading states, and account/signing UX.
Here’s what changed recently:
• Navigation between community pages and thread pages is now much smoother, so moving between /s/ and /p/ feels faster and less jarring.
• Loading skeletons were improved across key views to make data loading feel more intentional and less abrupt.
• Engagement loading was cleaned up, so replies, likes, and zaps no longer flash misleading 0 values before the real data arrives.
• Unnecessary duplicate fetching was reduced on important routes like thread and community pages.
• Discovery and joined feed loading behavior was improved.
• Several mobile UX issues were fixed across sheets, modals, and manage views.
• Parts of the signer flow were reworked, especially around browser extensions, remembered accounts, bunker/Amber support, and reconnect states.
• Remembered account handling was improved to make account switching feel more consistent, though switching between accounts still needs to get better overall.
• Share preview handling and fallback OG behavior for posts were improved.
• Moderation flow was continued with softer and more transparent removal behavior.
A lot of this work was not about flashy new features, but about making Substr feel more stable, faster, and less confusing to use.
Also, thanks to everyone who has been trying it, reporting bugs, and sharing honest feedback. That kind of feedback has been genuinely helpful and has directly shaped a lot of these improvements.
There’s still a lot to do, but it’s steadily getting more solid with each pass. More ideas, feedback, and rough edges are always welcome.
https://i.postimg.cc/3JTZSYCn/Screenshot-2026-04-01-at-15-12-35.png

2026-04-01 13:19:14 UTC

- reply

Should we need to prepare ourselves?

2026-04-01 05:53:28 UTC

- reply

Yeah, I know it.
But there’s not just one way to build this. Same idea can exist in multiple forms with different choices and trade-offs.
Not sure why in disbelief.
Also the dens are giving an error at the moment

2026-04-01 05:41:47 UTC

- reply

Fixed

2026-04-01 05:28:06 UTC

- reply

That’s a stretch.
Substr is already mostly Nostr-native. The only part still on a DB is communities, because current NIPs + relay support within my reach aren’t solid enough yet.
It just went live and I’m still working through issues, which is also why it’s not open source yet. But apparently enough to make fun it.

2026-03-31 06:38:17 UTC

- reply

Right now, communities still live on our own DB layer. Part of that is product-related. I’m still shaping moderation, discovery, ranking, and overall community UX based on real usage. I’d rather map that carefully onto emerging standards than rush it and end up with a worse experience.
I’ve experimented with these NIPs already, but in practice it didn’t feel stable or smooth enough yet to build the core of the product on top of. The other part is technical. Relay support for these kinds of community/group flows is still uneven, and public infrastructure just isn’t reliable enough yet for me to make that the foundation of the product.
Once these NIPs are more mature, or once I can properly support this through my own relays and infrastructure, I absolutely want to move the community layer in that direction.
Substr is still early and I’m still figuring out core decisions around architecture, UX, moderation, and infrastructure in real time. Opening the code too early would create pressure to support contributors, explain unfinished decisions, and maintain a level of polish that the product itself hasn’t reached yet.
There’s also a more human side to it. This is still an early, personal project, and I’m not at the point where I feel ready to fully detach from it. 😂
The project will be open in the future, but right now my focus is getting the product and infrastructure to a place where I actually feel confident standing behind

2026-03-30 22:29:57 UTC

- reply

Working on it ✍️
https://substr.network/

2026-03-30 20:19:02 UTC

How Substr Polls Work Across Nostr Clients
We built polls as Nostr-native events, not as a closed backend feature.The poll itself is a normal Nostr post with extra tags like poll_option, poll_results, and poll_closes_at. Votes are separate Nostr events that reference the poll and include a poll_vote tag.
That means other clients can still receive and store the poll and vote data through relays. The only difference is rendering: clients that support these poll tags can show a real poll UI, while others will just show them as regular posts.
https://i.postimg.cc/1XvCMfjr/Screenshot-2026-03-30-at-22-15-54.png

2026-03-30 18:47:36 UTC

- reply

Should be fixed now ✌️

2026-03-30 17:54:02 UTC

- reply

Thanks, I see what’s happening and working on fixing it!

2026-03-30 17:03:07 UTC

- reply

Not that I'm aware off... Can you tell me a bit more, what are you using so I can try to reproduce the flow.

2026-03-30 10:02:39 UTC

- reply

Those are the moments where progress is made 🤣