new ToS and Privacy Policy

[kunzite1]

there was a code push yesterday.

the new ToS and Privacy Policy are live. we haven't been notified yet.

ideally, they would have been pushed live and then immediately followed by a news post. or the other way around.

why does everything seem to be done backwards?

Comments

[burr86]

Because we have to do another code push right now, and once we finish that, we're going to be posting to news -- hold tight, don't freak out. :P

[kunzite1]

not freaking out. just confused as to why the order of events seems to always be the opposite of what i think is logical.

of course, my logic is rarely the same as the logic of others.

[christine]

To be fair, when it comes to any push+announcement situation, if the push is done first, and an announcement comes later, some people will find that disconcerting. If an annoucement is made first, and the pushes to support the announcement aren't done until later, people will find that disconcerting (and to be honest, the latter is very counterintuative to me).

[kunzite1]

i guess there's a difference in this situation since it's both code changes and changes to legal documents.

when the 6a/lj thing happened, users were forced to agree to the new ToS because it was radically different.

the ToS is changing again, and i think with the previous time, we were informed before it went live and had the big announcement dealy.

i could be mis-remembering though.

[donutgirl]

It's not just the TOS that has changed. I just saw my first ad - stupid thing with a dog. Is the sky falling yet?

(And no, I'm not signed up for the ad level. This was on the comment page for lj_ads, funnily enough.)

[adzite1]

i saw my first ad too! omg!

(and yes, this account is signed up for the ad level. this is kunzite1, funnily enough.)

;)

[foxfirefey]

Whoa, I better use our girl to check it out for misself!

[adzite1]

you make it sound like she's our secret lovechild or something. :P

[crucially]

So if there is any large problems we can revert, if we announce and there is a problem, people will have way more problems ...

[kunzite1]

that makes sense.

but there would be less of that (hopefully) if testing was done on a public test server where more eyes could take a look at it and try to break stuff.

though, i've been told that something like the ads system would generate more arguing than testing if it was put on a public test server.

[rahaeli]

We did test in a staging environment, and on local dev installs, and and and, but it's impossible to replicate the actual LJ environment in staging or test -- there are always bugs that won't be found until there are nine million eyeballs on them (or won't be found until the code is working against a large database, or one with legacy data, or working against memcache, or behaving at load, etc, etc, etc)

LJ has eighty gazillion variables; it's not possible to test in a controlled environment with all of them. We always prefer to take an extra twenty minutes after push to make sure nothing's on fire before it gets front-page status...

[crucially]

We did have testing, and we are moving to a more open testing environment where people can opt in for testing.

However, the biggest problem is load, we have no reliable ways to generate the kind of traffic LJ handles, so while we can do scaling tests we can't reliably test.

[adzite1]

test.