171–180 of 190 posts
Earlier quoted context omitted.
FYI: KeePass plus Syncthing works great for me for cross-device password databases.
Will have to check this out. Not used Syncthing before. Thanks!
As I mentioned in my other comment, the only gotcha is to make sure you set up your syncthing ignore file to ignore the KeePass database lockfile.
Earlier quoted context omitted.
Thanks for the reply. Adding a "cloud" icon to a button called "Save" does not make it clearer, it makes it contradictory (does it save it or does it upload it?). It's very clear based on the design of the interface that your primary goal is to get people to upload their screenshots to your servers. The "save" button is the only one with a label. The others are icons only. The "save" button is 3x as big as the other…
> I'm not convinced "user research" is the best way to go here. If the majority of your selected users think "save" should mean "upload to mozilla" does that mean they're right? More or less, yes, if more people understand one design than another, then the one that more people understand is the right one. We're generally shooting for more than a majority though, we'd want most people to understand the interface, and…
I take screenshots of internal graphs, admin pages that may contain pseudo-private endpoints and admin account information all the time ("Logged in as $ADMIN_USER", account numbers with vendors, etc.). Sharing those in a private chat or email is a big part of my screenshotting use case. People screenshot a lot of private data.
I don't think Mozilla is wise in making "send your image to a public bucket protected only by the obscurity of its URL" the default behavior, at least not without making it obvious that this is what's happening. This sneaky exfiltration of private data is a large part of what people hate about Google and Facebook.
Maybe there could be an opt-out on first use? I get that your average grandma isn't going to understand the distinction and will want something she can share (but she's also probably just trying to get to email or Facebook anyway), but this is a real potential security problem for your users.
I've been following https://utcc.utoronto.ca/~cks/space/blog/web/Firefox56AddonW... It's surprised me the amount some people rely on addons for their workflow and the amount of effort they will be going through to resist this change come 57. For my usage, I've found Firefox Klar/Focus (which I believe already include the speed improvements from 57+?) on Android and have been extremely impressed.
For people who are uber concerned about keeping v56 without losing your extensions as part of the 57 update, you can turn off auto update for Firefox: Go to about:preferences In Firefox Updates choose "Never Check for Updates" Breathe easy! I know this is not recommended, but I love my XUL based extensions a little too much (Tab Groups primary among those) to give them up so easily.
I'm also saddened that a transition with such a large change in functionality for end users didn't warrant syncing up with a Long Term Support version.
There's going to be a bit of a waiting game to see which extensions get ported and with what percentage of their original functionality retained.
Then it will be decision time.
> Firefox Quantum’s new engine uses 30% less memory than Chrome This is a pretty appealing claim. I'm ashamed to admit that one thing that might keep me on Chrome is the trove of passwords in my sync'd up account. But I'll definitely give Quantum a test drive.
Might be looking into bitwarden myself as lastpass as of this post does not support firefox 57.
Earlier quoted context omitted.
Thanks for the reply. Adding a "cloud" icon to a button called "Save" does not make it clearer, it makes it contradictory (does it save it or does it upload it?). It's very clear based on the design of the interface that your primary goal is to get people to upload their screenshots to your servers. The "save" button is the only one with a label. The others are icons only. The "save" button is 3x as big as the other…
> I'm not convinced "user research" is the best way to go here. If the majority of your selected users think "save" should mean "upload to mozilla" does that mean they're right? More or less, yes, if more people understand one design than another, then the one that more people understand is the right one. We're generally shooting for more than a majority though, we'd want most people to understand the interface, and…
Something something Henry Ford and faster horses. It's still bad design even if 50%+ε understand save as 'upload to some server' and not the old meaning that predates Windows 95 which is to save it to local storage. You shouldn't be taking liberties whenever you are about to upload any bit of information from your users, instead you should obtain informed consent from all users and not just from better informed ones that can parse the meaning from the cloud icon. The UI is wrong until only a moron in a hurry[1] would be mistaken about what your software is about to perform. Otherwise how are you any better than that other company that starts with a G and ends with oogle.
Tab Mix Plus, DownloadThemAll, RightToClick, Status-4-Evar... all regularly used by me, none migrated yet. Not to mention the loss of Classic Theme Restorer's control over the UI highly disappoints me. I really really dislike being locked into the "Chrome Style" UI. I've disliked it since Chrome was released.
Read the news for DownloadThemAll: http://www.downthemall.net/ It's coming. He has started. You can help by becoming a patron.
Woah!! I didn't think it was possible but...download acceleration post 57?
My big concern is add-ons. The whole reason I use Firefox is the availability of add-ons such as NoScript and Cookie Culler. I'm guessing NoScript will work with Quantum, but Cookie Culler hasn't been updated since last year. Roomy Bookmarks is also a major quality-of-life factor; it allows me to have a well-stocked bookmarks bar. And it definitely won't work with Quantum. That alone will give me strong pause about u…
What about cookie autodelete?
I will badly miss vimperator. Yeah 56.0 works smoothly but without ability to use keyboard only that's hollow victory for me. Typing this in vim after viewing hackers news in w3m shows how desperate I am.
Earlier quoted context omitted.
Absolutely. I won't be upgrading and I'm already looking for alternatives, as long as crucial parts of my workflow (tree tabs, session manager) have no adequate replacement. The ugly redesign is also a thorn in my side.
How's the redesign ugly?
Earlier quoted context omitted.
If this is a problem for you, please switch to 52 ESR and use it until June 2018, and file bug reports against those legacy extensions. Disabling updates for a piece of software that is used to run untrusted code is a terrible piece of advice.
Unfortunately, a profile backwards-incompatibility was added in FF55, IIRC, so if you're already on 56 you can't downgrade to 52.