Yes.

Any specific ways it should work? Like auto-send new posts as newsletter? Weekly newsletters with recent posts?

That’s so funny, I was just thinking how can I send a newsletter to the nip-05 subscribers on nostrarabia.com Then I went into a rabbit hole of thinking… what if nip-05 WERE emails… How would account creation look like, maybe you start with getting a nip-05, and the client gives you a “password” aka nsec. Then figure how would they interact with SMTP. And I designed a mental workflow that I think will be very valuable for nostr adoption. But I don’t know how to code 🤣

First I have a request about other thing: I would like to receive Nostr Dm when any of my contributors create a new long post. So I can be reminded that I should add their article on my blog. Maybe a notification option on search settings here:

Nostr DM or even email notification.

I'd be happy to learn more about your ideas here! Regarding sending to your nip05 subs - do you mean nostr DMs? Newsletters delivered over DMs might be interesting too.

Very useful, if it had this function I would abandon substack completely. It's great for my readers to know that there are new texts.

Hmm... Could you use Habla to discover new post of your contributors? And then we could add automations like "if you post THIS emoji as reaction to a post - add it to the site". This way you'd be able to submit to the site from any client.

Awesome! Should it just send each new post to your subscribers, or do you need more complex stuff?

Hum, complicated, no? Haha.

OTOH we could do something like "saved searches" on our side, and then add notifications if new stuff was found for a saved search...

I would prefer receive Email or DM about new long posts of my contributors.

Yes.

Depends on your setup. If you are following all of your contributors and discovering their content in your daily-driver app (i.e. Primal has Reads now) then just posting a specific emoji or a specific zap amount is much simpler than going to our UI.

I disagree, but ok, haha.

Could be interesting to combine that with Creatr/Patreon-like features. Having things like paywalled content.

I think through DMs is good too. One click send to all is amazing I think. Front-end: We will need an opt-in mechanism, because we don’t want to be spammy. Back-end: We need a message composer with a scheduler and draft features I think. As for the email idea, that’s more complicated.

For me this is great if I have a place to manually add the emails I already have in my database. that would solve everything.

Oh you'll definitely be able to add your existing subscribers to the list!

Composer+draft - so it's more about sending custom messages for you? Not just "here is a new post" newsletter kind of thing? Scheduler - what's your specific use for it? If you explain the complicated email idea maybe we could simplify it. Send DM if needed.

Yes paid access to content is definitely worth exploring, we'll get there eventually!

Perfect then, I'll wait for the new update to change everything to the new ecosystem.

Hmm, that might be interesting. Send message to member list on every new post with option to manually send a message as well. Are you thinking each npub.pro user would add smtp email settings in app or a unified provider for all npub.pro users? Bulk DMs would be less popular because most website users probably don't have a nostr client, and those that do can already see new posts on their existing client, but like others said, probably easier to implement.

I think unified provider must exist otherwise email stuff just won't be used. But allowing a custom smtp server makes sense too. Using DM-like encrypted events as nostr-newsletter is something we're going to explore too, but will start with emails. It might turn out very useful for onboarding fans from other networks and slowly converting them to nostr later.

This would be interesting to be able to replace something like Substack 100%. Especially if some kind of subscription or paywall option would be possible.

Yes that's where it's headed!

yes

yes very. currently at ghost now for over two years. And would have hope them to take on nostr instead of activitypub as their new horizon. email will be nice in order to reach that audience. I need to revisit npub pro again to see what's new. I think I read you can filter the feeds now? a big drawback for me before was that very post show in your site, not just long reads. will check it out again.

Do you have any specific features/requirements for "email newsletters"? How would you use it?

I agree that email would allow to connect with existing audience! You've always been able to choose "only long-form posts" to show up on the site, now you can also manually add any additional post, and disable auto-import entirely to only do manual submissions. Please let me know if you have any issues again. Thanks!

