Nabble - Delicious (del.icio.us)

Re: API denies access to Yahoo-based accounts

2009-11-11T08:56:05Z

Well, after poking around to other developers' forums I've found that this is a known issue/disaster. The most interesting discussion seems to be here:

http://developer.yahoo.net/forum/index.php?showtopic=3065&st=0&gopid=9358

Re: API denies access to Yahoo-based accounts

2009-11-10T10:38:03Z

Indeed there is. We will be updating our help docs soon with the details, however to access data from accounts created using a Yahoo! ID, use the same API's as you would normally, below, but change the path to /v2, and make HTTP requests using OAuth as provided by the Yahoo! Developer Network.

http://developer.yahoo.com/oauth/

Chris

--- In ydn-delicious@..., Jerry Krinock <jerry@...> wrote:

>
> I'm not sure how long this feature has been available, but I note that
> now, when joining Delicious, the user can first sign into their Yahoo!
> account and then create a Delicious account "within" their Yahoo!
> account, signing in with their Yahoo! ID. This morning I created such
> an account.
>
> However, such an account does not seem to be accessible using the
> Delicious API, and this breaks my application.
>
> For example, if I sign in to a regular (pre-Yahoo!) Delicious account,
> everything works:
>
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:PASSWORD https://api.del.icio.us/v1/posts/update
> <?xml version="1.0" encoding="UTF-8"?>
> <update time="2009-10-10T13:45:29Z" inboxnew="0"/>
> 
>
> But if I try to sign in using the account name that I chose after
> signing into Yahoo! this morning, access is denied:
>
> Jerrys-Mac-Mini:~ jk$ curl -ujerryYahoo:PASSWORD https://api.del.icio.us/v1/posts/update
> <?xml version="1.0" standalone="yes"?>
> <result code="access denied" />
> 
>
> The same thing happens if I use my Yahoo! ID instead:
>
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:PASSWORD https://api.del.icio.us/v1/posts/update
> <?xml version="1.0" standalone="yes"?>
> <result code="access denied" />
> 
>
> I hope there is a solution for this!
>
> Sincerely,
>
> Jerry Krinock
>

API denies access to Yahoo-based accounts

2009-11-09T16:30:05Z

I'm not sure how long this feature has been available, but I note that now, when joining Delicious, the user can first sign into their Yahoo! account and then create a Delicious account "within" their Yahoo! account, signing in with their Yahoo! ID. This morning I created such an account.

However, such an account does not seem to be accessible using the Delicious API, and this breaks my application.

For example, if I sign in to a regular (pre-Yahoo!) Delicious account, everything works:

Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-10-10T13:45:29Z" inboxnew="0"/>


But if I try to sign in using the account name that I chose after signing into Yahoo! this morning, access is denied:

Jerrys-Mac-Mini:~ jk$ curl -ujerryYahoo:PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" standalone="yes"?>
<result code="access denied" />


The same thing happens if I use my Yahoo! ID instead:

Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" standalone="yes"?>
<result code="access denied" />


I hope there is a solution for this!

Sincerely,

Jerry Krinock

API denies access to Yahoo-based accounts

2009-11-08T11:37:06Z

I'm not sure how long this feature has been available, but I note that
now, when joining Delicious, the user can first sign into their Yahoo!
account and then create a Delicious account "within" their Yahoo!
account, signing in with their Yahoo! ID. This morning I created such
an account.

However, such an account does not seem to be accessible using the
Delicious API, and this breaks my application.

For example, if I sign in to a regular (pre-Yahoo!) Delicious account,
everything works:

Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-10-10T13:45:29Z" inboxnew="0"/>


But if I try to sign in using the account name that I chose after
signing into Yahoo! this morning, access is denied:

Jerrys-Mac-Mini:~ jk$ curl -ujerryYahoo:PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" standalone="yes"?>
<result code="access denied" />


The same thing happens if I use my Yahoo! ID instead:

Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" standalone="yes"?>
<result code="access denied" />


I hope there is a solution for this!

Sincerely,

Jerry Krinock

Re: Re: Latest Policy on API posts/all request frequency?

2009-09-29T18:35:00Z

On 2009 Sep 27, at 18:46, Chris Draycott wrote:

> but in the case of Delicious you should actually be getting a 500
> http status code (I checked our logs, and that's what we're logging,
> at least)...

> Hope this helps

Yes, that helps, Chris. Indeed, posts/all is rarely sent, but I'll
study using the "start" and "results" parameters. It would be nice to
download in chunks so that I can display progress information.

Just for your information, though, here is a console transcript
showing the 999 responses (not 500). You see I requested posts/all
six times, by hitting the up-arrow and return keys. The first four
requests produced 200 responses, then after that, I started getting
999. Actual data output was sent to /dev/null, and I replaced out my
actual password before pasting.

Thank you,

Jerry

