Profile_bird

Hey there! nathanrice is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What are you doing? Join today to start receiving nathanrice's updates.

Already using Twitter
from your phone? Click here.

nathanrice

  1. word.
  2. “The democracy will cease to exist when you take away from those who are willing to work and give to those who would not.” Thomas Jefferson
  3. Time to watch "The Patriot" and a little of the HBO John Adams miniseries. I recommend both highly for a day like this.
  4. @pearsonified yeah, I wrote all that last night ... and it's still not 100% functional.
  5. @pearsonified it is, indeed, in all its incomplete glory -- http://code.google.com/p/pr... (latest changes not checked in, tho)
  6. … and that includes HTML5. The safest thing to do is either stick with xHTML1.1 or revert back to HTML4.1 until 5 is approved.
  7. So, xHTML isn't dead yet. There's an HTML5 variant for xHTML called xHTML5. But, we're still months, or years, away from any "new" standard.
  8. @michaeltorbert Yeah, I definitely want to stay compatible with your stuff.
  9. @michaeltorbert class_exists
  10. @DaveCarruthers SEO is becoming more about good content, and less about "methods" lately, and will continue to do so, IMO.
  11. SEO Title Tag takes priority over Prodigy's <title> generation too, and will be auto-hooked, if available. #prodigywp
  12. … and will use vestigial AIOSEO and HS options, if they are available in the post/page meta.
  13. Also, all Prodigy SEO features disable themselves if All-in-One SEO or Headspace2 is active ... #prodigywp
  14. Prodigy is getting some in-post SEO love --> http://twitpic.com/98tnn (not yet in trunk) #prodigywp
  15. @nomadone you can email them to me if you want
  16. Since XHTML2 has been abandoned, I suppose it's time to jump on the HTML (5) bandwagon and start relearning HTML syntax.
  17. @chrishajer maybe I should dial it back, but I just like to have a little fun with these types of questions. not trying to be mean.
  18. @chriswallace could be. isn't.
  19. "I can't log into my WordPress" -- of course, it must be the theme's fault. We're so very sorry! (idiot)
  20. "I can't edit my posts or pages" -- A support request posed to a theme developer. You tell me, does that sound like a theme issue?