Slashdot Mirror
Google Open Sources Browser Sync
Dan Berlin writes "After announcing that Browser Sync was being discontinued, a lot of people asked for Google to open source the code so development could continue.
Well, they've done just that.
The code for browser sync is now available on code.google.com, and a blog post about the release can be found on the Google open source blog"
http://tech.slashdot.org/article.pl?sid=08/06/30/2036213
But with your data encrypted, why do you need to trust anyone? For you it is the state of your browser, passwords etc, but for anyone else it is random bits.
Doesn't Browser sync already supports encrypting your data? Even if it doesn't I am sure this capability can be added now that it is open-source.
I'm sure there have been other examples, but this is the first and possibly only example I can think of of a company *actually responding* to requests for a discontinued product to be open-sourced. Let alone actually going ahead and doing it.
Bravo Google :)
How about hosting it on google? Like on gmail or something.
Hosting on Google is possible using Google App Engine.
There's a nice little add on for Firefox called "Live HTTP Headers", which shows all requests made from the browser. This includes the actual request by Flash to fetch the FLV file, so you get the full URL of the request, paste it back into the address bar, and choose save as file. Easy.
Let the FLV pr0n downloads begin.
I run 2 instances of Firefox (not Windows, two seperate processes) and I am forced to use different profiles. However I want them to have the same bookmarks and addons. Now I just symlink it from one profile to another what is needs. I would be much nicer to have something that could do that on my own machine, without telling anybody else what my Pr0n preferences are.
Don't fight for your country, if your country does not fight for you.
It's only the client code (the xul & javascript code, which can already be found in the xpi file). There is no sever code (yet ?).
Foxmarks is OK for syncing bookmarks, but GBS also synced your history, open tabs, passwords (if you were brave enough) and cookies. Having a synced history and cookies was very useful because you could stay logged in to the same sites across any GBS'd computer.
They all ready had it. You had two 'passwords' that you had to enter to use GBS. One was your account password and the other was a passphase used to encrypt what you uploaded to them.
It works the same way Mozilla's Weave project works. The only those with your passphrase can use your data.
You can't opensource abandonware that has other companies IP in it, or active patents. You could opensource the other components, but... it's abandonware! For some reason or another, they are no longer working with the code (and filtering the code may be impractical or impossible).
For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
There was a neat study that Greg KH did about corporate contributions to the kernel, which has us at a not-too-shabby 13th.
Co-Editor, Open Sources
Open Source Program Manager, Google, Inc.
You need to set up apache running webdav
http://wiki.foxmarks.com/wiki/Foxmarks:_Frequently_Asked_Questions#Using_Other_Servers
The difference between Canada and the USA is that in Canada healthcare is a right and gun ownership is a privilege.
Have a look at Passhash add-on for firefox. You only need to remember a single strong master password; the add-on generates different passwords for each site, according to their URL (or site tag).
In cases where the add-on is not locally available, there is a static html page with javascript with the same functionality, that you can host on your home server.