Golive Update
Jan. 17th, 2020 11:14 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
Just to give everyone an update, the archive should only be a few hours later than planned going live. Golive should be happening by 3-4am at the absolute latest, and there's a very good chance that it might be happening earlier.
If you're planning on posting a treat of any type before golive, try to have it posted by 2am EST.
If you're planning on posting a treat of any type before golive, try to have it posted by 2am EST.
(no subject)
Date: 2020-01-18 04:24 am (UTC)(no subject)
Date: 2020-01-18 04:28 am (UTC)(no subject)
Date: 2020-01-18 06:19 am (UTC)(no subject)
Date: 2020-01-18 06:27 am (UTC)(no subject)
Date: 2020-01-18 06:34 am (UTC)(no subject)
Date: 2020-01-18 06:43 am (UTC)(no subject)
Date: 2020-01-18 06:44 am (UTC)(no subject)
Date: 2020-01-18 06:52 am (UTC)(no subject)
Date: 2020-01-18 06:55 am (UTC)(no subject)
Date: 2020-01-18 07:01 am (UTC)Would it be possible for future rounds for the community post with rules and notes about different times in the schedule to be pinned so that it is always visible? In my experience more people are likely to reference the dreamwidth post than to read on AO3. Otherwise it's just sort of habit for exchange participants to assume that deadlines and reveals won't happen before the stated time on the AO3.
(no subject)
Date: 2020-01-18 07:16 am (UTC)The reason I was using the AO3 schedule is because I couldn't find the information on the Dreamwidth. I can't think of another exchange where the AO3 schedule is intended as the latest time the archive will open not the earliest, so if that was in a pinned post on the Dreamwidth it would be a lot clearer going forward.
(no subject)
Date: 2020-01-18 06:44 am (UTC)(no subject)
Date: 2020-01-18 06:52 am (UTC)(no subject)
Date: 2020-01-18 06:59 am (UTC)