Profile_bird

Hey there! phparch 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's happening? Join today to start receiving phparch's tweets.

Already using Twitter
from your phone? Click here.

phparch

  1. RT @mtacon: #tekx cfp over. Online registration officially up: http://bit.ly/8SVCwg Save up to $300 with our early-bird discounts. #php
  2. @koenvanurk Lots! We're still going through them.
  3. ♻ @mtacon: TEK·X Call for Papers: the last day is here! Where is your proposal? http://bit.ly/76yETw #tekx #php
  4. @jcarouth Doh, we'll fix it right away. Thanks!
  5. RT @mtabini: Want to win a 52" LCD HD home entertainment system? Try php|a's new contest: http://bit.ly/WKHpJ #php
  6. RT @mtacon: T-7 days until the tekX Call for Papers Ends. Do you know where your submission is? http://bit.ly/Lafv6
  7. Pro blogger applicants: we'll start looking at submissions this week. Have lots of responses; will take a while. Hang in there!
  8. RT @mtacon: http://bit.ly/1Hfx0e Getting Accepted @calevans gives hints on how to get talks accepted to a conference. #correctURL
  9. Announcing the php|architect Episode 2009-07: Bake'n'shake http://phparch.com/podcast/... #php #podcast
  10. php|a is looking for a few good bloggers; if you want to apply, more info on our site: http://bit.ly/Oaa5U #php #phpa
  11. Attention #winphp contest participants: we've started accepting entries… check your inboxes!
  12. @chrisyallop Sorry! You can still vote for the entries and get some goodies later on, though!
  13. Publish or perish (by @bdeshong): http://bit.ly/2ZmaGt
  14. @jclermont We have your name—we need your application's (it's under “about your application,” after all!)
  15. @gena01 No, it was a mistake in our zone file—pointed to old nameservers that only “happened” to work until Marco moved his blog recently.
  16. To all who were having problems with our DNS—we think we have fixed it—awaiting propagation to confirm. Props to @arneblankerts for his help
  17. @chrismcmacken Glad to hear that!
  18. @kchodorow No, it isn't… DNS is not working properly; it looks OK on our side, but we're investigating.
  19. @rudolfrck it's not broken on our end; it's a dns issue, but we seem to be ok—what DNS provider are you using?
  20. @chrismcmacken It's probably a DNS issue—trying to figure it out. Are you using OpenDNS?