"Never worry about getting your site hacked. Since there isn’t a database, there’s nothing to hack." Please. Seriously statiq.io wants prospective clients to believe this is their view on "hacking sites"?
Why I'm moving my clients to static blogging engines
21–30 of 38 posts
Re: Why I'm moving my clients to static blogging engines
#22Re: Why I'm moving my clients to static blogging engines
#23"Never worry about getting your site hacked. Since there isn’t a database, there’s nothing to hack." Please. Seriously statiq.io wants prospective clients to believe this is their view on "hacking sites"?
I know... Is there a server? Are there user accounts? Is there something generating the static pages? Then there's something to hack.
Re: Why I'm moving my clients to static blogging engines
#24out of curiosity, do you take paypal?
This is the third thing I tried to buy in the last few weeks, where my card was declined. All three were using Stripe to process payments.
The sellers all tell me they can't get any detailed errors from Stripe, and I should just check with my bank or try another card.
This is why I often choose Paypal when offered the choice. No bullshit errors about my card being declined or my address not being just right.
Why can't I make a buyer account at Stripe already?
I'll give you my credit card and address info once, I don't have to type all that again, you can verify me once and be done with it. You don't have to provide any wallet services, just let me give me damn money to all these businesses relying on you.
Re: Why I'm moving my clients to static blogging engines
#25Earlier quoted context omitted.
I know... Is there a server? Are there user accounts? Is there something generating the static pages? Then there's something to hack.
The only server involved is the one that runs the compile process. Once the site is built, we push it to S3, and your site is up… Nothing else is needed to view it.
I'm not suggesting it would be in any way easy, it may be nearly impossible, but not having a database isn't the same as being "unhackable."
Re: Why I'm moving my clients to static blogging engines
#26Earlier quoted context omitted.
I know... Is there a server? Are there user accounts? Is there something generating the static pages? Then there's something to hack.
The only server involved is the one that runs the compile process. Once the site is built, we push it to S3, and your site is up… Nothing else is needed to view it.
Re: Why I'm moving my clients to static blogging engines
#27[deleted]
Re: Why I'm moving my clients to static blogging engines
#28Earlier quoted context omitted.
The only server involved is the one that runs the compile process. Once the site is built, we push it to S3, and your site is up… Nothing else is needed to view it.
That still leaves a server that can be attacked, and a way to inject code into people's pages through the compiler. I'm not suggesting it would be in any way easy, it may be nearly impossible, but not having a database isn't the same as being "unhackable."
Re: Why I'm moving my clients to static blogging engines
#29Re: Why I'm moving my clients to static blogging engines
#30Earlier quoted context omitted.
ask the spam accounts. i'm sure they'll be happy to fill you in... [it's serving static - pre-rendered html - web pages. like blogging with github or bitbucket, for example.] [at time of posting half of comments were new accounts with content-less "wow" comments. [or people who don't know how to edit posts. haha.] if that's cynical i'm a pink giraffe.]
[fair enough] hahaha We're at Startup Weekend in Ogden and a few of the people here are being very generous.