Search the Community
Showing results for tags 'add-on'.
Karlston posted a topic in Guides & TutorialsFirefox's Multi-Account Containers add-on gets Site Isolation feature Containers is an interesting feature that Mozilla implemented in the Firefox web browser some time ago. It provides users with a way to separate sites from each other, and benefits of doing so are clear: less tracking, improved privacy, and the ability to sign-in to multiple accounts in a single browsing session. The Mutli-Account Containers add-on adds configuration options to the feature. You use it to create and edit containers, and to assign sites to containers. The extension ships with the four default containers personal, work, banking and shopping, and users may add more containers, rename existing ones, or customize them with different colors or icons. Up until now, it was possible to assign certain sites to specific containers. An assigned site would always be opened in that particular container in Firefox to separate it from others. The new major Firefox Multi-Account Containers release that just landed on Mozilla AMO introduces another feature: site isolation. Besides assigning sites to containers, it is now possible to limit containers to particular sites. You may use the improved functionality to isolate sites similarly to how standalone extensions such as Facebook Container isolate Facebook from the rest of the browsing session. Usage is straightforward. Load a site or sites in a particular container in Firefox, e.g. facebook.com. Select the Multi-Account Containers icon in the toolbar and activate the manage containers option in the interface that opens. Select the container that you added the site or sites to, and check the "limit to designated sites" box on the page that opens. Last step in the process is to open the sites again in a new tab and check the "always open in container" option to make sure that the site is opened in that container whenever it gets loaded in the browser. You may use the site isolation feature to limit sites to specific containers, and make sure that only the selected sites do get opened in these containers. The feature works really well for search engines. Say you assign Google Search or Bing Search to a container and make sure that only the search engine is opened in that container. Run a search and click on a result, and you will notice that the result is opened in a new tab outside the container. The same can be done for sites that post links that point to third-party resources, e.g. Reddit, Facebook, Pinterest, any search engine, or Twitter. Landing Page: https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/ Firefox's Multi-Account Containers add-on gets Site Isolation feature
Prevent Facebook from tracking you around the web. The Facebook Container extension for Firefox helps you take control and isolate your web activity from Facebook. What does it do? Facebook Container works by isolating your Facebook identity into a separate container that makes it harder for Facebook to track your visits to other websites with third-party cookies. How does it work? Installing this extension closes your Facebook tabs, deletes your Facebook cookies, and logs you out of Facebook. The next time you navigate to Facebook it will load in a new blue colored browser tab (the “Container”). You can log in and use Facebook normally when in the Facebook Container. If you click on a non-Facebook link or navigate to a non-Facebook website in the URL bar, these pages will load outside of the container. Clicking Facebook Share buttons on other browser tabs will load them within the Facebook Container. You should know that using these buttons passes information to Facebook about the website that you shared from. Which website features will not function? Because you will be logged into Facebook only in the Container, embedded Facebook comments and Like buttons in tabs outside the Facebook Container will not work. This prevents Facebook from associating information about your activity on websites outside of Facebook to your Facebook identity. In addition, websites that allow you to create an account or log in using your Facebook credentials will generally not work properly. Because this extension is designed to separate Facebook use from use of other websites, this behavior is expected. What does Facebook Container NOT protect against? It is important to know that this extension doesn’t prevent Facebook from mishandling the data that it already has, or permitted others to obtain, about you. Facebook still will have access to everything that you do while you are on facebook.com, including your Facebook comments, photo uploads, likes, any data you share with Facebook connected apps, etc. Rather than stop using a service you find valuable, we think you should have tools to limit what data others can obtain. This extension focuses on limiting Facebook tracking, but other ad networks may try to correlate your Facebook activities with your regular browsing. In addition to this extension, you can change your Facebook settings, use Private Browsing, enable Tracking Protection, block third-party cookies, and/or use Firefox Multi-Account Containers extension to further limit tracking. What data does Mozilla receive from this extension? Mozilla does not collect data from your use of the Facebook Container extension. We do receive the number of times the extension is installed or removed. Learn more Other Containers Facebook Container leverages the Containers feature that is already built in to Firefox. When you enable Facebook Container, you may also see Containers named Personal, Work, Shopping, and Banking while you browse. If you wish to use multiple Containers, you’ll have the best user experience if you install the Firefox Multi-Account Containers extension. Learn more about Containers on our support site. Known Issues When Facebook is open and you navigate to another website using the same tab (by entering an address, doing a search, or clicking a bookmark), the new website will be loaded outside of the Container and you will not be able to navigate back to Facebook using the back button in the browser. NOTE: If you are a Multi-Account Containers user who has already assigned Facebook to a Container, this extension will not work. In an effort to preserve your existing Container set up and logins, this add-on will not include the additional protection to keep other sites out of your Facebook Container. If you would like this additional protection, first unassign facebook.com in the Multi-Account Container extension, and then install this extension. What version of Firefox do I need for this? This extension works with Firefox 57 and higher on Desktop. Note that it does not work on other browsers and it does not work on Firefox for mobile. If you believe you are using Firefox 57+, but the install page is telling you that you are not on a supported browser, you can try installing by selecting or copying and pasting this link. (This may be occurring because you have set a preference or installed an extension that causes your browser to obscure its user agent for privacy or other reasons.) How does this compare to the Firefox Multi-Account Containers extension? Facebook Container specifically isolates Facebook and works automatically. Firefox Multi-Account Containers is a more general extension that allows you to create containers and determine which sites open in each container. You can use Multi-Account Containers to create a container for Facebook and assign facebook.com to it. Multi-Account Containers will then make sure to only open facebook.com in the Facebook Container. However, unlike Facebook Container, Multi-Account Containers doesn’t prevent you from opening non-Facebook sites in your Facebook Container. So users of Multi-Account Containers need to take a bit extra care to make sure they leave the Facebook Container when navigating to other sites. In addition, Facebook Container assigns some Facebook-owned sites like Instagram and Messenger to the Facebook Container. With Multi-Account Containers, you will have to assign these in addition to facebook.com. Facebook Container also deletes Facebook cookies from your other containers on install and when you restart the browser, to clean up any potential Facebook trackers. Multi-Account Containers does not do that for you. Report Issues If you come across any issues with this extension, please let us know by filing an issue here. Thank you! ----- Release Notes: This release also asks for permission to clear recent browsing history, so we can improve its protection and its integration with Multi-Account Containers. 83ae8bf fix #183: Can't search Google/other sites with string "fbclid". Add-on's Permissions: This add-on can: Access your data for all websites Clear recent browsing history, cookies, and related data Monitor extension usage and manage themes Access browser tabs ----- Homepage/Download https://addons.mozilla.org/en-US/firefox/addon/facebook-container/
zanderthunder posted a topic in Software NewsFirefox users won't be able to sideload extensions starting March 2020, with Firefox 74. Mozilla has announced today plans to discontinue one of the three methods through which extensions can be installed in Firefox. Starting next year, Firefox users won't be able to install extensions by placing an XPI extension file inside a special folder inside a user's Firefox directory. The method, known as sideloading, was initially created to aid developers of desktop apps. In case they wanted to distribute a Firefox extension with their desktop app, the developers could configure the app's installer to drop a Firefox XPI extension file inside the Firefox browser's folder. SIDELOADING REMOVED BECAUSE OF ABUSE This method has been available to Firefox extension developers since the browser's early days. However, today, Mozilla announced plans to discontinue supporting sideloaded extensions, citing security risks. "Sideloaded extensions frequently cause issues for users since they did not explicitly choose to install them and are unable to remove them from the Add-ons Manager," said Caitlin Neiman, Add-ons Community Manager at Mozilla. "This mechanism has also been employed in the past to install malware into Firefox," Neiman said. TWO-PHASE REMOVAL PLAN As a result, Mozilla plans to stop supporting this feature next year in a two-phase plan. The first will take place with the release of Firefox 73 in February 2020. Neiman says Firefox will continue to read sideloaded extensions, but they'll be slowly converted into normal add-ons inside a user's Firefox profile, and made available in the browser's Add-ons section. By March 2020, with the release of Firefox 74, Mozilla plans to completely remove the ability to sideload an extension. By that point, Mozilla hopes that all sideloaded extensions will be moved inside users' Add-ons section. Through the move, Mozilla also hopes to help clean up some Firefox installations where malware authors were secretly sideloading extensions behind users' backs. Since these extensions will now show up in the Add-ons sections, users will be able to remove any extensions they don't need or don't remember installing. TWO METHODS OF LOADING EXTENSIONS REMAIN Further, Mozilla's blog post on the matter today also serves as a notice for extension developers, who will have to update their extensions and make them available through another installation mechanism. There are currently two other ways through which developers can distribute extensions, and through which users can install them. The first and the most widely known is by installing extensions from the official addons.mozilla.org (AMO) portal. Extensions listed here are verified by Mozilla, so most are relatively safe, albeit the security checks aren't 100% sure to catch all malicious code. The second involves using the "Install Add-on From File" option in Firefox's Add-ons section. Users have to manually download a Firefox XPI extension file, visit the Add-ons section, and then use the "Install Add-on From File" option to load the extension in their browser. This option is usually employed for loading extensions that have to handle sensitive corporate data inside enterprise environments, and can't be distributed via the AMO portal. There was also a fourth method of loading extensions inside Firefox, but this was removed in September 2018, with the release of Firefox 62. This involved modifying Windows Registry keys to load custom extensions with Firefox installations. This, too, was abused by malware devs, and Mozilla decided to remove it. Source: Mozilla to stop supporting sideloaded extensions in Firefox (via ZDNet)