Right. The supported way to do this is with /post?title=...&url=....
Tags are not specifically supported in this forwarding chain because
I do not
want to give publishers the opportunity to pre-tag their stuff as per
reasons
I have stated several times in the past.
Joshua
On Dec 5, 2005, at 4:14 PM, Johan Sundström wrote:
[Hm, lost the list recipient; resending:]
This is somewhat verbose. It is also trying to be helpful, and
hopefully
without being overly annoying doing so. (I'm probably trying somewhat
too hard, because my opinions below seem to Scream "you Must be
Wrong about this and I must be Right, but I'm too polished to say that
out loud", which is not quite the polite angle I'm aiming for. Oh,
bother.)
Problem:
On entering Del.icio.us to add a new bookmark via the add address,
http://del.icio.us/<user>?
v=3&url=...&title=...&extended=...&tags=...
[...]
The posting form URL is not a guaranteed API for adding stuff to
delicious. We may change how it works, etc etc etc.
I'm sure you may, and I sort of presumed that the v=3 bit above was
indication of this having happened at least twice already, most likely
for good reasons, too.
But let me rephrase my bug report as a feature request, and explain
why it is that this non-API is such a Very Useful device for making
Del.icio.us improve the web and the web improve Del.icio.us. I'm not
trying to be a whiny ass, here. Your posting form is however, under
many circumstances, the Ideal way of hooking in to the functionality
you provide.
It's very similar to how RSS readers of today always tend to have a
passwordless, URL only API, where you can link to their URL with
the URL of an RSS feed provided in a query variable, and on visiting
that link, end up within the reader, with the option of subscribing
one
click away, or just doing nothing at all, closing the window again. As
is the case with making a Del.icio.us bookmark today with your form.
You should treasure this low threshold to access accordingly; it is a
very cheap way for you to be more useful to your users.
You should probably use the API itself for this.
Using the API allows me to add bookmarks, provided that I state my
Del.icio.us password. I could have my application write up a form for
adding a Del.icio.us bookmark to a post, filling in some fields,
leaving
others (the description field, where I might want some short executive
summary of my post, for instance) to be filled in, add a password
field
and finally emulate your form using the API. This would work, but also
kill the part of the user experience that makes this setup feel
comfier
than using lots of cut and paste between windows, using a method of
access (i e the bookmarklet and form, your browserextension) which
does not require the password.
Or, I could let my application ask for the password once, and store it
in a Greasemonkey persistent variable, which would be accessable to
any person knowing how to type "about:config" and "greasemonkey"
in my users' browser, which would be worse still.
I personally think users should never be encouraged to expose an API
password which would allow the holder read/write access to their data,
to a third party, such as my own application, unless strictly
necessary.
Adding one bookmark doesn't quite meet my gut feeling of neccessity.
Um... ...pretty please? :-)
--
/ Johan Sundström, http://ecmanaut.blogspot.com/
_______________________________________________
discuss mailing list
discuss@del.icio.us
http://lists.del.icio.us/cgi-bin/mailman/listinfo/discuss
--
joshua schachter
[EMAIL PROTECTED]
_______________________________________________
discuss mailing list
discuss@del.icio.us
http://lists.del.icio.us/cgi-bin/mailman/listinfo/discuss
