On 1/19/06, Tyler Close [EMAIL PROTECTED] wrote:
On 1/19/06, Jim Ley [EMAIL PROTECTED] wrote:
No, they'll just disable it, as it does them directly no benefit and
has a cost, so if you educate them enough to make a decision, they
will not decide to be tracked.
Why hasn't this happened to
am 20.01.2006 0:18 Uhr schrieb James Graham unter [EMAIL PROTECTED]:
I believe that even browsers significantly more popular than
iCab allow for this. Yet the vast majority of people leave the feature on.
Maybe because they don't know about referrer security problems and even if
they do they
Thomas Much wrote:
- If people don't want this feature, you'll have to provide a switch to turn
it off.
- If it can be switched off, websites will use the old, hidden ways to track
users.
Can't you say the same about cookies? Many people are up in arms about
tracking and browsers do provide
On Fri, 20 Jan 2006 23:04:52 +0600, Daniel Veditz [EMAIL PROTECTED]
wrote:
- If people don't want this feature, you'll have to provide a switch to
turn it off.
- If it can be switched off, websites will use the old, hidden ways to
track users.
Can't you say the same about cookies?
On Wed, 18 Jan 2006 23:38:41 +0600, James Graham [EMAIL PROTECTED] wrote:
And boy does it suggest this feature will be a marketing problem :(
Darin Fisher blogged the Mozilla implementation[1] and received a stream
of comments, many from people who clearly haven't thought about how easy
On 1/19/06, Tyler Close [EMAIL PROTECTED] wrote:
I think it would be fair to characterize current techniques for link
click tracking as opaque. In contrast, the proposed ping attribute
explicitly declares in the HTML what is intended and how it will
happen. Perhaps the right way to explain the
Hi Jim,
On 1/19/06, Jim Ley [EMAIL PROTECTED] wrote:
On 1/19/06, Tyler Close [EMAIL PROTECTED] wrote:
I think it would be fair to characterize current techniques for link
click tracking as opaque. In contrast, the proposed ping attribute
explicitly declares in the HTML what is intended and
Thomas Much wrote:
am 19.01.2006 23:50 Uhr schrieb Tyler Close unter [EMAIL PROTECTED]:
No, they'll just disable it
Why hasn't this happened to the HTTP Referer header?
There are browsers out there that let the user disable the HTTP referrer
(and enable it only for certain sites that
Hello,
On 10/21/05, S. Mike Dierken [EMAIL PROTECTED] wrote:
Or is it just hitting -- making an hidden HTTP GET request of each
token in the ping attibute?
Right. Hidden HTTP POST request, as it happens, but yes.
Oh, that really shouldn't be done via POST. Clicking a link should be
S. Mike Dierken wrote:
I'm not sure where this idea has come from that sending POSTs
is inherently unsafe (which, by the way, no-one has offered a
good explanation for yet).
POST requests are unsafe because the intent is to modify the data identified
by the resource - data modification is
Hi!
I stumbled about this thread and started reading ... I must admit I
haven't read all postings so please excuse me if my comment was in some
kind already mentioned.
The association I had while reading your problem description and
solution idea is Xlink. It would provide all your required
On Mon, 2005-10-24 at 21:35 +0200, Stefan Leitich wrote:
Hi!
I stumbled about this thread and started reading ... I must admit I
haven't read all postings so please excuse me if my comment was in some
kind already mentioned.
The association I had while reading your problem description
On Sun, 23 Oct 2005 03:47:56 +0300, Mike Dierken [EMAIL PROTECTED]
wrote:
...
How about not putting this notification URI in the anchors at all - what
about putting some metadata in the head element that indicates that
/all/
links clicked should send a notification to the indicated
On Fri, 21 Oct 2005, S. Mike Dierken wrote:
Bearing the above in mind, I've added a section to the a element
that describes a ping= attribute. The URIs given in this attribute
would be followed when the user clicks the link, thus getting around
the problems listed above.
The term
Ian Hickson wrote:
| Note: ... but authors are urged to use the ping attribute so that the
| user agent can .
Perhaps this sentence should be ended? :)
Oops! Fixed.
Not fixed very well.
| ...so that the user agent can the user's experience.
It's still missing the verb. You probably
It definitely should be a POST, because the action performed by it is not
idempotent. See [1].
I agree is seems logical to use POST - the actual URI being visited by the
user likely would be in the content body (although a request header similar
to Referer could be used) and no state from the
On Sat, 22 Oct 2005 00:14:46 +0300, Ian Hickson [EMAIL PROTECTED] wrote:
On Fri, 21 Oct 2005, Charles Iliya Krempeaux wrote:
...
Oh, I know. My salary comes almost entirely from Web advertising. :-)
...
As currently defined the ping= attribute takes a space-separated list
of
URIs, so
J. Graham wrote:
On Sat, 22 Oct 2005, Lachlan Hunt wrote:
It could be defined in reverse, where the ping attribute (probably
given a more suitable name, but I'll use ping for now) could be
advisory information about the final destination and the href
attribute defines the ping destination,
Since this is effectively capturing where the user's attention is
being spent (the click event I mean), should you also define the
other set of events of interest as well?
a href=... on-click-notify=myattention.org/dierken
on-hover-notify=myattention.org/dierken
On Fri, 21 Oct 2005 21:43:59 +0300, Ian Hickson [EMAIL PROTECTED] wrote:
One of the patterns I've seen a lot while looking at big sites is this:
a href=record?url=http%3A%2F%2Ffoo.example.com/ Foo /a
...where redirect is a CGI script that records that the user followed
the link, and that
On Fri, 21 Oct 2005, dolphinling wrote:
Thoughts? Is it evil?
http://whatwg.org/specs/web-apps/current-work/#ping
It's not evil in and of itself, but it won't ever be useful. Anyone who
just finds themselves curious won't be able to use it reliably for at
least 10 years,
Hello,
On 10/21/05, Ian Hickson [EMAIL PROTECTED] wrote:
[...]
Back to feature detecting though. Maybe if we had a kind of loopback
ping that would work. (If that makes sense.) That way a document
could initiate a ping to somewhere it would be able to detect.
You can detect whether
On 21 Oct, 2005, at 7:42 PM, Ian Hickson wrote:
On Fri, 21 Oct 2005, dolphinling wrote:
...
http://whatwg.org/specs/web-apps/current-work/#ping
It's not evil in and of itself, but it won't ever be useful. Anyone
who just finds themselves curious won't be able to use it reliably
for at
Ian Hickson wrote:
On Fri, 21 Oct 2005, Matthew Thomas wrote:
...
I'll leave it in until someone comes up with a better idea, so that we
have a placeholder (and so that people who wish to experiment with the
idea can do so -- there seems to be at least some interest in it).
...
But there is
24 matches
Mail list logo
