Oddbean

Great questions! These nostr-sites are nostr events of kind 30512 https://nostr.band/?q=travel+kind%3A30512 - we just don't have an app to showcase them yet. Themes are nostr events too of kind 30514 https://nostr.band/?q=ruby+kind%3A30514 - there will be a marketplace for them, imagine admin posting "please customize XYZ in my theme" and some developer adjusting it and publishing the update on nostr and admin applying it in 2 clicks. Theme assets (templates, js, css etc) are on blossom servers, addressed by hashes by the themes, if some server dies files can be discovered through nostr on other server (no code for that yet). The engine core is https://github.com/nostrband/libnostrsite - it can run on the client or on the server. We run it in three places: on the server to pre-render the sites we host, in the browser tab for the current self-hosted version, and in the service worker after the first page load. Our server does nothing after the first page load, all rendering happens by service worker talking to relays and blossom servers, all sites are PWAs that work offline, rendering nostr events cached in the browser's database. We don't have a self-hosted version with server-side rendering, but that one's coming too. Current client-side rendered self-hosted code can be hosted on github pages - first page load takes a while, and you don't have nice pre-rendered meta tags, but aside from that it's identical, and sites don't depend on our infrastructure. The nip-512 that we've drafted for nostr sites is meant to make "nostr site" description portable across the engines, so that you could switch from npub.pro engine to another implementation (Oracolo hopefully maybe), without having all your links or site structure broken. To summarize: npub.pro sites are as much nostr as they could possibly be, our hosting and management app are just a convenience.

Here's all that you've ever wanted to know about npub.pro's interworkings 👀 nostr:nevent1qqsffujen8vvrus3nqw2ygc0kmcamuzucvc5l9xkkccqzlvq4408qsspzemhxue69uhhqatjwpkx2un9d3shjtnrdakj7q3qxdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wsxpqqqqqqza5tc9q

I'm still low-level-noobl in terms of Nostr and npub.pro ...I love to see the potential, but have no idea how to contribute to it Trying to build a nostr.cooking style website for recipes, but falling at every hurdle in terms of 'posts' and 'notes' Hoping smart plebs than me can provide tutorials or links so a simple-pleb can study #npub.pro #asknostr

Got myself started as u described, but the fell face first as I didn't want my current npub notes to be the feed for this site, and couldn't figure out 'posts' Spinning up a new npub to practice but would love info from those in the know Appreciate nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqpzdmhxw309akx7cmpd35x7um58g6rsd3eqyxhwumn8ghj7mn0wvhxcmmvqyg8wumn8ghj7mn0wd68ytnhd9hx2px56dk taking the time 🤙 pura vida

why not create a new account specifically for your cooking site then use that account to post recipes as blog articles on yakihonne.com then spin us a npub.pro site using your cooking account and pull your posts as the recipes?

All of the recipes you upload to zap.cooking will follow your npub on the npub.pro site that you build. This is the interoperability that nostr offers 😁 See what @Enki did here with his https://enkiskitchen.npub.pro

Thank u nostr:nprofile1qqs2wguqtndxwfg3j8y8sm6d5k8hjlnfwavzxqf4fw5wjx7tqdpde8qpr9mhxue69uhhqatjv9mxjerp9ehx7um5wghxcctwvsq3samnwvaz7tmjv4kxz7fwd4hk6mmnw3ezuurfde4sz9thwden5te0v4jx2m3wdehhxarj9ekxzmnyvash6x Just to bring it back to basics for my simple self...are the recipes I'm seeing on nostr:nprofile1qqsyfhqu9kuu877hhm5j2lkwk5478nuvgza00d3lgmjkkk9px8r57zcprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qyg8wumn8ghj7mn0wd68ytnddakj7r4zzc8 npub.pro page, 'posts' that are through zap.cooking? What I don't want is to see my normal note feed on a website where I can contribute on cooking. The difference between 'posts' and 'notes' is lost on me I think I need to spin up a new npub and play around to understand Thank u all for being so helpful 🫂

Correct. The recipes are in a long form ‘note’ which is customized for recipes. This is different than a kind 1 ‘note’, which is universal of sorts and the same type that we are sharing back and forth on now. All of the notes that you post, whether long form for recipes, or long form blogs, as well as the kind 1 are all tied to your npub that you are signed in with, so your content is portable and connected to your npub.

Yes, in the npub Pro page, you can specify hashtags. So technically, what it's doing is it's searching for anything that is tagged with #nostrcooking, which is a hashtag that automatically gets appended to zap cooking posts. And in my other menu tab, anything that I tag with #Foodster shows up.

"Notes" are short notes you post using Damus/Primal/Amethyst. "Posts" are long-form content that you can post with habla.news or highlighter.com or yakihonne.com, and zap.cooking recipes are also long-form posts. Looks like we should rename "Posts" to "Long-form posts" - longer, but more obvious to new people.

That's almost exactly how npub.pro sites work, you could render them inside an app without relying on the website url. All you're asking is us to rebuild html+css, which is too much to ask nostr:nevent1qqsffujen8vvrus3nqw2ygc0kmcamuzucvc5l9xkkccqzlvq4408qssppemhxue69uhkummn9ekx7mp0qgsrx4k7vxeev3unrn5ty9qt9w4cxlsgzrqw752mh6fduqjgqs9chhgrqsqqqqqptadtwv

This is why I think it's revolutionary. People dont yet see the possibilities, but with every new user, every new website, every new theme, every new widget, eyes will open more. It's still quite early in its iterations and may have to be improved many times over years. But the structure is so good, that the surface for innovation is high. And, importantly, we know the web scales to 10 billion people already. It's like a bobsled, first you start pushing it, but then it gains momentum and you jump in.

Yes. Also very important is that it's permissionless without a king-maker effect. You dont have to write a NIP, get it approved, make an app. You can just tinker with your nostr homepage, and if something works out, post it in a note. In fact, people are doing this already, including non-techies. That's how you know it's a winner.