Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:Not-so-accurate source (Score 1) 487

by xrmb (#43927633) Attached to: BBC Clock Inaccurate - 100 Days To Fix?
Really? or do I miss something? ...put the server time as seconds since 1970 in a variable when rendering on the page... ...as soon as javascript starts you take the local computers time and calculate the offset which you apply every time you update the clock... ...make sure your webserver has the correct time, but that is easy to-do... ...also timezones wont matter at all, since you just query the UTC times, the offset applied to the local time will still be correct... ...yeah 100hrs sounds about right, where can I apply to do it?

Comment: how does it compare to kzip? (Score 2) 124

by xrmb (#43049595) Attached to: Google Publishes Zopfli, an Open-Source Compression Library
I wonder how it compares to kzip (http://advsys.net/ken/utils.htm) which is trying to do the same just better and faster. Also google is trying to save 3% on gzipped content, but they dont use optipng/pngout on their images... up to 10% gains... jpegs, never heard of jpegtran google? it saves 20% on my digicam pictures (leaving exif and all meta intact).

"Mach was the greatest intellectual fraud in the last ten years." "What about X?" "I said `intellectual'." ;login, 9/1990

Working...