Hi all,
We didn't develop any new feature from July/08 to October/08, but we did one thing: make diigo database scalable and easy to recover if something bad happened.
For back up strategy:

1) Real time backup for ever node of the distributed database( in several servers)
2) Dump the whole database and store it off site every month.

Don't worry about your data, it's safe in diigo :)

Hi Robert,
We will catch up all problems and issues within 1 day.

Gialloporpora did make a post in the group, but he is not a group member. However, the design is not good. We should allow users to filter posts no matter whether he/she is a group member.

Thanks.

We fixed some bugs in cache server and search server. Don't worry. Once your bookmark URL is in diigo system, we will try our best to fetch the cache page.

We will have more computation power soon.

Ok. We will make it as private.

Actually, I experienced the similar problem before. However, the system is URL centric and it's hard to solve the problem in current architecture. BTW, we're designing diigo 4.0 and will try to find a solution.

We are looking into this issue. BTW, you can work around it by bookmarking the URL from "My bookmark" page.

Hi Riyaz,
It's ok in Firefox. Did you experience the problem in Safari?

Hi Miroslav,
Currently, this feature is not available in diigo. However, we will evaluate it.

In Safari?

I can use both Tab Mix Plus(0.3.7.3) and Diigo Toolbar(3.1.6.13) in windows XP. Could you try a new profile in Unbuntu and only install Mix Plus(0.3.7.3) and Diigo Toolbar(3.1.6.13) to see whether they work together?

BTW, what's your browser theme?

Thanks

It's because we only claims support for FF3.1 in the install.rdf file which is in the extension.

Let's wait a beta version to see whether it's a firefox bug or diigo bug.

Hi Onesimusx,
Please check Firefox ==>Tools ==>Options ==> Privacy ==> Cookies ==> make sure Accept cookies from sites and Accept thrid-party cookies are checked.

Let me know if it is helpful. If not, could you zip and send your firefox profile to joel【at】diigo dot com? We'd like to help you out.

Thanks.

Hi All,
Here is why diigolet needs thrid-party cookie enabled: You don't need to login diigolet again when you restart your browser.

Hi all,

The problem was finally solved.

1. Diigolet uses cookies authroization if available (available means that 3rd party cookies are allowed)
2. If cookies are not available, diigolet gracefully falls back to http authorization.
3. The advantage of cookies auth over http auth is that your sign in status can be remembered so you don't have to type your username and password the next time you open the browser.

Hi Graham and Roar,
The whole backend system is URL based and it will bring much complexity and load to implement this feature. For example, it costs more computation power for EVERY page you visit to decide whether there are some synonym URLs. Suppose there are M users, every user visits N page a day, ever page costs extra e% computation power, It will add M*N*e% extra load to the system per day.

Hi all,
Thanks for your reporting and help. The CPU 100% problem was fixed. Please update the new version 1.1.6.13, Let me know whether it works for you.

Big thanks to Scott. Without his profile, it's harder for us to find the problem.

Thanks. We noticed the problem and will look into it soon.

Hi Swaan,
You can change it as Graham suggested. BTW, actually it is diigo+ google, part of your bookmark search result, part of your google search result.

Hi Swaan,
I am so sorry about the problem in the address bar.
Installing new version doesn't solve the existing problem. Here is how to fix it manually:

1. Input about:config in the firefox address bar, then enter this address
2. Click I will be careful, I promise! button.
3. Input keyword.url in the filter
4. Double click the value and change the value to http://www.google.com/search?ie=UTF-8&oe=UTF-8&sourceid=navclient&gfns=1&q=
5. Restart Firefox.

Let me know whether it works for you.

Thanks.

Hi Swaan,
The bug was a huge mistake. We tried to hack some firefox new features and forgot to comment it out in the release version.

Oh, it works for me. Can you reproduce the problem after you restart Firefox?

How about recommending new users to use Diioglet which is not browser specific?