We need more educators writing about the benefits of nostr in various niches. And publishing them on other platforms besides nostr.
Discussion
Funny enough, I’m working on something. Was going to post in on nostr though 😂.
Cross post to other channels. We need the word going out. I’m also writing something atm.
Are you writing about k-12 or university?
When the time comes, could I get some guidance on how to publish cross platform?
I’m just writing a blog post on my own platform about why it should move to nostr 😂
But I may tweak it and publish on medium and anywhere else I can find.
I stopped communicating on Twitter because it’s censoring nostr content reach and my followers are acting brain dead for some reason.
My goal is to get podcasts that are served from nostr but with RSS feeds that allow them to go out to all the normal platforms. #podstr
That is one avenue for getting nostr content out to non-nostr audiences while still using the platform.
🔥
Imagine the experience for a normie when they’re in their podcast app and the episode says, “Hey, this podcast you’re listening to right now? It is hosted in nostr. You’re already using the service and you didn’t know it.” #purplepill
That’s interesting 🤔
Do we think they will care where it’s ran from?
But yeah, more exposure is good 👍
I’ve been wanting this. Id much rather pay us $16 a month than SoundCloud, RSS or whoever else.
Circular economy is the way.
Put in a good word to the people on the opensats panel, let’s get it funded! 💪
I was asking #[4] to lend his expertise on this very thing. 🥺
#[3] and I have chatted about this a bit. Need to get a NIP written up. I’ve been slammed by the fiat job lately so haven’t been able to. Also have chatted with Adam and Dave over at Podcast Index. They aren’t as excited about it, mostly because they think that we’re yet another project trying to replace RSS. That’s not the goal.
Yus ! I fully support this 💯
I submitted it to opensats, hoping to get help funding the dev.
Sick!
The project definition is excellent, and your point about podstr being a Trojan horse for nostr is spot on.
Do you have an idea of the resources you need? Talent, sats, etc?
The website has a project timeline with a high-level breakdown of the pieces that need to be built. The time estimates are for one person doing it all alone.
Resources:
- 1-2 web devs to write the authoring tool, RSS interface, audio client (mostly as an example).
- 1 dev working on the NIP and working with Podcasting 2.0 namespace project to ensure compatibility.
- 1 designer to help with the interface for the authoring tool and the example client
- When the initial parts are usable, we need people to evangelize to podcasters to get them cross-posting on podstr
- A few trusted community members to run podstr relays (nostr relays that use the necessary NIPs)
Dude yes, I've had this same thought.