Jerrys-Mac-Mini: jk$ curl -ujerrykrinock4:myPassword -w "Received HTTP
Status Code: %{http_code}\n" -o "/dev/null" https://api.del.icio.us/v1/posts/all
% Total % Received % Xferd Average Speed Time Time
Time Current
Dload Upload Total Spent
Left Speed
100 914 0 914 0 0 1252 0 --:--:-- --:--:--
--:--:-- 0
Received HTTP Status Code: 200
Jerrys-Mac-Mini: jk$ curl -ujerrykrinock4:myPassword -w "Received HTTP
Status Code: %{http_code}\n" -o "/dev/null" https://api.del.icio.us/v1/posts/all
% Total % Received % Xferd Average Speed Time Time
Time Current
Dload Upload Total Spent
Left Speed
100 914 0 914 0 0 1362 0 --:--:-- --:--:--
--:--:-- 0
Received HTTP Status Code: 200
Jerrys-Mac-Mini: jk$ curl -ujerrykrinock4:myPassword -w "Received HTTP
Status Code: %{http_code}\n" -o "/dev/null" https://api.del.icio.us/v1/posts/all
% Total % Received % Xferd Average Speed Time Time
Time Current
Dload Upload Total Spent
Left Speed
100 914 0 914 0 0 1416 0 --:--:-- --:--:--
--:--:-- 0
Received HTTP Status Code: 200
Jerrys-Mac-Mini: jk$ curl -ujerrykrinock4:myPassword -w "Received HTTP
Status Code: %{http_code}\n" -o "/dev/null" https://api.del.icio.us/v1/posts/all
% Total % Received % Xferd Average Speed Time Time
Time Current
Dload Upload Total Spent
Left Speed
100 914 0 914 0 0 1408 0 --:--:-- --:--:--
--:--:-- 0
Received HTTP Status Code: 200
Jerrys-Mac-Mini: jk$ curl -ujerrykrinock4:myPassword -w "Received HTTP
Status Code: %{http_code}\n" -o "/dev/null" https://api.del.icio.us/v1/posts/all
% Total % Received % Xferd Average Speed Time Time
Time Current
Dload Upload Total Spent
Left Speed
100 4233 0 4233 0 0 6838 0 --:--:-- --:--:--
--:--:-- 217k
Received HTTP Status Code: 999
Jerrys-Mac-Mini: jk$ curl -ujerrykrinock4:myPassword -w "Received HTTP
Status Code: %{http_code}\n" -o "/dev/null" https://api.del.icio.us/v1/posts/all
% Total % Received % Xferd Average Speed Time Time
Time Current
Dload Upload Total Spent
Left Speed
100 4233 0 4233 0 0 6712 0 --:--:-- --:--:--
--:--:-- 217k
Received HTTP Status Code: 999
Jerrys-Mac-Mini: jk$

Re: Latest Policy on API posts/all request frequency?

2009-09-27T18:46:14Z

Hi Jerry,

I'll do my best to answer your problem :)
First of all, the 999 is the Yahoo-wide response code for this type of rate limiting in the message, but in the case of Delicious you should actually be getting a 500 http status code (I checked our logs, and that's what we're logging, at least). Still, as you point out, the docs say 503, and it's not that. While 500 does not quite meet the exact definition of what we're doing, we use 503 for other cases and wanted to have a distinct code to allow them to be differentiated.

As for the rate at which you can hit posts/all, which I can't give you the exact details because they are always open to tweaking depending on abuse vectors etc, I would say that posts/all as a raw query should be avoided wherever possible. If, however, you request from that api using "results" parameter (probably in conjunction with "start") you can make many more requests. Depending on what you're trying to do, I would suggest that results=100 is probably a reasonable query, and the "paginate" until you get all the results.For most users, this will only take a few queries to get the whole collection.

Hope this helps
Chris

--- In ydn-delicious@..., Jerry Krinock <jerry@...> wrote:

>
> I have designed my application to prevent a user from requesting posts/
> all to often and being banned or throttled. Of course, this does not
> happen very often to a real user, because my application caches the
> data and checks with posts/update, doing posts/all only when needed.
> But it can happen if the user does certain things, and of course I can
> inadvertently send lots of posts/all during development :(
>
> A couple years ago, I noted that if I sent posts/all more frequently
> than once a minute, I would get a 503 response code and, apparently,
> my IP address would be banned for a couple hours. This has now changed.
>
> Even sending posts/all less frequently than once every 3 minutes, I
> can still get banned, although now it appears to be for only five
> minutes or so. Another thing different is that instead of getting a
> 503 response code, I get a 999 response code and a web page saying
> "We're sorry, we couldn't complete your request right now."
>
> So, if someone could please tell me what the latest policy is I'd be
> happy to design for it, with plenty of margin.
>
> Also, is it true that the "You've been sending too many posts/all"
> response is now 999 instead of 503? The documentation still looks the
> same as it did two years ago, implying that throttling is indicated by
> a 503...
>
> http://delicious.com/help/api
>
> Thanks,
>
> Jerry Krinock
>
> P.S. For future reference, I believe that a 4xx Client Error would be
> more appropriate than 999.
>
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
>
> According to the last paragraph in sec 6.1.1,
>
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6.1
>
> the Status Codes are supposed to be "extensible". I guess that means
> you could make up your own, maybe 450 or something. 999 looks like
> not a lot of thought went into it ;)
>

Latest Policy on API posts/all request frequency?

2009-09-25T18:27:37Z

I have designed my application to prevent a user from requesting posts/
all to often and being banned or throttled. Of course, this does not
happen very often to a real user, because my application caches the
data and checks with posts/update, doing posts/all only when needed.
But it can happen if the user does certain things, and of course I can
inadvertently send lots of posts/all during development :(

A couple years ago, I noted that if I sent posts/all more frequently
than once a minute, I would get a 503 response code and, apparently,
my IP address would be banned for a couple hours. This has now changed.

Even sending posts/all less frequently than once every 3 minutes, I
can still get banned, although now it appears to be for only five
minutes or so. Another thing different is that instead of getting a
503 response code, I get a 999 response code and a web page saying
"We're sorry, we couldn't complete your request right now."

So, if someone could please tell me what the latest policy is I'd be
happy to design for it, with plenty of margin.

Also, is it true that the "You've been sending too many posts/all"
response is now 999 instead of 503? The documentation still looks the
same as it did two years ago, implying that throttling is indicated by
a 503...

http://delicious.com/help/api

Thanks,

Jerry Krinock

P.S. For future reference, I believe that a 4xx Client Error would be
more appropriate than 999.

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

According to the last paragraph in sec 6.1.1,

http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6.1

the Status Codes are supposed to be "extensible". I guess that means
you could make up your own, maybe 450 or something. 999 looks like
not a lot of thought went into it ;)

Had to delete account to delete all bookmarks; now username's unavailable

2009-06-21T11:55:02Z

Delicious Support may know me as the person who's been struggling for years to import my bookmarks into Delicious.

This message states that the import bug has finally been fixed:

