What's the easiest way to host a single page site on a domain where the content is a long form post pulled from relays?
Discussion
Cloudflare Pages
https://npub.pro is pretty easy. Havent tried to self host the domain but that seems simple too.
build it locally (hard part) then use caddy to reverse proxy it to a cloudflare tunnel
I'm learning so much from this thread which is great because reverse TOR proxy = hellfire & brimstone.
Post the content on highlighter dot com then point a domain name towards it with redirect Dot pizza.
Npub.pro for sure
Here is what my website looks like.
That's not a custom domain
If you DM nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy I think he can set you up with one if you use npub.pro He wanted to test it out.
Can’t you just CNAME to that?
only if npub.prob supports it
We do now. There's Custom domain section in settings, released to public access as you are asking. You can also self host on GitHub https://blog.npub.pro/post/how-to-self-host-on-github/
So you could just add a custom CNAME and have your own domain
do a cheap web hosting service
Zap a dev 10,000 sats to write a few lines of Javascript for you
I accept the 10,000 sats for a few lines of Javascript deal, nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8
I have also been looking for something like this. Kind of the reverse of pluja/blogo which backs up a static site to nostr, and instead something that just reads kind 8s from a relay and displays them.
Check out https://nsite.lol
nostr:npub1klr0dy2ul2dx9llk58czvpx73rprcmrvd5dc7ck8esg8f8es06qs427gxc nostr:npub1elta7cneng3w8p9y4dw633qzdjr4kyvaparuyuttyrx6e8xp7xnq32cume and I are working on static websites on nostr
you are dispatching to SOCKS5, aren't you. cool!
This is pretty cool but what I'm envisioning is a replacement to Hugo/ghost/etc where you out of band write longform content (as markdown), publish it to your relays, and have a static site just pull every kind 8 from a set of npubs and display them. The hope is to not have to run a server at all (other than your own relay if you want)
You can create a https://npub.pro/ site and set it to "long form posts" only. Then you have a hosted website that shows your longform content. It's just limited to a single npub.
It's not limited to single npub, you can add many contributors
This is what I am most interested in. A simple CMS Site Displaying from a list of npubs. Something like nocomment: https://github.com/fiatjaf/nocomment
This looks great. Along with a static site rendering long form content this is essentially a full fledged blogging engine.
Nocomment is a concept waiting for someone to build it. I don't know enough about nostr to be proficient in coding it, but would be willing to put time into this. nostr:npub19hhggqd5zpmmddv9dvu2qq0ne5pn7f884v4dmku3llp4s44xaqzsl0vms7 your post it the first one I have seen with the similar vision that I have.
... a super-lean CMS for plebs to blog on without the need for the likes of WordPress or even any of the frameworks. It can be built from plain javascript with a slim nosr relay and run on the smallest vps. It would allow people to customize a web site without including mountains of untested unreviewed libraries that they do not need, tied to tech companies they do not want (think disqus ). Soon nostr will replace DNS for discovery and plebs will be able to run sites like this on a raspberry pi with no domain at all.
node app + caddy
Simple static site, one page only, content only from nostr, no formatting, you may want to change it a bit if you want it to look nice (you asked for the easiest, so just as a joke I wrote the truly simplest website possible that does that!)
```js
const noteId = "fdf3d23250bea5008dc5d361ab195eef81942fe938f7aa7ae128379fc4161755";
const relay = "wss://nos.lol/";
const ws = new WebSocket(relay);
ws.onmessage = (e) => {
let event = JSON.parse(e.data);
if(event[0] == 'EOSE') return;
document.body.innerText = event[2].content;
};
ws.onopen = () => ws.send(JSON.stringify(["REQ", "science", { ids: [noteId] }]));
```
(naturally this is not production ready, but I had to do it as a joke 😛)
problem is the ip routing, so NWS(nostr web service)
