The Countdown to a Thousand!

[Paula]

Aaand we are falling badly behind. We should be at nearly 500 by now to make it.

[Suzee]

Must to writing moar.... moar writingsses!

[Leigh]

If you have time, Suzee, it's your turn on our T'lat/A'kua post. I think.

[Leigh]

So. Um.

Like I said in the Cbox, I screwed up. I lost count of the posts. I think I did, anyway. I've wracked my brain over and over today, and I just can't remember for sure. We're either at 365 posts, or 367.

Either way, I think I effed up.

The way I see it, this can go two ways: One, I somehow fix this and we keep trying. Two, I let this challenge drop. This hasn't been a good year for several of us; we've been sick, busy as hell with work or real life, grieving, dealing with screwy technology, and in one case, possibly dead. (Which is probably just my anxiety talking, but that's another story.) I might've asked too much of y'all with this anyway. However, we could try again in 2017, starting midnight Mountain time after the Times Square ball drops.

What do y'all think we should do? You're all smarter than me; I trust your judgement.

[Suzee]

Actually Leigh, I have access to the database and can give you an accurate count of all the posts that have been timelined up to the end of June,  Then you can pick it up from there.  How's that?

So I exported the table to Excel and filtered for 2016 through the end of June. That gave me a number of 312 total posts timelined.

[Leigh]

That doesn't count all the posts we lost before GoDaddy boned us, though, and some of the posts we lost were reposted to our GoogleGroup, so I had to disregard those from the count. We were working on my best estimate from the start. :-/ So along with the posts we had before GoDaddy royally mucked up, we're still on 365 or 367 overall.

But if I'm completely wrong, and we really are only at 312, then I should've asked someone else to do the post counts a long time go. (sorry, everyone!)

[Avery]

Leigh, it may be somewhere in the middle ground. As far as I'm aware the timeliners were able to get most if not all of the pre-GoDaddy-fail stuff. But also sometimes folks send backdated posts that don't get timelined, so those don't come up on the site.

[Leigh]

I think in that case, I need to adjust my post perimeters and indeed start again next year.

My profound thanks to everyone who had fun with this.

[Heather]

Leigh, it may be somewhere in the middle ground. As far as I'm aware the timeliners were able to get most if not all of the pre-GoDaddy-fail stuff. But also sometimes folks send backdated posts that don't get timelined, so those don't come up on the site.

Shouldn't all posts get timelined, even if they are backdated? Otherwise, what's the point of even posting it? Is there a way for it to be timelined but not credited toward marks?

**Off topic **

[Suzee]

Leigh, it may be somewhere in the middle ground. As far as I'm aware the timeliners were able to get most if not all of the pre-GoDaddy-fail stuff. But also sometimes folks send backdated posts that don't get timelined, so those don't come up on the site.

Shouldn't all posts get timelined, even if they are backdated? Otherwise, what's the point of even posting it? Is there a way for it to be timelined but not credited toward marks?

**Off topic **

Yeah well that last question is the reason they aren't timelined because ... nope.

[Heather]

How sad.

[Suzee]

Yeah, I agree,

Typically, there really is a grace period into the next month, and posts that are late because of LOA or something similar ARE timelined.  So, if you see one that was late for that reason we can still make sure its posted on the site.

Remember you can petition the council if you have one ready but can't send in because the other person hasn't signed. In this case the council can approve the timelining when it's finally ready to post.

This is also the reason some posts are wrapped in a flashback.  In that was the post can be dated in the current month while the body of what happened can be in the past.