http://support.delicious.com/forum/comments.php?DiscussionID=2384&page=1#Comment_12233

But now, in order to re-import all my bookmarks, I had to delete my account and create a new one as I'd done before. (Why you don't have batch bookmark delete I don't know.)

A day later, and my username (fjordaan) is still not available. And I can't post on the Delicious forums as I don't have an account anymore.

Will it ever become available?

francois

Re: API posts/update often returns no response

2009-04-30T17:16:37Z

Hi Chris Draycott,

I am working on a project for a class. I attempted to download bookmark
data as a JSON feed. I received the same error as described in this thread.
The response I received from the url was the following:



I verified that my code works with other feeds. So, I guess the problem
others experienced has reappeared. If you could help me with this, I would
greatly appreciate it.

Thanks,

progmanos

--- In ydn-delicious@..., "chris_draycott" <draycott@...> wrote:

>
> Hi,
>
> This server was having some problems it seems, so we've removed it. Things should be back to normal. Apologies for the inconvenience, and thanks for reporting it.
>
> Chris
> --- In ydn-delicious@..., Luis de la Rosa <luis@> wrote:
> >
> > Hi again,
> >
> > I looked into this and it does indeed happen with "posts/update". It
> > is still happening frequently.
> >
> > It seems to just return most of the time:
> >
> > 
> >
> > Also it does not seem to be returning a 500 error when it does this.
> >
> > This confirms what Jerry found previously.
> >
> > It appears that the only reliable way to get around this is to call
> > "posts/update" and then try again soon afterwards. If you back off
> > for another 30 minutes, then you will likely get this problem again.
> >
> > This is affecting the users of my app WebnoteHappy. I could issue a
> > fix that calls "posts/update" twice in quick succession, but this does
> > not seem like a good long term solution.
> >
> > Any suggestions?
> >
> > Thanks,
> > Louie
> > Happy Apps
> >
> > On Mar 5, 2009, at 12:39 PM, chris_draycott wrote:
> >
> > > Hi all,
> > >
> > > Looks like there might be some problems on our side here.
> > > In the case where you get no xml response back you should be getting
> > > an HTTP response code of 500, but I agree that is not ideal (some
> > > xml that you can see and parse would be much better). We're working
> > > on changing that.
> > >
> > > In addition, we've ironed out some other issues and while you still
> > > might get this empty response, it should be much less frequent now.
> > >
> > > Chris
> > >
> > > --- In ydn-delicious@..., Luis de la Rosa <luis@>
> > > wrote:
> > > >
> > > > I have been experiencing similar issues with XML sometimes not being
> > > > returned. I think it is with the call "posts/all". This seems to
> > > > have started yesterday March 4th. I haven't traced it to a
> > > particular
> > > > server.
> > > >
> > > > Thanks,
> > > > Louie
> > > > Happy Apps
> > > >
> > > > On Mar 5, 2009, at 1:21 AM, Jerry Krinock wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I was doing some testing tonight and found that the API requests
> > > > > "posts/update" were often not giving me any XML. Further testing
> > > > > showed that it's most like to fail if I wait a few minutes -- the
> > > > > first response I get has no XML. But subsequent requests sent
> > > > > immediately this tend to succeed.
> > > > >
> > > > > In the following run of 14 posts/update requests made via curl,
> > > note
> > > > > that numbers 1 and 11 failed. The others succeeded.
> > > > >
> > > > > It seems that the failures always occur with server fe07, but
> > > > > sometimes fe07 works. Is something broken in Yahoo!-land?
> > > > >
> > > > > Jerry Krinock
> > > > >
> > > > > FAILED:
> > > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > > 
> > > > >
> > > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > > 
> > > > >
> > > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > > 
> > > > >
> > > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > > 
> > > > >
> > > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > > 
> > > > >
> > > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > > 
> > > > >
> > > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > > 
> > > > >
> > > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > > 
> > > > >
> > > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > > 
> > > > >
> > > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > > 
> > > > >
> > > > > FAILED:
> > > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > > 
> > > > >
> > > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > > 
> > > > >
> > > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > > 
> > > > >
> > > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > > 
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> > >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>

Re: API posts/update often returns no response

2009-04-30T16:17:38Z

Hi Chris Draycott,

I am working on a project for a class. I attempted to download bookmark data as a JSON feed. I received the same error as described in this thread. The response I received from the url was the following:



I verified that my code works with other feeds. So, I guess the problem others experienced has reappeared. If you could help me with this, I would greatly appreciate it.

Thanks,

progmanos

Chris Draycott wrote:

Hi,

This server was having some problems it seems, so we've removed it. Things should be back to normal. Apologies for the inconvenience, and thanks for reporting it.