so I have two Substacks, and the keys would be (1) ease of importing the email list such that you just tell your subscribers I’m switching, and they really don’t know the difference; (2) ease of composing/editing — make it as easy as Substack; (3) ease of payment — use @strike or whatever to convert fiat payments into sats (probably a harder one); (4) podcasts and video —I upload my podcasts to Substack, and it sends out the feed to ITunes, Spotify, Fountain, etc. If you could do (1) and (2) I would mirror my posts here — I actually already do with Highligher, though it lacks email, but all four would obsolete Substack entirely. Substack takes a substantial chunk of the subscription revenue, BTW, and I think most people here would be happy to do the equivalent in sats. I know I would. Imagine the biggest challenge for paid newsletters is most people built their audience via credit card subscribers, and getting those credit cards into sats for normies might be tough. That and hosting all the larger files like video and audio. But maybe if it were just (1) and (2) I could do a Substack post announcing the Nostr newsletter, get some of the people to sign up and post different written content for those who were interested too. Sorry, this is long, but bottom line the more avenues to escape centralized platforms, the better.

Will definitely look further into it again! I probably look at examples that let all post show. I will take advantage and ask some questions, pls ignore or answer latter if you can, but if not maybe some one else will. I just have not see the answers to the following: 1) Can I bring all my post from my Ghost site, and "import" them on npubpro? If so, will they keep same metadata and dates? or as new "notes" will have the current date when imported. 2) On Ghost I can manage custom and dynamic routing, in order to create collections, etc. If I have set up my site in this way, then when moving my content to npubpro, can I do the same? if not I will end up with lots of non existing pages. .... But even if I am not trying to import, can I have similar flexibility in organizing my posts, e.g javierfeliu (.) com / notes/ filterednotes, or javierfeliu (.) com / blog/ longformposts 3) Is the payment wall, recurrent subscription, right? At least that's is kind of what I understand from your comments elsewhere. 4) Last one I promise! In a self hosted or hosted elsewhere site, you have the ability to close your site, and apart from the servers, the only other place to retrieve your content, is the waybackmachine, or in my ignorance that's what I think so. Having your site on nostr protocol will mean that my posts now events live on relays, making them likely never to go away, so I wont be able to really delete anything, is this correct? I am not yet fully ready to just get ride of my current cms, but for sure your client make a compelling case to bring websites into the hopefully new internet! This are some questions I have had in my mind. Thanks!

Wow that's a ton of input, thank you! 1. There will definitely be a way to import emails (not credit cards, just email addresses), so if you started sending emails from npub.pro people wouldn't necessarily need to be notified - they'd just receive your emails from a different provider. I guess you'd only need to notify people if they're active Substack users who prefer commenting etc on Substack. If there are many active Substack users among subscribers then it would make sense to not import the full list but invite people to re-subscribe on npub.pro. Could you please help me figure out the logic here? 2. Good editor is actually pretty hard to do. Would it work if you just composed a long-form post on Highlighter and then used npub.pro to turn the post into a newsletter issue and send to the email subs? 3. Paid subsciptions are a much bigger deal, especially fiat-related. There's a lot to explore there, so we're leaving it for later now. 4. Video/audio can already be uploaded via any nostr app and then you'd post with a link to that file, and then publish that post on npub.pro site and you'd get an RSS feed that's suitable for submission the podcasting ecosystem. We haven't polished the RSS/podcasting features bcs there are no active users of it yet, but the bones are already there. Example podcast

CITADEL DISPATCH

CITADEL DISPATCH

Interactive freedom tech live show -- hosted by ODELL -- Search CITADEL DISPATCH in your favorite podcast app.

Please let me know if the above points make sense and if you have more feedback. Thanks a lot!

1. There's Ghost import tool at

Npub.pro | Ghost Import

