> Mike Dierken wrote:
>
> >How about not putting this notification URI in the anchors at all -
> >what about putting some metadata in the element that
> indicates
> >that /all/ links clicked should send a notification to the
> indicated service?
> >
> That idea has several obvious flaws, the
Mike Dierken wrote:
>How about not putting this notification URI in the anchors at all - what
>about putting some metadata in the element that indicates that /all/
>links clicked should send a notification to the indicated service?
>
That idea has several obvious flaws, the two most important bei
> > > >
> > > > 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?
> > > > > > > on-hover-notify="myattention.org/dierken"
> > >
>
> I would posit that mos
>
> > Bearing the above in mind, I've added a section to the 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.
>
> Since this is effectively capturing where t
On Sat, 2005-10-22 at 16:33 -0700, S. Mike Dierken wrote:
> > >
> > > 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?
> > > > > on-hover-notify="myattention.o
>
> > 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?
> > > on-hover-notify="myattention.org/dierken"
> > on-copy-notify="myattention.org/dierken">Wicked Cool Stuff
> >
> > 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?
> > > on-hover-notify="myattention.org/dierken"
>
> I realise this is hypothetical, but on-hover-notify w
>
href="http://www.flickr.com/photos/dierken/?delete=39177102&magic_cookie=528
479cac210fc6z837c0ac708334fe6"
>
> I would certainly hope that Flickr requires authentication
> before an URL
> like that had any effect, in which case the developer of the website
> would only be able to delete their
On Sat, 2005-10-22 at 20:25 +1000, 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,
Lachlan Hunt wrote:
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
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, su
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, such that following
On Sat, 22 Oct 2005 00:34:28 +0300, Ian Hickson <[EMAIL PROTECTED]> wrote:
On Fri, 21 Oct 2005, ROBO Design wrote:
<...>
:-)
I agree with most of your points. In reply to specific suggestions:
<...>
You can do this already using elements (in fact it's even more
effecting for DDOSing a s
On Sat, 22 Oct 2005 09:50:44 +0300, S. Mike Dierken <[EMAIL PROTECTED]>
wrote:
<...>
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?
Wicked Cool Stuff Here
This wo
Ian Hickson wrote:
One of the patterns I've seen a lot while looking at big sites is this:
Foo
...where "redirect" is a CGI script that records that the user followed
the link, and that then redirects the user to the real page (potentially
setting a cookie in the process).
This is used
On Sat, 22 Oct 2005 06:36:30 +0300, dolphinling
<[EMAIL PROTECTED]> wrote:
Ian Hickson wrote:
<...>
This still doesn't "force" it to work. As a user-tracking-implementer
doing it for money, I want to make absolutely sure I count properly.
That means forcing people to hit the counter _be
On Sat, 22 Oct 2005 00:38:05 +0300, Ian Hickson <[EMAIL PROTECTED]> wrote:
On Fri, 21 Oct 2005, James Graham wrote:
<...>
Can you list some? Other than redirects, I couldn't actually think of any
reliable ones. XMLHttpRequests dispatched in tandem with the original
request are unreliable sinc
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
U
On 10/22/05, Ian Hickson <[EMAIL PROTECTED]> wrote:
> On Fri, 21 Oct 2005, S. Mike Dierken wrote:
> > Oh, that really shouldn't be done via POST. Clicking a link should be
> > safe and sending a POST as a side-effect is not safe.
>
> GET means that you can do it again without affecting anything. In
On Fri, 2005-10-21 at 23:50 -0700, S. Mike Dierken wrote:
> > Bearing the above in mind, I've added a section to the
> > 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
20 matches
Mail list logo