Chris
--- In ydn-delicious@yahoogroups.com, Luis de la Rosa <luis@...> wrote:
>
> Hi again,
>
> I looked into this and it does indeed happen with "posts/update". It
> is still happening frequently.
>
> It seems to just return most of the time:
>
> 
>
> Also it does not seem to be returning a 500 error when it does this.
>
> This confirms what Jerry found previously.
>
> It appears that the only reliable way to get around this is to call
> "posts/update" and then try again soon afterwards. If you back off
> for another 30 minutes, then you will likely get this problem again.
>
> This is affecting the users of my app WebnoteHappy. I could issue a
> fix that calls "posts/update" twice in quick succession, but this does
> not seem like a good long term solution.
>
> Any suggestions?
>
> Thanks,
> Louie
> Happy Apps
>
> On Mar 5, 2009, at 12:39 PM, chris_draycott wrote:
>
> > Hi all,
> >
> > Looks like there might be some problems on our side here.
> > In the case where you get no xml response back you should be getting
> > an HTTP response code of 500, but I agree that is not ideal (some
> > xml that you can see and parse would be much better). We're working
> > on changing that.
> >
> > In addition, we've ironed out some other issues and while you still
> > might get this empty response, it should be much less frequent now.
> >
> > Chris
> >
> > --- In ydn-delicious@yahoogroups.com, Luis de la Rosa <luis@>
> > wrote:
> > >
> > > I have been experiencing similar issues with XML sometimes not being
> > > returned. I think it is with the call "posts/all". This seems to
> > > have started yesterday March 4th. I haven't traced it to a
> > particular
> > > server.
> > >
> > > Thanks,
> > > Louie
> > > Happy Apps
> > >
> > > On Mar 5, 2009, at 1:21 AM, Jerry Krinock wrote:
> > >
> > > > Hi,
> > > >
> > > > I was doing some testing tonight and found that the API requests
> > > > "posts/update" were often not giving me any XML. Further testing
> > > > showed that it's most like to fail if I wait a few minutes -- the
> > > > first response I get has no XML. But subsequent requests sent
> > > > immediately this tend to succeed.
> > > >
> > > > In the following run of 14 posts/update requests made via curl,
> > note
> > > > that numbers 1 and 11 failed. The others succeeded.
> > > >
> > > > It seems that the failures always occur with server fe07, but
> > > > sometimes fe07 works. Is something broken in Yahoo!-land?
> > > >
> > > > Jerry Krinock
> > > >
> > > > FAILED:
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > FAILED:
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
>
>
>
> [Non-text portions of this message have been removed]
>

Re: Tired of tag list, try visual bookmarking

2009-04-28T21:04:01Z

Cool features, the visual mapping is definitely a plus

stetoscope wrote:

Peartlrees is a free social service that let you create the living map of the web. In pearltrees you will make maps to :
1. Organize your web (best than with bookmarks)
2. Guide your friends through the web (More easily than with usual services)
3. Broaden your web horizon by navigating on the maps that will cross yours

www.pearltrees.com

Tired of tag list, try visual bookmarking

2009-04-10T07:21:59Z

Peartlrees is a free social service that let you create the living map of the web. In pearltrees you will make maps to :
1. Organize your web (best than with bookmarks)
2. Guide your friends through the web (More easily than with usual services)
3. Broaden your web horizon by navigating on the maps that will cross yours

www.pearltrees.com

need beta testers

2009-03-23T13:41:01Z

Hi,

Its been a while we catched up. Whats up with you?

I started this service, www.RemindMeSam.com, in my free time, and am looking for beta
testers.

Can you please mail me the email address of a few contacts of yours in US who might be interested?
4-5 of them can really make my day :-)

Thanks in advance

--

Amit Upadhyay

[Non-text portions of this message have been removed]

hi

2009-03-21T08:13:40Z

Hey,

Checkout www.RemindMeSam.com .

--

Amit Upadhyay

Via - www.remindmesam.com

[Non-text portions of this message have been removed]

Re: Importing Powermarks into Delicious

2009-03-10T15:05:12Z

Hi Rocco,

> ADD_DATE is correct. We have a known problem with really early
> ADD_DATEs that should be fixed in the next few weeks.

So I don't need to do anything but wait?

After importing, a large number of my bookmarks ended up with the date 31 Dec 2002, and none older than that. (I have 2256 bookmarks older than that, dating back to October 2000.)

I'd really appreciate an email when this issue is fixed, since I don't always read the ydn-delicious digests.

francois

Re: API posts/update often returns no response

2009-03-10T09:14:06Z

Hi,

This server was having some problems it seems, so we've removed it. Things should be back to normal. Apologies for the inconvenience, and thanks for reporting it.

Chris
--- In ydn-delicious@..., Luis de la Rosa <luis@...> wrote:

>
> Hi again,
>
> I looked into this and it does indeed happen with "posts/update". It
> is still happening frequently.
>
> It seems to just return most of the time:
>
> 
>
> Also it does not seem to be returning a 500 error when it does this.
>
> This confirms what Jerry found previously.
>
> It appears that the only reliable way to get around this is to call
> "posts/update" and then try again soon afterwards. If you back off
> for another 30 minutes, then you will likely get this problem again.
>
> This is affecting the users of my app WebnoteHappy. I could issue a
> fix that calls "posts/update" twice in quick succession, but this does
> not seem like a good long term solution.
>
> Any suggestions?
>
> Thanks,
> Louie
> Happy Apps
>
> On Mar 5, 2009, at 12:39 PM, chris_draycott wrote:
>
> > Hi all,
> >
> > Looks like there might be some problems on our side here.
> > In the case where you get no xml response back you should be getting
> > an HTTP response code of 500, but I agree that is not ideal (some
> > xml that you can see and parse would be much better). We're working
> > on changing that.
> >
> > In addition, we've ironed out some other issues and while you still
> > might get this empty response, it should be much less frequent now.
> >
> > Chris
> >
> > --- In ydn-delicious@..., Luis de la Rosa <luis@>
> > wrote:
> > >
> > > I have been experiencing similar issues with XML sometimes not being
> > > returned. I think it is with the call "posts/all". This seems to
> > > have started yesterday March 4th. I haven't traced it to a
> > particular
> > > server.
> > >
> > > Thanks,
> > > Louie
> > > Happy Apps
> > >
> > > On Mar 5, 2009, at 1:21 AM, Jerry Krinock wrote:
> > >
> > > > Hi,
> > > >
> > > > I was doing some testing tonight and found that the API requests
> > > > "posts/update" were often not giving me any XML. Further testing
> > > > showed that it's most like to fail if I wait a few minutes -- the
> > > > first response I get has no XML. But subsequent requests sent
> > > > immediately this tend to succeed.
> > > >
> > > > In the following run of 14 posts/update requests made via curl,
> > note
> > > > that numbers 1 and 11 failed. The others succeeded.
> > > >
> > > > It seems that the failures always occur with server fe07, but
> > > > sometimes fe07 works. Is something broken in Yahoo!-land?
> > > >
> > > > Jerry Krinock
> > > >
> > > > FAILED:
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > FAILED:
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > > 
> > > >
> > > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
>
>
>
> [Non-text portions of this message have been removed]
>