- all metadata is kept, there will be proper dates. 2. There's no custom routing right now, we're adding static pages but that's a bit different. Your posts should have the same hashtags they had in Ghost after import, and npub.pro will have a page per hashtag at /tag/<hashtag> - just like default routing in Ghost. Please send me your Ghost site url and I can check and provide more input if it's possible to keep the similar site structure. 3. No, there's no paywall or recurring subscription at the moment. I don't think any nostr app built a proper paywall or recurring subs yet, although many are looking into that, us included. 4. You can send delete requests to relays to delete your content, it's a widely supported feature. It's not much different from the current internet - after site is taken down there will probably be copies in caches/archives here and there for a while, but eventually it will go away - nobody has any incentives to keep your stuff online forever. Thanks for great questions! You don't really have to ditch your current setup, just try cross-posting to nostr and get a sense of what's working. That also helps us build out the tools.

1. If you have people in the Substack ecosystem with credit cards, and they’re getting everything — videos, podcasts, letters — unless it’s mirrored completely, it’s better for them not to be switched. But there is a minority that would probably volunteer their emails for new/extra content that went out via nostr. If the entire ecosystem were in place here, I would just import the entire list in that case. But if it’s only newsletters (and no payments), I would make it opt-in, and do different content for those users. 2. Yes, Highlighter is good, and that’s a good point. No need to re-invent the wheel — could just compose there, send via npub.pro. 4. I’ll look into it — some of the video files are 2GB or whatever though. And no problem — thanks for building these tools!

GM, question. As there is no data base, all content is technically static? or because it draws from relays is still considered dynamic. just asking because thought that git pages just hosted static. If I self host, can I connected my nostr site as a subdomain on, lets say nstr.javierfeliu com ? I think this will be a super fun sandbox. and a great way to drop the mark a difference between all internet www. and new nstr. 😅. Alternatively, same question if I host the code with your team. (which is always an option. but I wamt to learn and this sounds like a good project to give it a try) My personal site is javierfeliu.com . the only dynamic routing is the collection of /blog/ that host the index template and the / host a static page. I am still not sure what I will do with the site at the end, have some ideas but kids have taken all the free time this year.

