3 ms·

Wuala is a desktop app - this is a website that works everywhere on most modern browsers, including Chrome for Android. Securesha.re wouldn't have even been pos

by STRML 14y ago

Wuala is a desktop app - this is a website that works everywhere on most modern browsers, including Chrome for Android. Securesha.re wouldn't have even been possible a year ago; it relies on some very new File API calls that were recently added by the W3C. (http://www.w3.org/TR/FileAPI/ http://www.w3.org/TR/FileAPI/)

saurik 14y ago
Over a year ago, it was a safe bet that users had Flash installed (more than today are likely to have a "modern browser"). Flash can read files directly with, AFAIK, arbitrary complexity and was specifically popular to build improved file upload widgets (such as Facebook's photo importer tool). This concept thereby doesn't really "rely" on the File API (so one could easily imagine there having been someone doing exactly this many years ago, not that "first" is really relevant anyway ;P). In the case of Wuala, they actually were totally available via web browsers [1]; they used Java, however, instead of Flash, as seemingly their desktop client was already written in Java, so this was convenient. (Additionally, Java came pre-installed on most systems, albeit Windows shipped with the ancient 1.1 version, of course, due to that lawsuit.) You can find presentations from 2009 discussing the technical issues that went into this [2]. [1]: http://www.wuala.com/en/launch/ http://www.wuala.com/en/launch/ [2]: http://jazoon.com/portals/0/Content/ArchivWebsite/jazoon.com/jazoon09/download/presentations/10100.pdf http://jazoon.com/portals/0/Content/ArchivWebsite/jazoon.com... This method did, of course, involve getting pulled out of the web browser, but AFAIK that was not a technical requirement of Java for this purpose. (They claim in the presentation that a "Web App", even with Flash, wasn't capable of client-side encryption, which doesn't make much sense to me; maybe they just didn't want to implement the encryption algorithm? I also do not see them considering embedding the Applet into the website as opposed to just using it to launch their external app, but again: convenience to their existing codebase is likely a strong factor.)
Angostura 14y ago
> this is a website that works everywhere on most modern browsers, including Chrome Well, actually - it only seems to work fully on Chrome. https://mega.co.nz/#blog_1 https://mega.co.nz/#blog_1
- STRML 14y ago
  I'm speaking about my site, not Mega, which works in Firefox, Chrome for Android and Safari. Although Safari support is limited for now and has actually moved measurably backwards in the last few weeks. The better version of this post likely would have been a "state of browser-based encryption"; we're so close to really being there but any possible implementation is still a slow hack that won't work on all systems.

by STRML 14y ago

saurik 14y ago

Over a year ago, it was a safe bet that users had Flash installed (more than today are likely to have a "modern browser"). Flash can read files directly with, AFAIK, arbitrary complexity and was specifically popular to build improved file upload widgets (such as Facebook's photo importer tool). This concept thereby doesn't really "rely" on the File API (so one could easily imagine there having been someone doing exactly this many years ago, not that "first" is really relevant anyway ;P). In the case of Wuala, they actually were totally available via web browsers [1]; they used Java, however, instead of Flash, as seemingly their desktop client was already written in Java, so this was convenient. (Additionally, Java came pre-installed on most systems, albeit Windows shipped with the ancient 1.1 version, of course, due to that lawsuit.) You can find presentations from 2009 discussing the technical issues that went into this [2]. [1]: http://www.wuala.com/en/launch/ http://www.wuala.com/en/launch/ [2]: http://jazoon.com/portals/0/Content/ArchivWebsite/jazoon.com/jazoon09/download/presentations/10100.pdf http://jazoon.com/portals/0/Content/ArchivWebsite/jazoon.com... This method did, of course, involve getting pulled out of the web browser, but AFAIK that was not a technical requirement of Java for this purpose. (They claim in the presentation that a "Web App", even with Flash, wasn't capable of client-side encryption, which doesn't make much sense to me; maybe they just didn't want to implement the encryption algorithm? I also do not see them considering embedding the Applet into the website as opposed to just using it to launch their external app, but again: convenience to their existing codebase is likely a strong factor.)

Angostura 14y ago

> this is a website that works everywhere on most modern browsers, including Chrome Well, actually - it only seems to work fully on Chrome. https://mega.co.nz/#blog_1 https://mega.co.nz/#blog_1

STRML 14y ago
I'm speaking about my site, not Mega, which works in Firefox, Chrome for Android and Safari. Although Safari support is limited for now and has actually moved measurably backwards in the last few weeks. The better version of this post likely would have been a "state of browser-based encryption"; we're so close to really being there but any possible implementation is still a slow hack that won't work on all systems.