Re: Re: API posts/update often returns no response

2009-03-09T21:05:49Z

On 2009 Mar 05, at 09:39, chris_draycott wrote:

> Looks like there might be some problems on our side here.
> In the case where you get no xml response back you should be getting
> an HTTP response code of 500, but I agree that is not ideal (some
> xml that you can see and parse would be much better). We're working
> on changing that.

Well, if it would give me some useful information which I could
display to the user regarding why it failed, that would be
worthwhile. But if it's just going to say "Sorry, request could not
handled", well, 500 is good enough. And it doesn't require me to add
any more code to my app :))

> In addition, we've ironed out some other issues and while you still
> might get this empty response, it should be much less frequent now.

It seems about the same to me, Chris. Server fe07 is still the
culprit. I just ran another test and got:

Server fe07 Worked properly: 1/4 Score: 25%
Other servers Worked properly: 5/5 Score: 100%

The test is very easy to do....

Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T22:35:43Z" inboxnew="0"/>


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T22:35:43Z" inboxnew="0"/>


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T22:35:43Z" inboxnew="0"/>


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T22:35:43Z" inboxnew="0"/>


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T22:35:43Z" inboxnew="0"/>


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T22:35:43Z" inboxnew="0"/>

Re: Re: API posts/update often returns no response

2009-03-09T20:26:37Z

Hi again,

I looked into this and it does indeed happen with "posts/update". It
is still happening frequently.

It seems to just return most of the time:



Also it does not seem to be returning a 500 error when it does this.

This confirms what Jerry found previously.

It appears that the only reliable way to get around this is to call
"posts/update" and then try again soon afterwards. If you back off
for another 30 minutes, then you will likely get this problem again.

This is affecting the users of my app WebnoteHappy. I could issue a
fix that calls "posts/update" twice in quick succession, but this does
not seem like a good long term solution.

Any suggestions?

Thanks,
Louie
Happy Apps

On Mar 5, 2009, at 12:39 PM, chris_draycott wrote:

> Hi all,
>
> Looks like there might be some problems on our side here.
> In the case where you get no xml response back you should be getting
> an HTTP response code of 500, but I agree that is not ideal (some
> xml that you can see and parse would be much better). We're working
> on changing that.
>
> In addition, we've ironed out some other issues and while you still
> might get this empty response, it should be much less frequent now.
>
> Chris
>
> --- In ydn-delicious@..., Luis de la Rosa <luis@...>
> wrote:
> >
> > I have been experiencing similar issues with XML sometimes not being
> > returned. I think it is with the call "posts/all". This seems to
> > have started yesterday March 4th. I haven't traced it to a
> particular
> > server.
> >
> > Thanks,
> > Louie
> > Happy Apps
> >
> > On Mar 5, 2009, at 1:21 AM, Jerry Krinock wrote:
> >
> > > Hi,
> > >
> > > I was doing some testing tonight and found that the API requests
> > > "posts/update" were often not giving me any XML. Further testing
> > > showed that it's most like to fail if I wait a few minutes -- the
> > > first response I get has no XML. But subsequent requests sent
> > > immediately this tend to succeed.
> > >
> > > In the following run of 14 posts/update requests made via curl,
> note
> > > that numbers 1 and 11 failed. The others succeeded.
> > >
> > > It seems that the failures always occur with server fe07, but
> > > sometimes fe07 works. Is something broken in Yahoo!-land?
> > >
> > > Jerry Krinock
> > >
> > > FAILED:
> > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > 
> > >
> > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > 
> > >
> > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > 
> > >
> > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > 
> > >
> > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > 
> > >
> > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > 
> > >
> > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > 
> > >
> > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > 
> > >
> > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > 
> > >
> > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > 
> > >
> > > FAILED:
> > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > 
> > >
> > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > 
> > >
> > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > 
> > >
> > > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > > 
> > >
> > >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>

[Non-text portions of this message have been removed]

Re: Re: Importing Powermarks into Delicious

2009-03-09T17:17:05Z

ADD_DATE is correct. We have a known problem with really early
ADD_DATEs that should be fixed in the next few weeks.

--
Rocco Caputo - Delicious

On Mar 9, 2009, at 19:39, fjordaan2000 wrote:

> Hi Rocco, James,
>
> Thanks for the advice -- a few regular expressions later, and my
> bookmarks imported with the tags successfully preserved.
>
> Just one more problem. It seems to have used the wrong date field.
> Powermarks has the following 3 date fields:
>
> ADD_DATE="972230504" LAST_VISIT="972230504" LAST_MODIFIED="1188335016"
>
> Where Add Date is all I care about, and the above number should be
> equivalent to 2000-10-22
>
> After importing, the bookmark in question shows a date of 31 Dec
> 2002 instead, which I assume is one of the other fields.
>
> What should I rename ADD_DATE to? Or should I just delete the others?
>
> I'll have to delete my account and re-import everything (why is the
> batch delete function so feeble?), but I really want the dates to be
> correct.
>
> francois
>
>
>

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ydn-delicious/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/ydn-delicious/join
(Yahoo! ID required)

<*> To change settings via email:
mailto:ydn-delicious-digest@...
mailto:ydn-delicious-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
ydn-delicious-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

Re: Importing Powermarks into Delicious

2009-03-09T16:39:12Z

Hi Rocco, James,

Thanks for the advice -- a few regular expressions later, and my bookmarks imported with the tags successfully preserved.

Just one more problem. It seems to have used the wrong date field. Powermarks has the following 3 date fields:

ADD_DATE="972230504" LAST_VISIT="972230504" LAST_MODIFIED="1188335016"

Where Add Date is all I care about, and the above number should be equivalent to 2000-10-22

After importing, the bookmark in question shows a date of 31 Dec 2002 instead, which I assume is one of the other fields.