Hi, great questions! 1. Git pages allow hosting dynamic sites if the code works in the browser - most nostr apps are like that. Our engine can work on the server and in the browser, it connects directly to relays and converts events to html pages. Our hosting runs the code both on the server (to pre-render for search engines) and in the browser after the first page is loaded (to save our resources and to enable offline work). The self-hosted option we're offering is currently limited to browser-side rendering - so it can be hosted on Git pages, but can't be crawled by search engines properly. Server side engine coming later (won't work with Git pages as it will require nodejs). 2. Yes you can attach a custom (sub)domain with our hosting, and you definitely can add it if self-hosting. 3. Our alternative to your /blog/ collection would just be /posts/ (for long-form articles), and with static pages coming soon you'd be able to override the homepage and make other static pages like About me. I suggest you just try npub.pro, and try importing a couple posts from your Ghost site and try playing with it. It should take 10 minutes to do all that and have something usable. You can always attach custom domain or self-host later, there's no "migration" - it's nostr, all the data is out there.

The last point is key, thanks! Based on that, I will try it out! I guess It didn't sink it yet the "no migration" part, we are just so used to it, so didn't want to start something, to later just re do it all if migrate and self host. "You can always attach custom domain or self-host later, there's no "migration" - it's nostr, all the data is out there."

Exactly! That's the beauty of nostr! And thanks for the zap!

You are welcome. thank you for the open info.

@brugeman GM!, I create a npub pro site yesterday, really fast, sweet. I like the tags filter for the homepage, navigation and other custom options, AND that it has code injection section, really cool. After creating the site, I gave it a try to the self hosted version, to complicate my life more I hosted it on Netifly as for test I figure it would be easier, just drag and drop the zip file and connect my subdomain. that site is now here https://nostr.javierfeliu.com/ . I change the "website address" on the npub admin panel. to this new address. The npub site is

The Shaggy Report

The Shaggy Report

Craft Beauty in the Chaos: Reflections on woodworking, faith, life, entrepreneurship, culture, and family—changing how you see life, one storm at...

First issue is that I obviously have two site, how do I keep the self host version if I desire to, without having two versions? I guess I could delete, but that will no longer give me the option to download the zip file every time I make an update to settings, correct? Second, I try to connect my domain in npub pro, but then I realize it will conflict with my set up in netifly, as essentially will direct both to the same subdomain. AND that is for the paid pro version you offer (wish I very well take at some point). I am just playing with it right now. If, selfhosted, I just change the web address, but not touch domain right? (as seen in the instructions) I just add the records npub ask if I am planning to take your premium tier? The version hosted in your server, its considerably faster to load. On phone, i can zap both sites, no problem, on desktop just the npub version, not the self hosted(it stay loading..) Thank you for any feedback if you have some! Have a good day

@brugeman GM! any feedback on this will be much appreciated and zaps will be sent for sure 😅 . To try to finish a set up. I try to read on the blog and other docs, but do not find these answers.

Hi, sorry for long reply, was away for a couple days. You don't need to re-upload the zip file after each settings update - settings are saved on nostr and the code inside zip file will take new settings from nostr. The only reason to reupload the zip file would be some big updates to our code (minor updates are auto-propagated now). For now we're just rendering all sites on our servers - there are probably less then a dozen of self-hosted ones so we didn't bother to come up with special handling for them. The only real issue with having two sites is duplicate content that might confuse Google - but you won't be getting much search traffic anyways for starters, so that's not a big priority for now. If you attach your subdomain to npub.pro then it will no longer point to netlify (you'll need to remove netlify's dns records), so there can't be much conflict there. I'm not sure I understand the question about the paid plan and DNS settings, please let me know more. Re. zaps - I just zapped on your self-hosted site, there shouldn't be any difference, please try reloading the page or clear cache etc. The self-hosted version is client-side rendered, so first page load is slow, but then both self-hosted and us-hosted versions work the same - rendering happens in the browser, so they should be equally fast after the first load. Server-side rendered self-hosted version will be available later. Thanks for a lot of feedback!

thanks! 1) the zaps are working fine, try it the next day and was working. 2) I was guessing that changes to the theme, navigation or code injection, will require and update to the self hosted code, is that not correct? I do understand that normal nostr profile settings will be made on any client and reflect there without need of re upload nothing. 3) Yes, that was worry ( not really big at all) the content duplication....but was mostly courios if I was missing something. 4) The question about Dns settings and the subdomain attachment is: As a self hosted user, can I point the npub site to my netifly, but I am understanding right now by your answer, that I can not. When I mentioned the pay plan, is that when I start the configuration of my own domain from npub settings, I am lead to upload some records, cname and text, because the "your own domaim" is a setting for the pay plan, I was guessing this really has no use if I self host, so I do not need to add any npub records on my dns except to point to my npub site as I currently have it. hope that make sense. Because you already said the npub version. Will be keep on being life, I am guessing there is no point in messing with that domain configuration from the settings panel, unless I am on the paid plan **...please if those not make sense, ignore. once I am consistent in content I may delve deeper, I do not want to waste your time!** Thanks!!

> 2) I was guessing that changes to the theme, navigation or code injection, will require and update to the self hosted code, is that not correct? No, all changes you make in admin panel are saved on nostr as a special event kind and thus are fetched by self-hosted code, no need to update it. Well, technically site name or icon are printed in a manifest file which would need to be reuploaded so that these changes would be visible if people add site to homescreen (PWA), but I'd say it's a minor concern. It would only be absolutely necessary to reupload if we made significant changes to the site engine code. > can I point the npub site to my netifly No, you can't point subdomain.npub.pro to netlify. > this really has no use if I self host, so I do not need to add any npub records on my dns If you self-host, you don't need our dns settings. You can attach a custom domain on a site hosted by us for free while we're testing in public and don't have paid plans launched yet. Thanks for asking, this helps us understand the sources of potential confusion!

this clarify all the doubts for sure!!! and I am clear now with the code being hosted but almost all settings (not just posts) being events on nostr. Again, it is a whole new way of thinking. thank you!!