21–30 of 48 posts
Good list, but what about security? SQLInjections etc? You need to have that covered more than the rest in my opinion.
How would you 'check' it, in the sense it could be on a checklist. Are there tools to automate this type of thing?
You could also let a program like Nessus run on your website. But that goes globally and will detect it.
I know the text says "... or equivalent software," but is there any great advantage between using Google Analytics or a hosted component on your own server? I feel it's impolite to subject your users to be tracked by Google and other huge companies just because they visited your website. Is there at least any tracking service that respects Mozilla's DNT[1]? [1]: http://dnt.mozilla.org/
It's also probably illegal in Europe now, though at least in the UK the authorities have declared a one year moratorium on taking action over it because the new privacy rules on cookies etc. are practically unworkable even if well-intentioned.
Earlier quoted context omitted.
True, what I want to say is. If you have a ton of user uploaded media (and such), you probably want to not want SE to index everything. (For example to save bandwidth). I should probably re-word that line, but I dont want to get too technical.
> If you have a ton of user uploaded media (and such), you probably want to not want SE to index everything. (For example to save bandwidth). Bandwidth is cheap. Ranking poorly in search engines is not. If you've got a ton of user uploaded media, you've potentially got a ton of content for Google to pick up on and rank you for.
I'm curious, what is the standard practice for the storage of static media - where are the static files (text/images) stored on the server, and how are the appropriate config files that concern that media set up?
In a way, it gives you a bunch of excuses to put off your public launch - "I just need to fix some CSS bugs in Firefox 2" or "I just need to test the backup restore process one more time to make sure it works". Most of us aren't building bank software here, and if you're building anything consumer based (think Facebook), the advantage of having a site up and getting feedback on it over having all these things checked off is astronomical.
Good list, but what about security? SQLInjections etc? You need to have that covered more than the rest in my opinion.
Earlier quoted context omitted.
> If you have a ton of user uploaded media (and such), you probably want to not want SE to index everything. (For example to save bandwidth). Bandwidth is cheap. Ranking poorly in search engines is not. If you've got a ton of user uploaded media, you've potentially got a ton of content for Google to pick up on and rank you for.
For something like an image hosting or pastebin site, isn't that possible a privacy concern? I'm curious, what is the standard practice for the storage of static media - where are the static files (text/images) stored on the server, and how are the appropriate config files that concern that media set up?
Good list, but what about security? SQLInjections etc? You need to have that covered more than the rest in my opinion.
I know the text says "... or equivalent software," but is there any great advantage between using Google Analytics or a hosted component on your own server? I feel it's impolite to subject your users to be tracked by Google and other huge companies just because they visited your website. Is there at least any tracking service that respects Mozilla's DNT[1]? [1]: http://dnt.mozilla.org/
Earlier quoted context omitted.
That's ugly. But who cares? A sophisticated user (read, anyone using Pingdom) won't be using the same password for their Pingdom account and their email. Though the consequences if they did would be ugly.
Generally, I use a different password for every site (using 1passwords generate feature). That helps guard against any site storing in plaintext