Re: [delicious-discuss] Re: Frequently Accessed Sites
On 11/29/05, DeWitt Clinton [EMAIL PROTECTED] wrote: http://delancey.unto.net/ Interesting. I would like to see transparent click-tracking like this in delicious. I don't like that right-clicking a link increments the counter, but I can see a rationale for having it so... c ___ discuss mailing list discuss@del.icio.us http://lists.del.icio.us/cgi-bin/mailman/listinfo/discuss
Re: [delicious-discuss] Re: Frequently Accessed Sites
I totally understand. I wasn't particularly sure what the right trade-off was when it came to link tracking, so I just did my best to have it count all clicks. Of course, that part is highly browser-dependent, so it is a little inconsistent from client to client. The next thing I will likely implement is an optional Greasemonkey script for Firefox that downloads a list of your bookmark hashes, and when the browser visits a site that matches the hashed URL, post an increment to the Delancey server. Thus when the Greasemonkey script is installed I can do away with outbound click tracking altogether, and simply rely on the script to increment the count no matter how the user got to the page. This also has the advantage in that the counts will be accurate even when the user doesn't go through Delancey. (And for those concerned with privacy, as I am, Delancey only stores one-way hashes, and the Greasemonkey script would only post increments for URLs that have already been publicly bookmarked by the user.) More feedback is always appreciated! Cheers, -DeWitt On 11/29/05, Chris Lott [EMAIL PROTECTED] wrote: On 11/29/05, DeWitt Clinton [EMAIL PROTECTED] wrote: http://delancey.unto.net/ Interesting. I would like to see transparent click-tracking like this in delicious. I don't like that right-clicking a link increments the counter, but I can see a rationale for having it so... c ___ discuss mailing list discuss@del.icio.us http://lists.del.icio.us/cgi-bin/mailman/listinfo/discuss ___ discuss mailing list discuss@del.icio.us http://lists.del.icio.us/cgi-bin/mailman/listinfo/discuss
Re: [delicious-discuss] Re: Frequently Accessed Sites
Regarding passwords -- I completely agree. I thought long and hard about how to allow people to claim a username on Delancey without ever asking for their del.icio.us password. The compromise was a claim system whereby they could set up a new password for Delancey, and then use a bookmark in their del.icio.us account to verify they are who they say they are. That said, I need to do an even better job of emphasizing that their Delancey password *should not* be the same as their del.icio.us password. (I only store a one-way hash of it anyway, but I don't want to even come close to the del.icio.us password.) As far as del.icio.us adding this functionality -- cool. It would obviate the need for Delancey, of course, but del.icio.us is clearly the best place for this functionality. As it stands, I think Delancey is best considered a useful tool and tech demo and a testament to the power of the openness of del.icio.us. Interestingly, I didn't use the del.icio.us API at all in building Delancey. Not that I didn't try, but it turned out that I got far more mileage out of the JSON feeds and form POSTs than I did with the API. I'm all in favor of your ideas about a way of proxy authentication. Check out OpenID -- there may be some potential in there. Coincidentally, I'm working on a generic distributed identity engine as my next project on unto.net, and I'm definitely going to expose parts of it as OpenID. Best, -DeWitt On 11/29/05, joshua schachter [EMAIL PROTECTED] wrote: DeWitt Clinton wrote: Hi, I recently ran across the delicious-discuss thread on keeping track of which links are clicked on most frequently. As it turns out, I just released a client/server application called Delancey that enhances del.icio.us to do just that. I'll be posting the technical details regarding the implementation and source code in the next day or two, but until then, you may want to simply try it out and see. The Delancey application can be found at: http://delancey.unto.net/ Suggestions and comments always appreciated. Thanks, and best regards! Looks neat. Some observations: 1) I'm still freaked out about putting my userid and password into random forms. I floated this proposal earlier: http://lists.del.icio.us/pipermail/discuss/2005-September/003912.html 2) We are planning to do click-tracking in delicious after the current round of changes are done. Presumably this will be exposed via the API. Joshua -- joshua schachter [EMAIL PROTECTED] http://del.icio.us/joshua ___ discuss mailing list discuss@del.icio.us http://lists.del.icio.us/cgi-bin/mailman/listinfo/discuss
Re: [delicious-discuss] Re: Frequently Accessed Sites
On 11/29/05, joshua schachter [EMAIL PROTECTED] wrote: Tom Tobin wrote: Can this be disabled on a per-user basis? I really, *really* don't like click tracking. Presumably. We haven't thought about it too much. What bookmarks did I click on recently is a frequent feature request, though. My biggest problem with the common implementations of click tracking is that they make a common use pattern of mine worthless. Google's click-tracking works by having every search result link to a horrible url like: http://www.google.com/url?sa=tct=rescd=1url=http%3A//www.random.org/ei=l6iMQ_bmBMT2YKiBzekHsig2=GABCdvvbnFGHbRk_Qax1OQ and bollocksing the statusbar text to look the the actual url (http://www.random.org in this case). In practice, I find that this leads to me doing a search to find a url to paste into an email/blog post, right-clicking to copy the url, and finding that I have this horrible redirect url instead. It's a pain. But an implementation that, say, used javascript to rewrite every tracked link such that it was still a real link, but its onclick actually submitted a form that ran the redirect... that would be nice. It'd have more missed clicks than the simpler approach (people without JavaScript, and I don't know what opening in a new tab/window would do to that), but since it's not critical functionality... -David --- http://www.ficwad.com ___ discuss mailing list discuss@del.icio.us http://lists.del.icio.us/cgi-bin/mailman/listinfo/discuss
Re: [delicious-discuss] Re: Frequently Accessed Sites
My biggest problem with the common implementations of click tracking is that they make a common use pattern of mine worthless. Google's click-tracking works by having every search result link to a horrible url like: http://www.google.com/url?sa=tct=rescd=1url=http%3A//www.random.org/ei=l6iMQ_bmBMT2YKiBzekHsig2=GABCdvvbnFGHbRk_Qax1OQ and bollocksing the statusbar text to look the the actual url (http://www.random.org in this case). In practice, I find that this leads to me doing a search to find a url to paste into an email/blog post, right-clicking to copy the url, and finding that I have this horrible redirect url instead. It's a pain. We won't do anything that will break right-click. This is a fundamental user gesture for links. I don't believe the javascript rewrite is necessary - you just need a href= onclick=... Joshua ___ discuss mailing list discuss@del.icio.us http://lists.del.icio.us/cgi-bin/mailman/listinfo/discuss
Re: [delicious-discuss] Re: Frequently Accessed Sites
On 11/14/05, Björn Lindström [EMAIL PROTECTED] wrote: Tobias [EMAIL PROTECTED] writes: I would like to have some sort of system or page that ranks my bookmarked sites in order of access.Meaning the more I click the link the higher in my list the link will rise. . . All my frequently clicked bookmarks will be on top! Anyone know of anything like this or how it could be implemented?That would mean each link would have to be connected to a bit of _javascript_ or something like that. I would not like to see that happen. It wouldn't necessarily involve _javascript_ at all. You could implement it by using server-side redirects, akin to how Google (and others) track what link users click on search results, Gmail, etc. Bookmark links would go somewhere like this: http://del.icio.us/redirect/http/www.google.com The redirect page would track the click (along with any appropriate user information, referrer, etc.) and redirect the user to http://www.google.com -Bill ___ discuss mailing list discuss@del.icio.us http://lists.del.icio.us/cgi-bin/mailman/listinfo/discuss
[delicious-discuss] Re: Frequently Accessed Sites
Bill Clark [EMAIL PROTECTED] writes: On 11/14/05, Björn Lindström [EMAIL PROTECTED] wrote: That would mean each link would have to be connected to a bit of JavaScript or something like that. I would not like to see that happen. It wouldn't necessarily involve JavaScript at all. You could implement it by using server-side redirects, akin to how Google (and others) track what link users click on search results, Gmail, etc. Google doesn't do that. Not for regular search results, anyway. In any case, I sort of included that solution in the something like that that I don't like. Let links be links. ;-) ___ discuss mailing list discuss@del.icio.us http://lists.del.icio.us/cgi-bin/mailman/listinfo/discuss
