I suggest you ...

secure and encrypt network traffic between the client and Diigo servers

All client-side applications of Diigo should secure — and ideally encrypt — all traffic between the client and Diigo servers.

This is most important when bookmarking or annotating content that is wholly or partly secured (i.e. https) or non-public.

I'll not categorise this topic; the suggestion applies to all Diigo products and services.

397 votes
Sign in
Signed in as (Sign out)
You have left! (?) (thinking…)
Graham PerrinGraham Perrin shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
Max MillionMax Million shared a merged idea: Why not use SSL (secure connection) for Bookmarklet[s] ?  ·   · 
Douglas VazDouglas Vaz shared a merged idea: Change Diigolet to use https  ·   · 


Sign in
Signed in as (Sign out)
  • corvettez06pilotcorvettez06pilot commented  ·   ·  Flag as inappropriate

    Great. This was far and away the most important feature to me. Folks that don't think it's important either don't get it or do not use it at work. If you do, think about it...

  • Thomas WoodardThomas Woodard commented  ·   ·  Flag as inappropriate

    This is the most annoying issue I have with the Diigolet, it doesn't work if you want to bookmark a https page. With the increasing trend of sites enabling https by default it means less and less sites I can bookmark with the Diigolet.

    If I change the code of the diigolet to:

    it starts running on https pages, but then stops and reports "Loading Diigolet..." forever. All you have to do is switch from "http://"; to "//" in your scripts.

  • D McD Mc commented  ·   ·  Flag as inappropriate

    @ sandy_diigo:

    Thank you so much! I look forward to the next version. Again, I really, really enjoy this service (and your responsiveness) very much. You guys are great!

  • D McD Mc commented  ·   ·  Flag as inappropriate

    This isn't just about content privacy but also about keeping account log-ins secure. If someone were to snoop a user's network, the captured packets could be used to replay the web session or sniff out password information. This isn't just a problem with home networks-- hackers in the workplace can do this sort of thing, too. Sometimes admins abuse their privileges and use their networking knowledge for unethical reasons. I really want to see HTTPS between the plug-ins, clients, apps and the web site. I really love this service and I'm becoming quite dependent on it. I would want to see this feature added before anything else.

  • corvettez06pilotcorvettez06pilot commented  ·   ·  Flag as inappropriate

    This REALLY needs to happen. There are those of us that use diigo through VPN, workplace proxies, etc. To me, my personal content at diigo is important enough to protect with a "strong" password. TLS/SSL needs to happen for diigo. Plenty of folks would like to get this information that you hold--and that I pay for you to hold.


  • tesa enigmatesa enigma commented  ·   ·  Flag as inappropriate

    App is useless until HTTPS is available while on your 'diigo" page. To put so much time into configuring it only to learn that it's not an encrypted site is frustrating. Should of just skipped this service I think.

  • tesa enigmatesa enigma commented  ·   ·  Flag as inappropriate

    I agree, this needs to be standard. Using this service for anything other than leisure research would be out of the question. I waste so much time trying to configure this stuff only to find out I'm not even on an HTTPS page when I'm logged into my diigo page. Useless now. Wake me up when you guys implement this feature, thanks.

  • tiramstirams commented  ·   ·  Flag as inappropriate

    when will this be available? will start premium once you have https like evernote has

  • Mike DonovanMike Donovan commented  ·   ·  Flag as inappropriate

    Crucial. I can't upload/download/bookmark, etc. data that's not secured by an SSL certificate (https). If necessary, it can be a premium feature, but right now - Diigo is a no-go until there's a secure connection. Thanks!

← Previous 1

Feedback and Knowledge Base