posted by dennisn on September 3rd, 2008 at 10:03PM
That's unecessary. In particular, it will hurt developers and security analysts.
Also, if everything ends up getting submitted anyways (be it to content or pendingcontent), it still allows for an abuser to flood the database/filesystem. There should just be a check in the submission trigger to prevent too many insertions in a certain time interval.
That pendingcontent list is /really/ a bad idea. Not only is it very misleading -- false-positively identified users will think everyone is ignoring them, and everyone will think he has disappeared from the site --- but, also, who gets to move pendingcontent to content?
It /may/ have some uses if the community grows /really/ big, and we decide to select front-page stories, but that's never going to happen :)
Also, if everything ends up getting submitted anyways (be it to content or pendingcontent), it still allows for an abuser to flood the database/filesystem. There should just be a check in the submission trigger to prevent too many insertions in a certain time interval.
That pendingcontent list is /really/ a bad idea. Not only is it very misleading -- false-positively identified users will think everyone is ignoring them, and everyone will think he has disappeared from the site --- but, also, who gets to move pendingcontent to content?
It /may/ have some uses if the community grows /really/ big, and we decide to select front-page stories, but that's never going to happen :)
|
posted by dennisn on September 3rd, 2008 at 10:06PM
There are a couple things that I updated (or tried to update ... namely the code:unread/modified content pages to include the siteuri base), that appear like regular stories on the front page. It's unsightly, and if I didn't know better, I'd start to get angry that nobody was responding.
|
