Firefox screenshot feature should allow users to block data upload
I have read description of Firefox screenshot feature and some discussions on the subject and don't see any reason for forced uploading data screenshot to the cloud. It is mentioned in the feature description at https://support.mozilla.org/en-US/kb/firefox-screenshots that there are two components involved in the process of creating and uploading the screenshot. It is done under header "Can I opt out of data collection?" and is formulated in extremely unclear way: "Definitely. Screenshots consists of a web-based component and a browser-based component. Firefox’s Options are undergoing a remodel, so disabling metrics works slightly differently depending on which version of Firefox you’re using." Thus while one can assume that it is possible to set up Firefox in such a way as to block sending screenshot data to the Mozilla server, there's no information how to do it. The similarly unclear formulation in another section of the above mentioned page describe data collected by Firefox. "What data does Firefox Screenshots collect? Firefox Screenshots collects event data in a manner consistent with the Firefox Browser Privacy Notice. We collect this data in order to learn how people use Screenshots so we can make it better for everyone. You can view all of the events we capture in this document." The link under last word of the above sentence leads to rather complicated and very technical description of data structures and message types used for collecting information about users activities, presumably selected with care, however completely unsuitable as explanation to the sentence linking to it. In the whole long description there is no information how to disable the screenshot data upload without disabling the whole feature. In addition the description is rather old: mentioned Firefox releases 55 and 56 are definitely not fresh for many months. To add a bit specific taste to the situation there was quite comprehensive discussion of the matter (https://discourse.mozilla.org/t/upload-of-screenshot-without-asking-for-permission-or-even-warning-me/16451) by Ashawi which ends with the note "Thanks for your suggestions. I’ve filed an issue at https://github.com/mozilla-services/screenshots/issues/3499" by clouserw on Sep '17. The related thread on github is very short. Besides citation of essential part of Ashavi suggestions (to change wording in the description of the feature to clearly state how to make screenshot without uploading it to Mozilla servers) and a couple of technicalities, it contains an assignment to Release 57 made by johngruen on Oct 31, 2017, and then is closed on Mar 17 - also by johngruen!
Is it a technical problem or someone prefers the current situation?
All Replies (6)
You can click the Download button (down pointing arrow) to save the screenshot to your computer. The Save button saves the screenshot to internet (screenshot server).
cor-el, You (I'm afraid not the first time) not responded to the point. Bluntly, your response seems to have single objective - to avoid questions left unanswered.
Firstly, I understand what "Download" button *should do,* as well as "Save" button. The question is whether these names are correctly describing the actions. "Save" is commonly understood as local action, while "download" is interpreted as an action of transfer of data from Internet (cloud, server) and has opposite term "upload". Thus it is obvious that use of these terms in Firefox screenshot is misleading. (I'm intentionally skipping the question whether "download" is active before "save" is used.)
Secondly, the open question is whether "Download" button *does not upload* the data to the server, in other words: is it really local action? There is no explicit statement concerning this.
Thirdly, my post addressed more general problem (which you ignored): why such situation is tolerated? And additionally, it seems this is done on purpose!
So I repeat my question, just to allow to dispel doubts: what's the reason for inaction of people who could (a) correct Firefox screenshot buttons names to follow common understanding of used terms and (b) correct the tool FAQ for so long time? It's difficult to believe that it is real technical problem or that developers are so occupied... And if not any above mentioned reasons then WHAT is the reason? Or in more explicit way: Is anybody interested in misleading Firefox users?
Modified by witrak()
people replying here in the support forum are generally volunteers and not really in a position to answer questions like this one...
philipp said
people replying here in the support forum are generally volunteers and not really in a position to answer questions like this one...
Yes, I know. And I appreciate good, clear answers I often see there. But it doesn't mean that all questions must be answered. And definitely doesn't mean that it's is good practice to provide answers not relevant enough.
The developers see Firefox screenshot from the perspective of the Firefox screenshot website on internet and save means saving to that website and download means saving to the computer. I agree that this is confusing and that is why I explained above how it works. Always keep in mind that other read these question pages and may not be aware of this perspective. The screenshot doesn't leave the computer when you click download.
Note that the developer tools also have a full page screenshot button available as part of its toolbox that exists for quite a few years as you might be ware of. Both use the same screenshot API, only Firefox screenshot extension makes it easier to select part of the screen (the developer tools have a "Screenshot Node" item in the right-click context menu in the left pane in the Inspector).
Thank you for your response. Now I understand why the buttons naming is so absurdly unintuitive: it simply follows the developers naming conventions with total disregarding to the fact that they make perhaps less than 0.01% of users. Nevertheless, it's not the reason for ignoring the legitimate and quite polite request, which effectively is the action taken by the developer I mentioned earlier when he closed the request for change without a word of explanation. Also, a change of the FAQ text and an explicit statement fully explaining actions of each button could at least partially resolve the issue. It shouldn't be much work, but it wasn't done in so long period of time... That's, unfortunately, a typical example of arrogance and disregard of some members of the community which en masse makes a wonderful job. It's a pity that Mozilla Foundation while investing so much effort in making Firefox user-friendly isn't able to create an organizational environment encouraging a proper attitude of employees and contributors.
Modified by witrak()