Timestamps aren't becoming a server thing -- we'll still be using the date and time from your computer (either the timestamp when you loaded the update page, or the timestamp when you posted the entry, depending on whether you have the 'use time when entry was posted' checkbox checked or not). We'll just be removing the "you can't post this entry, you have an entry timestamped after it" error that stops you from dating things out of order.
(We haven't decided yet what the UI is going to look like for scheduled entry scheduling -- we're still working on solving backend stuff, and because of how we're implementing things, we have to get server-side draft posts implemented before we can do scheduled posts; we've got a, well, draft of some of the draft post backend complete, but we're still trying to solve a few things there, too. The whole thing turned out to be way, way more complicated than we thought it would be originally. Still, I doubt our implementation of scheduled posts will look like LJ's, with the timestamp on the update page used as a "you should post it at this time" trigger; it doesn't fit in with some of the features I really want in the implementation.)
If you are unable to use this captcha for any reason, please contact us by email at firstname.lastname@example.org