Just a Good VS Evil mobile wallpaper
Substr
npub122wd...fgdf
Official Substr Account - The community layer of Nostr. Your space, your people
Substr Update - Shared Nostr Events, Community Space Cards, Live Stream Polish
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!
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!
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 @Tomek ⚡ K
https://substr.network/s/events
GM 💪
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://substr.network/s/open-source-art
https://substr.network/s/open-source-art
Stay Humble
GM ✌️ 
We just shipped the first step towards livestreams on Substr.network
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.
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.
From brainfart to execution. We’re almost there... 😄
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.
View quoted note →
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.
View quoted note →
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
GM
still building. still learning.
Login Signer Flow Update
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.
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.
Todays theme is Brutalism 😎
Video upload ✅ Livestream next?
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
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
GM
Should we add another post type? If so, which one? 
Add mentions or keep it clean?
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.
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.
Substr, For more logical feeds 
Goal for the coming days!
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.
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.