Show HN: Nekoweb – a retro static web hosting
1–10 of 121 posts
Re: Show HN: Nekoweb – a retro static web hosting
#2Re: Show HN: Nekoweb – a retro static web hosting
#3Re: Show HN: Nekoweb – a retro static web hosting
#4If this is ad free and free to publish on, what’s the monetization strategy? What the benefit to using Nekoweb over publishing static content to S3/CloudFront?
Re: Show HN: Nekoweb – a retro static web hosting
#5Like neocities? Whats the difference?
and some paid plan differences: - ftp support - up to 5 custom domains - cheaper (you can get 1 custom domain for $1 or 5 and all perks for $3 vs neocities' $5)
Re: Show HN: Nekoweb – a retro static web hosting
#6If this is ad free and free to publish on, what’s the monetization strategy? What the benefit to using Nekoweb over publishing static content to S3/CloudFront?
Why does this matter? If they can provide 99% uptime for the service they provide, I don't care.
> What the benefit to using Nekoweb over publishing static content to S3/CloudFront?
This is the attitude that kills the net. Sends of the vibe "It's not on AWS so it must not be used, don't you dare".
What the benefit of to using S3/CloudFront?
I suppose it all boils down to that folk not knowing the old internet. The understanding where you relied on hosting companies to provide webspace with an banner, or paid-so webspace that's now lost in today "innovative" world.
One day the clouds will fall, and your site will be with it.
Re: Show HN: Nekoweb – a retro static web hosting
#7If this is ad free and free to publish on, what’s the monetization strategy? What the benefit to using Nekoweb over publishing static content to S3/CloudFront?
> If this is ad free and free to publish on, what’s the monetization strategy? Why does this matter? If they can provide 99% uptime for the service they provide, I don't care. > What the benefit to using Nekoweb over publishing static content to S3/CloudFront? This is the attitude that kills the net. Sends of the vibe "It's not on AWS so it must not be used, don't you dare". What the benefit of to using S3/CloudFront…
Re: Show HN: Nekoweb – a retro static web hosting
#8If this is ad free and free to publish on, what’s the monetization strategy? What the benefit to using Nekoweb over publishing static content to S3/CloudFront?
Re: Show HN: Nekoweb – a retro static web hosting
#9Earlier quoted context omitted.
> If this is ad free and free to publish on, what’s the monetization strategy? Why does this matter? If they can provide 99% uptime for the service they provide, I don't care. > What the benefit to using Nekoweb over publishing static content to S3/CloudFront? This is the attitude that kills the net. Sends of the vibe "It's not on AWS so it must not be used, don't you dare". What the benefit of to using S3/CloudFront…
I guess the reason to ask about monetization is because you want to know how long a host is going to exist. Knowing how they plan to make money is a part of knowing the answer to that. As you say, it used to be good enough to have a space and accept there was an ad banner…but if no banner, then how?
CloudFlare has been losing money for ages. I use it but seemingly everyone is sure it'll last forever.
Re: Show HN: Nekoweb – a retro static web hosting
#10If this is ad free and free to publish on, what’s the monetization strategy? What the benefit to using Nekoweb over publishing static content to S3/CloudFront?
> If this is ad free and free to publish on, what’s the monetization strategy? Why does this matter? If they can provide 99% uptime for the service they provide, I don't care. > What the benefit to using Nekoweb over publishing static content to S3/CloudFront? This is the attitude that kills the net. Sends of the vibe "It's not on AWS so it must not be used, don't you dare". What the benefit of to using S3/CloudFront…
...what?
S3 launched in '06 and is coming up on 20 years of being a thing. At this point it's had a stronger/longer lifespan - and will likely continue to do so - than pretty much any of the old net hosting sites.
OP was clearly just asking why bother using something like this over . The only real answer is that you want to do something different - and that's totally fine.