What should I rename ADD_DATE to? Or should I just delete the others?

I'll have to delete my account and re-import everything (why is the batch delete function so feeble?), but I really want the dates to be correct.

francois

Re: API posts/update often returns no response

2009-03-05T09:39:47Z

Hi all,

Looks like there might be some problems on our side here.
In the case where you get no xml response back you should be getting an HTTP response code of 500, but I agree that is not ideal (some xml that you can see and parse would be much better). We're working on changing that.

In addition, we've ironed out some other issues and while you still might get this empty response, it should be much less frequent now.

Chris

--- In ydn-delicious@..., Luis de la Rosa <luis@...> wrote:

>
> I have been experiencing similar issues with XML sometimes not being
> returned. I think it is with the call "posts/all". This seems to
> have started yesterday March 4th. I haven't traced it to a particular
> server.
>
> Thanks,
> Louie
> Happy Apps
>
> On Mar 5, 2009, at 1:21 AM, Jerry Krinock wrote:
>
> > Hi,
> >
> > I was doing some testing tonight and found that the API requests
> > "posts/update" were often not giving me any XML. Further testing
> > showed that it's most like to fail if I wait a few minutes -- the
> > first response I get has no XML. But subsequent requests sent
> > immediately this tend to succeed.
> >
> > In the following run of 14 posts/update requests made via curl, note
> > that numbers 1 and 11 failed. The others succeeded.
> >
> > It seems that the failures always occur with server fe07, but
> > sometimes fe07 works. Is something broken in Yahoo!-land?
> >
> > Jerry Krinock
> >
> > FAILED:
> > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > 
> >
> > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > <?xml version="1.0" encoding="UTF-8"?>
> > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > 
> >
> > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > <?xml version="1.0" encoding="UTF-8"?>
> > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > 
> >
> > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > <?xml version="1.0" encoding="UTF-8"?>
> > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > 
> >
> > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > <?xml version="1.0" encoding="UTF-8"?>
> > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > 
> >
> > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > <?xml version="1.0" encoding="UTF-8"?>
> > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > 
> >
> > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > <?xml version="1.0" encoding="UTF-8"?>
> > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > 
> >
> > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > <?xml version="1.0" encoding="UTF-8"?>
> > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > 
> >
> > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > <?xml version="1.0" encoding="UTF-8"?>
> > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > 
> >
> > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > <?xml version="1.0" encoding="UTF-8"?>
> > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > 
> >
> > FAILED:
> > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > 
> >
> > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > <?xml version="1.0" encoding="UTF-8"?>
> > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > 
> >
> > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > <?xml version="1.0" encoding="UTF-8"?>
> > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > 
> >
> > Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> > <?xml version="1.0" encoding="UTF-8"?>
> > <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> > 
> >
> >
>
>
>
> [Non-text portions of this message have been removed]
>

Re: API posts/update often returns no response

2009-03-04T22:55:17Z

I have been experiencing similar issues with XML sometimes not being
returned. I think it is with the call "posts/all". This seems to
have started yesterday March 4th. I haven't traced it to a particular
server.

Thanks,
Louie
Happy Apps

On Mar 5, 2009, at 1:21 AM, Jerry Krinock wrote:

> Hi,
>
> I was doing some testing tonight and found that the API requests
> "posts/update" were often not giving me any XML. Further testing
> showed that it's most like to fail if I wait a few minutes -- the
> first response I get has no XML. But subsequent requests sent
> immediately this tend to succeed.
>
> In the following run of 14 posts/update requests made via curl, note
> that numbers 1 and 11 failed. The others succeeded.
>
> It seems that the failures always occur with server fe07, but
> sometimes fe07 works. Is something broken in Yahoo!-land?
>
> Jerry Krinock
>
> FAILED:
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> 
>
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> <?xml version="1.0" encoding="UTF-8"?>
> <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> 
>
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> <?xml version="1.0" encoding="UTF-8"?>
> <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> 
>
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> <?xml version="1.0" encoding="UTF-8"?>
> <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> 
>
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> <?xml version="1.0" encoding="UTF-8"?>
> <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> 
>
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> <?xml version="1.0" encoding="UTF-8"?>
> <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> 
>
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> <?xml version="1.0" encoding="UTF-8"?>
> <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> 
>
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> <?xml version="1.0" encoding="UTF-8"?>
> <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> 
>
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> <?xml version="1.0" encoding="UTF-8"?>
> <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> 
>
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> <?xml version="1.0" encoding="UTF-8"?>
> <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> 
>
> FAILED:
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> 
>
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> <?xml version="1.0" encoding="UTF-8"?>
> <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> 
>
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> <?xml version="1.0" encoding="UTF-8"?>
> <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> 
>
> Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
> <?xml version="1.0" encoding="UTF-8"?>
> <update time="2009-03-05T05:42:53Z" inboxnew="0"/>
> 
>
>

[Non-text portions of this message have been removed]

API posts/update often returns no response

2009-03-04T22:21:38Z

Hi,

I was doing some testing tonight and found that the API requests
"posts/update" were often not giving me any XML. Further testing
showed that it's most like to fail if I wait a few minutes -- the
first response I get has no XML. But subsequent requests sent
immediately this tend to succeed.

In the following run of 14 posts/update requests made via curl, note
that numbers 1 and 11 failed. The others succeeded.

It seems that the failures always occur with server fe07, but
sometimes fe07 works. Is something broken in Yahoo!-land?

Jerry Krinock

FAILED:
Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T05:42:53Z" inboxnew="0"/>


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T05:42:53Z" inboxnew="0"/>


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T05:42:53Z" inboxnew="0"/>


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T05:42:53Z" inboxnew="0"/>


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T05:42:53Z" inboxnew="0"/>


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T05:42:53Z" inboxnew="0"/>


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T05:42:53Z" inboxnew="0"/>


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T05:42:53Z" inboxnew="0"/>


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T05:42:53Z" inboxnew="0"/>


