Comments for Data.Driven()

Comment on Marking files as binary in CVS by Marcos

Marcos — Sun, 11 Sep 2011 09:03:42 +0000

They know They are using mercurial now but I can’t move my stuff over as it’s all interlinked.

Comment on Marking files as binary in CVS by c69

c69 — Fri, 02 Sep 2011 21:33:29 +0000

You should tell them about git, someday Or mercurial, to not scare them with new syntax.

Comment on Marking files as binary in CVS by Marcos

Marcos — Tue, 23 Aug 2011 09:28:56 +0000

I’m not using CVS by choice… the w3c made me!

Comment on Marking files as binary in CVS by Jay

Jay — Tue, 23 Aug 2011 09:27:22 +0000

You are using CSV? How very 1990s of you. Henceforth, before reading your blog, I’m going to put a short-sleeve-tshirt on over a long-sleeve-tshirt and listen to some Pearl Jam

Comment on Zip files and Encoding – I hate you. by Yuhong Bao

Yuhong Bao — Mon, 27 Jun 2011 02:10:07 +0000

“There’s nothing “weird” or “nonstandard” about the OS X Unicode decomposition,”
Not exactly true:
http://developer.apple.com/library/mac/#technotes/tn/tn1150.html

Comment on Zip files and Encoding – I hate you. by Yuhong Bao

Yuhong Bao — Mon, 27 Jun 2011 02:00:02 +0000

O. Andersen: FYI, the difference between CP437 and CP1252 is that CP437 is a OEM codepage and CP1252 is the ANSI codepage. Yes, there are two codepages in use in Windows. Most GUI stuff use the ANSI one, most console stuff and other stuff that comes from DOS uses the OEM one.

Comment on Zip files and Encoding – I hate you. by VlaD

VlaD — Thu, 18 Nov 2010 21:07:51 +0000

I used this simple utf8 normalizing sub, which solved all issues with all the archive types:

Here’s the example:
#!/usr/bin/perl -w

use strict;
use warnings;
use bytes;
use Encode::Detect;

sub normalize_to_utf8 {
return decode(”Detect”, shift);
}

$fname = “any_filename_from_archive_as_it_comes”;
$fname = normalize_to_utf8($fname);

# now $file’s encoding detected and converted to UTF8
# ready to be used

Hope this helps.

Comment on Privacy of Geolocation Implementations by Data.Driven()» Blog Archive » Presentation Slides – Privacy of Geolocation Implementations

Wed, 14 Jul 2010 17:58:07 +0000

[...] are the slides for the presentation I gave at the W3C Workshop for Advanced Web APIs. See my other blog post for more information about the workshop and the paper. View more presentations from Me. Share [...]

Comment on Privacy of Geolocation Implementations by Marcos

Marcos — Wed, 14 Jul 2010 15:09:25 +0000

@oisin, yes, you are correct that the paper would benefit from a discussion in those terms. I did that for the actual presentation I gave at the W3C workshop. I will publish those slides now.

[WORDPRESS HASHCASH] The poster sent us ‘0 which is not a hashcash value.

Comment on Privacy of Geolocation Implementations by Oisín

Oisín — Thu, 08 Jul 2010 12:36:55 +0000

That’s a decent paper, and could perhaps serve as a motivating force for improving the understandably immature implementations of geolocation privacy mechanisms we have today.

I’m somewhat surprised that Chrome has a more transparent and flexible privacy mechanism than the other browsers compared (two methods of modifying access rights: centralised interface and the on-the-fly activity indicator, etc), given the popular contention that Google’s thirst data collection may not be in the best interests of individual privacy. On the other hand, I’m not surprised that Apple’s privacy mechanism in Mobile Safari is somewhat poor.

One thing that seems to be missing from the paper is a summary scoring of the browsers across the different privacy needs – accessibility, control, confidentiality.