brugeman on Nostr: Hi, sorry for long reply, was away for a couple days. You don't need to re-upload the ...
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!
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!