FAILED:
Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T05:42:53Z" inboxnew="0"/>


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T05:42:53Z" inboxnew="0"/>


Jerrys-Mac-Mini:~ jk$ curl -ujerrykrinock:MY_PASSWORD https://api.del.icio.us/v1/posts/update
<?xml version="1.0" encoding="UTF-8"?>
<update time="2009-03-05T05:42:53Z" inboxnew="0"/>

Re: Re: Importing Powermarks into Delicious

2009-03-04T20:01:33Z

Hi, Francois.

Delicious looks for tags separated by commas in bookmarks.html. If
you have three tags, "this one", "that one" and "the other" (without
the quotes), then your bookmark would look something like this:

<A HREF="http://example.com/" ...
TAGS="this_one,that_one,the_other" ...>Example Bookmark!</A>

You can see more examples by bookmarking something in Delicious with
more than one tag, then exporting your Delicious bookmarks.

I hope this helps.

--
Rocco Caputo - Delicious

On Mar 4, 2009, at 19:04, fjordaan2000 wrote:
>
> So, I still have a problem. Netvouz claims to export bookmarks in
> Delicious-compatible format, but when I attempted to import that
> into Delicious, the tags get messed up (connected with
> underscores), probably due to bad markup in the bookmark file. I
> could probably fix it myself if I knew what it needed to look like.

Re: Importing Powermarks into Delicious

2009-03-04T16:04:33Z

Hi James,

Bravo. I was one of those unlucky souls who spent years begging Kaylon and Yahoo [1] and the lazyweb in general to create a Powermarks-Delicious importer. (I think -- and suggested -- Kaylon could've extended Powermarks' lifespan as a product by updating it to sync to Delicious, but to no avail.)

[1] http://tech.groups.yahoo.com/group/ydn-delicious/message/215

You seem to have succeeded where I failed. It looks like your method loses the bookmark creation date, however, which I considered of vital importance.

