Not a particularly useful use of the inode table. The filesystem is great for a few hundred or even a few thousand records, but when you're dealing with billions of records, that adds up to a lot of wasted space.
I'm pro-paperless because it's a blasted mess.
Burning my karma kandle at both ends.
that our government is sliding towards communism!
( ) Killing them that way is not slow and painful enough
Pray tell, what level of vigilante justice would you consider to be slow and painful enough?
Right. They are ignoring the huge volume of legitimate mail that hotmail/msn silently deletes in violation of the RFCs.
Hotmail doesn't represent the majority of e-mail accounts, and usually it seems to be down solely to the incompetence of whoever is administering hotmail, rather than intentionally violating RFC. Same difference, I suppose, but it's certainly not a majority of the legitimate e-mail they get to them, anyway.
"Over seven years ago my friend Joseph Fung and I decided the web needed an alternative to the leading PHP forum package out there. We created a PHP fork of perl based YaBB and after working with what we called YaBB SE for a bit, we re-branded as SMF, or Simple Machines Forums, along with a new core of code written by a developer who called himself [Unknown]. After seven years its crumbling but why?"
Other former SMF contributors are already picking up the story (Original German version).
As of writing this, the SMF community has begun banning members who link to blog post on their official forums, including Co-Founder Jeff Lewis."
Link to Original Source
Wrong - the auto-update feature is new to 7.x, so actual sites running 6.x (or earlier) doesn't benefit from it. Also, the new feature will only install and update modules and themes, not 'core', so I'm guessing updating core from 7.0 to 7.1 is probably going to require about as many manipulation steps as you need to go from 6.14 to 6.15. I don't have a lot of experience, but I would not say it's "extremely easy": the stable 6.x version requires you to do a lot of file and configuration manipulation just to go from 6.14 to 6.15 (if you follow all the recommended steps, which I did for my test site recently). It's not hard, it's just not automated.
If you set everything up properly, you just overwrite everything not in the sites directory with the new files, and then possibly run the database update script. Quite trivial.
I actually set up Drupal sites by symlinking to a main drupal installation for files and common modules. All the benefit of the
...on my servers come from hijacked IE6 machines or bots claiming to be IE6.
Nail cannot come too soon.