Subscribe: Comments on: echo reply
http://shaver.off.net/diary/2006/01/20/echo-reply/feed/
Added By: Feedage Forager Feedage Grade C rated
Language: English
Tags:
americans browser  americans  disabled  foil heads  foil  heads  heise  important americans  important  ping  pref  privacy  read  tin foil  tin 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: Comments on: echo reply

Comments on: echo reply



noise from signal



Last Build Date: Thu, 10 Nov 2011 07:05:56 +0000

 



By: morgamic

Sat, 21 Jan 2006 09:59:05 +0000

Nice post, Mike. I thought it was well written and it cleared things up a bit.




By: shaver

Fri, 20 Jan 2006 20:16:26 +0000

I know privacy isn’t very important to most americans, but a browser is important to privacy so as a developer you should think about the fears of some tin foil heads and talk about it in advance, so other people not quite tin foil heads feel better about it.

I don't know that privacy isn't very important to most Americans -- certainly most Americans I've worked with have had strong feelings on it, but that's not the important part of your comment.

I agree with the rest: we owe it to ourselves to communicate these things better, especially when we can tell from other mailing list conversations and bug comments that "non-tinfoil types" need to have some pieces of it explained to them. That was, in fact, the main point of my post, and I apologize if that wasn't clear.




By: Herman

Fri, 20 Jan 2006 19:53:55 +0000

Yes, it was a loud landing, no hidden stuff. But I didn't read about it beforehand, only read the blog. Instantly comments asked if this feature could be disabled (or is disabled by default). An update to the blog only told that feature also exists as exploit in IE. That's bad communication made worse. The technical reasons for the change are valid and may improve speed, they also improve tracking, but imho not much. In heise.de (50% Firefox!) there instantly was a big discussion, and someone told it can be disabled by pref browser.send_pings. I asked him where he got that info, he couldn't tell, so I foolishly searched bugzilla for 'ping' (looping, swapping, wrapping etc..) instead of looking at checkins, found some ping bugs, found the bug, read discussion and comments, and had to read the patch to find the pref. I then tested the pref to be working at gemal.dk.

I don't accept an excuse this is for testing only, won't be in next release. You don't have to test what never could be in a release. Maybe it really was for making a field test, then it should have be done more clandestine, or more openly. Of course more clandestine would have hitten worse...

I know privacy isn't very important to most americans, but a browser is important to privacy so as a developer you should think about the fears of some tin foil heads and talk about it in advance, so other people not quite tin foil heads feel better about it.

herman

http://www.heise.de/mediadaten/english.shtml heise has 400.000 c't magazines each fortnight, heise-online has 22 million visits and 150 million pageimpressions monthly.

http://www.heise.de/newsticker/meldung/65723 49.2% Gecko, 31.8% Microsoft ;-) 10/2005

http://www.heise.de/newsticker/meldung/33169 21.3% Netscape 66.9% Microsoft 03/2002




By: Max

Fri, 20 Jan 2006 14:50:02 +0000

It just needs a little marketing. The ping attribute is a polite way for websites to ask users for tracking information. Redirects are obnoxious and can't be turned off. Ping is an improvment because it can be turned off by the user, hence the ping attribute can be seen as the site saying 'Please tell me when you click this link'. In that context, it doesn't really matter how much it gets used, at least site developers who want the info but also respect thier users would use it.