What I ended up doing was to import my bookmarks into Netvouz.com, a lower-tier online bookmarking service, whose creator wrote a Powermarks importer. (Why couldn't Delicious?) This has served me well enough over the last 2 years, but it's not being actively developed, doesn't have an API, so I still would prefer being on Delicious.

So, I still have a problem. Netvouz claims to export bookmarks in Delicious-compatible format, but when I attempted to import that into Delicious, the tags get messed up (connected with
underscores), probably due to bad markup in the bookmark file. I could probably fix it myself if I knew what it needed to look like.

Delicious "customer care" has been hopeless. I have asked them to provide me with an example of correct markup for a Delicious bookmark, but I've never received anything back except boilerplate "We have escalated this to our Engineering Department and hope that it will be resolved soon."

Anyway, I realise this is somewhat irrelevant to your original post. But do you, by any chance, have an example of bookmark HTML that Delicious imports correctly?

Regards,

francois

Importing Powermarks into Delicious

2009-03-03T16:53:27Z

This is an answer to the many posts on how to import Powermarks into Delicious. I searched the web, contacted the author of Powermarks and could find no way to do it.

I had the same issue and I manually found a way to get Powermarks bookmarks imported into Delicious using only Microsoft Excel. It should take you less than 30 minutes to it.

Steps to import Powermarks into Delicious.com using Microsoft Excel 2003

1. Put a bookmark in Delicious and export bookmark file from Delicious by going under settings then Export / Backup Bookmarks.
2. Export bookmarks from Powermarks under File -> export as type delimited ASCII.
3. Open the exported Powermarks text file in Excel.
4. Put columns in order of url, keywords, then title and delete all remaining columns.
5. Setup the Excel sheet with the following columns to mimic the exported Delicious file format. Copy and paste the test string following each column name into the first cell of each column then copy and paste that cell all the way down the column to the last row of your bookmarks. (The text is exact after the Column letters and spaces with the red lines as the original data columns from Powermarks):
Column A <DL><p><DT><A HREF="
Column B The url field
Column C " TAGS="
Column D The keywords field
Column E ">
Column F The bookmark name field
Column G </A></DL><p>

6. Select keywords column and go under Edit -> replace put a space in the find what field and a comma in the replace with field. This will put commas in the place of all the spaces in between the keywords.
7. Press ctrl-a to select whole sheet and go under Data -> filter -> autofilter . Open the filter cell in the first row of the url column. Select custom and do contains file: Then delete all those rows to get rid of the file bookmarks.
8. Do ctrl-a to select whole sheet then ctrl-c to copy then open notepad.exe and ctrl-v to paste sheet.
9. In notepad highlight and copy one of the tab characters placed in the rows as field separators, then go under edit and replace and paste the tab character in the find what field and hit replace all to get rid of the tab delimiters.
10. Copy top part of Delicious export file before first <DL><p><DT> line and paste into top of Powermarks notepad file, change both instances of the word bookmarks to Powermarks. Make sure all format exactly matches original Delicious download file.
11. Save the notepad file as powermarks.htm
12. Go in delicious.com, go under settings and Import / Upload Bookmarks. At the bottom select manual import. Delete "imported" out of tag field and hit Import Now.
13. You should get a success statement and your bookmarks should now begin showing up under bookmarks.

Re: Daily Blog Posting

2009-02-27T02:09:45Z

averatec laptop 6100 battery

asus laptop battery

Re: How can I import Furl bookmarks with the keywords becoming tags in del.icio.us?

2009-01-26T03:35:58Z

If you still have this problem and know a little bit about C#, this tool http://chopeen.blogspot.com/2009/01/furl2delicious-tool-to-import-bookmarks.html can help you.

gregor_utm wrote:

I would like to import my Furl bookmarks into del.icio.us. I used the
keywords field in Furl for extensively tagging my bookmarks and, of
course, I would now like to get these transferred to del.icio.us as
well. The only export format that really exports all information
including the keywords and not just the topics field for example is
the Furl XML format.
Is there any way how I can import this into del.icio.us?

Re: policy on advertising

2008-12-18T01:32:48Z

Hi Matthew,

Thanks for bringing this to our attention. We consider this spam, and we
try to ferret it out before it shows up and bothers people, but we
sometimes miss a few things. You can always report suspicious stuff to
https://secure.delicious.com/help/abuse and we'll take care of it as
soon as possible.

Britta
Delicious community manager intern

--- In ydn-delicious@..., "mweymar" <matthew.weymar@...> wrote:

>
> If you look at
> http://delicious.com/tag/berlin+hotel
> you will see that a particular place was bookmarked 4 times on one day
> by 4 different users "who" have only one bookmark each, that one.
>
> This is clearly advertising.
>
> Is this explicitly allowed, or not allowed? If this is not allowed, do
> you make any effort to exclude this sort of practice?...
>
> I'm just curious. I have nothing against the Hotel 4 Youth.
>
> Thanks,
> Matthew
>

policy on advertising

2008-12-16T20:23:53Z

If you look at
http://delicious.com/tag/berlin+hotel
you will see that a particular place was bookmarked 4 times on one day
by 4 different users "who" have only one bookmark each, that one.

This is clearly advertising.

Is this explicitly allowed, or not allowed? If this is not allowed, do
you make any effort to exclude this sort of practice?...

I'm just curious. I have nothing against the Hotel 4 Youth.

Thanks,
Matthew

Re: Re: Deleting rarely visited or old bookmarks

2008-12-11T13:42:00Z

Hi,

Actually Delicious doesn't store any of that information. You'll
notice on the exported bookmarks file that the LAST_VISIT and the
ADD_DATE are exactly the same and are in fact the date you added the
bookmark.

If you can sort the order of your bookmarks by going to Sorted By and
clicking on "Most Recent" and then selecting "Reverse Sort". That'll
give display your first bookmarks at the top.

From there you can delete individual bookmarks but unfortunately you
will have to be the judge of whether you want them or not. If you are
lucky you maybe included within the Bulk Edit bucket test - some users
will see a "Bulk Edit (Beta)" in the top right tag menu - and then
delete (permanently ) in bulk.

I hope that helps.

- Davinder
Delicious Frontend
http://delicious.com/davindermahal

--- In ydn-delicious@..., "stephenbungert"
<stephenbungert@...> wrote: > > Of course they do, just export your
bookmarks and your see that they > log when you last visited them, and
any link you click on at delicious > could be logged by delicious,
including the time you spent on pages etc. > --- In ydn-delicious@...
, "stephenbungert" <stephenbungert@...> wrote:
>
> Of course they do, just export your bookmarks and your see that they
> log when you last visited them, and any link you click on at
delicious
> could be logged by delicious, including the time you spent on pages
etc.
>

Re: Deleting rarely visited or old bookmarks

2008-12-11T02:17:02Z

Of course they do, just export your bookmarks and your see that they
log when you last visited them, and any link you click on at delicious
could be logged by delicious, including the time you spent on pages etc.

--
Stephen Bungert

Call for study participation: a study on the use of Delicious

2008-11-23T15:55:42Z

Hello,
My name is Heejin Park. I am a PhD student at the School of Library,
Archival and Information Studies, University of British Columbia.
I am conducting a study to fulfill the research component of my
degree, and I am sending this note to ask for volunteers. In my
research, I am interested in the use of Delicious and looking for
participants who will share their experiences with the system.

The purpose of this study is to explore how you use Delicious in
order to access, share, and navigate Web information.
If you agree to participate in this study, I will ask you to complete
a Web questionnaire and to keep an electronic diary which records
your use of Delicious. The Web questionnaire and diary process will
take approximately two to three hours of your time over a one to two
week period.

Participation in this research is voluntary, and participants are
ensured confidentiality.
The completed questionnaire will be accessible only to the researcher
named below, and will be kept in strict confidence.
The Delicious user name on the questionnaire is for data management
purposes only. As soon as the responses are coded, information
linking data to respondent will be destroyed.

Please consider participating.
To show our appreciation for your participation in this study, you
will receive an honorarium in the amount of $20 in the form of an
Amazon.com gift card.
If you would like to participate, to support the research or because
you would like to help out a colleague, please respond to this email
address [papermod@...].
If you do not wish to participate, but can recommend someone who can
participate, please forward this message to that person.

If you decide to participate, I will email information that includes
a link to the questionnaire and a form of the electronic diaries, and
my contact information.
Please note that I have listed my e-mail account below. Do not
hesitate to ask any questions about the study.

Thank you very much.

Heejin Park
papermod@...

Principal Investigators
Edie Rasmussen, Professor
School of Library, Archival and Information Studies
University of British Columbia;

Joseph Tennis, Assistant Professor
The Information School of the University of Washington

Re: Deleting rarely visited or old bookmarks

2008-11-12T07:54:24Z

On Wed, Nov 05, 2008 at 01:34:52PM -0000,
stephenbungert <stephenbungert@...> wrote
a message of 399 lines which said:

> Is it possible view all bookmarks that I have only visited once or
> twice?

It seems the links displayed by del.icio.us from your bookmarks are
direct links to the target, they do not go through del.icio.us.

Therefore, del.icio.us has no way of knowing that you visited them or
not (which is probably a good thing, privacy-wise).

Deleting rarely visited or old bookmarks

2008-11-05T05:34:52Z

Is it possible view all bookmarks that I have only visited once or
twice? Or ones that are over a year old? Maybe even bookmarkes that
are over a year old and have not been visited?

Since starting using delicious my bookmarks have jumped from about 400
to over 1200, the first 400 took me years to accrue in Internet
Explorer, but I new what bookmarks I had and where they were.

In the last few months I have given up trying to use bundles, and just
search for what I want. Now I want to get rid of old or unused
bookmarks. Is there a way of doing this? I thought about starting a
new account, but I don't want to have to do that if there is an easier
way.

--
Stephen Bungert