XHTML-CSS.com

This is our blog. It's mainly about programming, web developement and design, social web, coding habits and advice and miscellaneous geekery. You can subscribe to the feeds to never miss a bit.

Twitt my URL !

Permanant link —Nov 18, 09:32 AM

As you may see, the bivalidator didn't got all the success we expected. Even on the W3C mailing lists, there's not so much noise about it… You may think that it's somehow disappointing. Well... no... actually YES! :) But seriously, we knew at the very beginning that we won't be able to handle millions of hits for the simple reason that we're hosted on a shared hosting! No, really, not even a VPS! So the processing time and bandwidth we consume currently on Bluehost aren't that harmful.

Anyway, many people asked a legitimate question: "Why a yet another validator? We can use the W3C ones!" Yes sure! The answer is also simple: "For fun! We made this for fun and learning!" But that's not all. In fact, having a single place to check for markup/style validity is simpler than two.

Second, having raw validation data in XML/SOAP format gives us real power for providing features that the W3C doesn't provide yet. And that's what we're happy to announce today: Feature #2 (the #1 was to check for validity duh!) is to track the validity of your pages with twitter!

Twitter, recently made a nice feature called "track" with it you can track for a word or a phrase and be notified whenever someone talks about it. Now all you have to track the validity of your pages is to set a track on your url with your twitter account and you're done! Easy, simple and even the W3C doesn't provide that yet ;-)

Example: track http://google.com

P.S. Please, please! don't abuse our lil' tiny emo project, don't use bots or sorcery with it. We told you we're on a shared hosting and they could kick us out for huge processor usage.
P.P.S Please slicehost, give us a slice :)
P.P.S. slicehost Said NO!


Enjoyed this post? please subscribe to our feeds to stay informed.

Commenting is closed for this article.

« Previous post:
Next post: »