Sorry about the downtime

[Dani]

I apologize for the downtime we've experienced over the past couple of days. We were in the process of moving servers, and it's finally compete :)

Sorry for any inconvenience,
Dani

[nanosani]

Yes ... daniweb had become readonly in this period :D

[Dani]

Sorry ... but hopefully from now on we'll be faster. Do you notice any difference?

[Ancient Dragon]

how long is this going to go on anyway? I still cannot access it from IE6 -- Firefox works ok.

[Dani]

Everything should be perfectly fine as of yesterday. I am an IE 6 user myself so DaniWeb definitely works in IE. Additionally, I'm in NY and the server is down in Texas, so it's not as if I have any special connection to the web server. If you can't access the site from one browser but you can from another on the same machine, I suspect you have something cached or perhaps a software firewall is acting up.

[Comatose]

It's a good thing you fixed it, ya know, us Daniweb Junkies go through serious withdrawal when the site goes down ;)

[tayspen]

Tell me about it :) Seriously though, glad its all working :D.

[Comatose]

Ok, I LOVE the Avatar.

[tayspen]

Lol, thanks you are the second person who has commented on it :).

[WolfPack]

I'm in NY and the server is down in Texas

Looks like the butterfly effect to me. ;)
Glad the server is up anyway. I actually started reading a book during the downtime. :cheesy:

[Dani]

There really hasn't been any consistant downtime. We were down two or three times over the past week, with no time being for more than an hour, in addition to about 5 hours during which DaniWeb was read-only while the database was being transferred to the new server.

[WolfPack]

There really hasn't been any consistant downtime.

yeah. That maybe why I couldn't finish reading. :sad:

[Ancient Dragon]

If you can't access the site from one browser but you can from another on the same machine.

The IE6 is at work and FireFox is at home, about 20 miles away in a different city. I'm in Illinois and will try again this morning when I get to work.

[Dani]

Is it possible there is a proxy server at work that is caching the old DNS?

[Dani]

For some reason, your work is caching the old IP of daniweb.com. Until your work decides to update their DNS (grr) you can access DaniWeb from http://web.daniweb.com

[Ancient Dragon]

Hurray! The link worked. Thanks :)

[Dani]

Hehe, yup. Not sure why your work doesn't want to update their DNS entry to point http://www.daniweb.com to the web.daniweb.com server.

[goldeagle2005]

Lol, thanks you are the second person who has commented on it :).

I'm the third....I'm the third....I'm the third....

Cool Avatar

[Dani]

I was the first.

[goldeagle2005]

Yeah, you're the admin. You always get to be the first ;)

[The Dude]

Did we finally move to VBB 3.5??

Im noticing threads i didnt read STILL BOLD when i re-login and that sucks!! (I think DATABASE THREAD TRACKING is awefull -- "Cookie based" thread tracking is much better)

Just wondering if we went 3.5 (Nothing wrong with 3.5 but when i noticed the threads,i started to wonder)

[Dani]

We went vB 3.5 a few days ago and we are using database thread tracking. Personally, I like it much better. May I ask why you don't?

[The Dude]

Well because you have to remember to click MARK ALL READ before you logout,otherwise you lose your place :)

Im not mad or anything honey and THANK YOU for being honest :)

I knew straight away when the change occured (the threads))

Ill just have to remember to click MARK ALL READ before i logout (I have to do that on a couple other 3.5 sites also)

Not to worry!!

[Dani]

I'm confused why. For me, when I click on the Posts Since Last Visit link, it works the same way with 3.0.x as it does with 3.5. The only difference is now it additionally shows "threads that have not been updated since your last visit but still contain unread posts" below the listing. I find it more helpful :)

[The Dude]

Hmmmm

I dont know why VBULLETIN included DATABASE thread tracking anyway on 3.5,its very MEMORY HEAVY on the DB,its silly to store stuff that way..... (Uses alot of storage to remember everyones last read post,etc......)

Regardless they should have made it a LOCAL OPTION that the user can control from thier control panel (Allow members to choose DB tracking or the old way on thier account) -- That would make more sense than what they did (Made it a global setting either 1 or the other)

Ah well..

[Dani]

It's not as memory heavy as you might think because once you visit a forum, it automatically considers all threads within that forum older than 15 days as read. (From what I understand at least, I might be mistaken). The previous cookie-based method wasn't working well for us because a lot of our members access the site from home and from work and cookies don't remember settings. Additionally, a lot of the Windows users frequently clear their cookie settings when trying to debug IE problems and browser hijacks. Besides, without database-stored thread marking, I wouldn't be able to have added that neat feature to the homepage that shows recently viewed threads when you're logged in :)

[The Dude]

Ah i see :)

Well like i said,nothing to worry about.......

:)