Loading Profile...
Why have you violated my trust?
The old version of Foxmarks did what I wanted. Shared my bookmarks, on my own server, where I could control it. Instead, the new version has reset my details, interfered with search results, and started uploading data to God knows where. Not only did you change the license terms (from FOSS to propertirary), you now take the good will of your many users and completely change the ethos and nature of the program. I am very unhappy with the direction that you have taken.
I’m very upset
4
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
The best solution from the company
-
For more details on the original problem reported (loss of own-server setting during upgrade), please consult this related topic:
http://getsatisfaction.com/foxmarks/t...
It absolutely was not our intent to turn off that setting during the upgrade; it was instead an unfortunate byproduct of a refactoring of our configuration settings in the extension. There's a fairly straightforward fix available to reactivate your own-server settings, and we intend to have the upgrade problem fixed in the next version of Xmarks we release.
I'm very sorry for any frustration that mix-up may have caused; trust me, we're bonking our foreheads for having missed that item in our QA passes.
The company says
this solves the problem
-
Inappropriate?Agree 100%. Best Addon gone. very annoying.
To go back to old version do the following.
1. Note your Xmarks username and password.
2. Uninstall Xmarks.
3. Go to https://addons.mozilla.org/en-US/fire....7.2
4. Install Foxmarks.
5. Login with your username and password.
Joe
I’m annoyed
1 person says
this solves the problem
-
Inappropriate?Yeah a lotta changes - I ran into most of these concerns too:
Pretty sure you can still use your own server (in the advanced part of the settings). I was able to use it (as an experiment, I went back to using their servers after). Unless you use your own server, I think they've always uploaded to "god-knows-where" tho', so no change there. You can also turn off the discovery/search stuff in the settings (I like it, but ymmv) and the bookmark aggregation can be turned off too (this is in the website account, they just added it last week). I'm glad they added the opt-out, altho' I do like the discovery. But I also use adblock and expect the sites I like to still survive... so no change in attitude for me there :-)
As for the license... hmmm... I may be wrong, but I think they never changed that. This isn't foss, never was, never pretended to be as far as I can tell. Altho' all the source is right there for anyone to see in the FF extension, altho' there's clearly some diff-like magic at the servers.
I’m diff'ing right now.
1 Comment Add a comment
This solves the problem
-
The license was changed in version 2, from FOSS to proprietary - see http://getsatisfaction.com/foxmarks/t...
One of my biggest problems is the way they did this without informing the user at all. Instead, I applied what I thought was a security update, and suddenly Google's results were changed, and my data was being uploaded. I was previously using my own server - magically, this was turned off, and defaults restored. (incidentally, there is no clever stuff at the servers, since it is just a JSON file that contains your bookmarks - that all happens on the client.)
So all in all, this is a massive backwards step for me, with an horrendous way to deal with your user-base as well. -
Inappropriate?Ah good point, I stand corrected. On the server thing, I think you'll find that own-server is indeed a dumb upload/download, but if you use their servers you see (always have had this) different traffic that only uploads the minimal changes (obviously there's an up/down mode too, but most of the time it's diffs). I did some sniffing with wireshark.
I’m lovin' the sniffer.
-
Inappropriate?Bill, your read of the code is correct -- Xmarks sends only diffs to our servers, which yields large network bandwidth efficiencies. We obviously can't do that with a simple DAV or FTP server, so if you're using your own server, Xmarks sends a file representation of your entire bookmark set over the wire each time. That's fine for you if you use your own server, but not so great for us with millions of users.
In addition to participating in the "diff" protocol, our servers also support two lesser-used but handy features: they let you restore to an arbitrary previous version so you can recover from a meltdown, and they support sync profiles, which let you exclude your personal stuff from work and vice versa. These features are also not supported by simple DAV or FTP.
P.S. Martin, we emailed everyone for whom we had an email address to announce the changes we were making. If you were using your own server and never had an account with us, we would have missed you. But I'm not sure what else we could do -- if we don't have your email address, there's no way for us to communicate with you other than making a software upgrade available to you and have the software itself communicate those changes (which is what we did).1 Comment Add a comment
This solves the problem
-
I'm sorry Todd, but that's not good enough. You yourself have realised that it is a different product - you've given it a new name! So why annoy everyone who is happy with the way things are?
If you really wanted to push the new 'features' then do what Firefox (for example from v2 to v3 - what any well behaved program does), and simply notify me me that this new version exists. You certainly don't reset settings and enforce brand new behaviour without explicit opt-in. -
Inappropriate?For more details on the original problem reported (loss of own-server setting during upgrade), please consult this related topic:
http://getsatisfaction.com/foxmarks/t...
It absolutely was not our intent to turn off that setting during the upgrade; it was instead an unfortunate byproduct of a refactoring of our configuration settings in the extension. There's a fairly straightforward fix available to reactivate your own-server settings, and we intend to have the upgrade problem fixed in the next version of Xmarks we release.
I'm very sorry for any frustration that mix-up may have caused; trust me, we're bonking our foreheads for having missed that item in our QA passes.
The company says
this solves the problem
EMPLOYEE
EMPLOYEE
