Molpyup ketchup time...
HES wrote: At the Book of Aubron speeds (which is how I initially ketchedup) you can't fully apreciate these early frames. While the lines are thicker and the detail is less castlish1 than later on, there's still a subtlety to it.
Same here. Though I visited the OTT five times
while the OTC was live, I was using explainxkcd, Aubron and Geekwagon to see Time itself. Going through it on live replay
, I've seen a lot of things in the early frames I had never noticed (beyond the first 8 frames which I used for my Boom-de-Yada
And having all of the OTTers here posting UNGs, and all the folks we've missed coming back to help celebrate, makes me really glad I Time-travelled up here for this celebration!
mscha wrote: Also, do we really need to allow “plus-or-minus 24”? I think we can trust OTTers to figure out the correct np (op?), using tools like your awesomeful replay viewer, my viewer (that conveniently gives the time of each frame in both UTC and ‘local’ time), and earlier oldpixbot posts.
I didn't want people to have to rely on my viewer, because that would be a single point of failure. But you point out that your viewer
has local time, which I had not noticed before
So that clinches it — I retract the sliding-window proposal.
azule wrote:Maybe an initial run for the week, then a shift to once or twice per NP thereafter. What's the calculation for the time this would take to show the rest before the next Timeversary?
Here I agree with @mscha
that it wouldn't be as useful to me if the frames are stretched out like that over a longer amount of Outside time. I effectively did that while Blitzing (it took 7 mips for me to Blitz through the 4 mips of those first 1254 Newpages), and it was nothing like this Tymiversary experience now. I can only imagine that's a fairly common experience for anyone who is in the Present.
mscha wrote: ... I'll probably go for the original plan: only post if not ninja'd, and no oldpixbot post in the last n posts. ...
I think this will be seaishly molpish! As long as n
is at least 1: I really do think we need to be Rosetta-serious about the double-post thing.
Eternal Density wrote:Teaching old bots new tricks can't go wrong, right?
Sure ... says the creator of
[mustard now removed
macraw83 wrote: ... EditONG sounds molpish, but on the other hand there's a chance that we'll run into the issue of ONGs with a timestamp well before their true time, which could confuse some OTTers into reposting an ONG. ...
That sort of thing is why I was thinking we might need the fudge factor. In particular, my xkcd fora settings put "UTC" after the time on each post, but it's really not UTC, it's my local time. I found these were the only settings that let the Newpix Converter script display the proper newpix time. But when my bot fetches the HTML (or if I view a page in a browser where I'm not logged in) it displays in real, correct UTC. This combined with the fact that OTTers are looking at the OTC from one yip ago (using Kieryn's or my index
to figure out which page goes with each ONG) means we're definitely doing to get some mis-aligned UNGs.
But I suppose when an UNG is early or late, another OTTer might point that out, so no harm done.
Here's the closing bracket: ]
whew, that's better.
BlueCrab wrote:Does anymolpy else translate classical music composers to OTTish? Beesnakethoven is great, isn't he?
Molpzart? (un-oh, do I hear a familiar sawing sound in the distance?)
yappobiscuits wrote: Ch*rp... I'm tired and need coma, but still haven't finished the OTTscars. Well, at least it gives BlitzGirl a bit more Time to work on her things for it. Molpy down.
No problem, not in the slightest! We're all here to
That's an awesomeful Trebuchet into Space, @balthasar_s
Edit: little typos like has->had, by->my