Archive for the ‘Add-ons’ Category

Photobucket Uploader Extension

Posted: Friday, December 17, 2010 by El Guru in Add-ons, Blogs, Firefox, Fx 3.0, Fx 3.5, Fx 3.6, Fx 4.0

It has been a long while since we’ve done an extension review. I came across the Photobucket Uploader Extension a week or two ago while I was in my Photobucket account. I use Photobucket for both management and storage of images I use on the three blogs (FF Extension Guru, Email Mafia and El Guru’s) and their associated websites. I just find it easier to work with images this way, especially when incorporating them into the WordPress environments (WordPress.com & WordPress.org/self-hosted).

This extension is a major time saver. Once installed and link to your Photobucket account, simply right-click on any image (except CSS coded background images) within Firefox and select Upload to Photobucket from the context menu. That is it, the image will be uploaded to your default album and you can even get your links as soon as the upload is completed. No more having to right-click on the image copy the URL, go into Photobucket, then upload via the pasted image URL.

But wait, there’s more! Say you have an image saved on your computer and you want to upload it into Photobucket. Normally, you would need to go Photobucket, select to upload from your computer and then spend a couple minutes trying to get to where the image is saved. I run into this issue a lot, being that I can have the image saved in one of many locations depending on if the image is going to be used for a blog or website. In the case of earlier tonight I had a couple photos I had taken and had cropped earlier that I wanted to upload for use on the El Guru’s Blog. I had the folder which the photos were saved within opened in Windows Explorer. I simply opened a new Firefox tab and then dragged the image into Firefox. Once it was in Firefox, it was a simple right-click and the image was in my Photobucket Album and I had the link I needed to post the image.

The Photobucket Uploader Extension is not endorsed or sponsored by Photobucket. The extension works with Firefox 3.0 up through 3.6 (do not know if it can be forced to work on Firefox 4).

Advertisements

Detect FireSheep snoop software

Posted: Tuesday, November 9, 2010 by gareon in Add-ons, Firefox

” Researchers from security firm Zscaler have published free software that detects when users’ web connections are being monitored by a controversial tool that steals log-in credentials from Facebook, Google and dozens of other websites.
Dubbed BlackSheep, the Firefox extension alerts users when computers on a local area network are using FireSheep to steal unencrypted cookies the websites use to grant users access to their account pages. When BlackSheep detects the snoop software in a hotspot or other open Wi-Fi network, it displays a message that reads “Somebody is using FireSheep on this network.” It then displays the LAN IP address of the offending party… “

8th November 2010

Source: The Register
 http://www.theregister.co.uk/2010/11/08/firesheep_detection_tool/
.



   Gary    

Changes to Search Engine Plugins Coming

Posted: Saturday, October 9, 2010 by El Guru in Add-ons, Blogs, Firefox, Fx 3.6, Google, Microsoft

Starting with most likely the next Firefox 3.6.x update (currently scheduled for mid-October) the default set of Search Engine plugins shipping with Firefox will be changing. Microsoft’s Bing will now be included (user had to manually install this search engine plugin prior). Answers.com and Creative Commons are being removed, but can be installed manually by clicking the links here. Google, Yahoo, Amazon, eBay and Wikipedia are staying put along with any other search engines the user has manually installed on their profile.

New Default Search Engines installed with Firefox 3.6

Source: Mozilla Links

Recently a forum member over at Go Firefox! was getting the below error whenever they tried to install a GreaseMonkey Script. They recently reinstalled Firefox with a fresh profile. They could install GreaseMonkey without issue but any time they tried to load up a script they got this ugly error:

Now, I know I had seen that error before but still took some searching to find the solution. Turns out this is caused by either a missing or damaged GreaseMonkey folder inside the profile folder. The fix is fairly simple and should only take a couple minutes:

  1. Locate Firefox Profile Folder.
  2. Check to see if there is sub folder called gm_scripts chances are it won’t be there. If it is missing go ahead and create it. In Windows Explorer go to File >> New >> Folder.  This will create a folder called New Folder, rename this to gm_scripts. Continue to next step
  3. Check this folder to see if there is a config.xml file. If not, in Windows Explorer go to File >> New >> Text Document. This will create a 0 KB text file called New Text Document.txt , rename this to config.xml

Note: If you have not previously installed any GreaseMonkey scripts and the gm_scripts folder is present with files and folders inside of it, delete the contents inside the gm_scripts folder and then recreate the config.xml file as described in step 3.

Recently there has been a fake Firefox update page (see below) has been floating around the web. This page not only tells the user they are running an out-dated version of Firefox, but that they need to update Adobe Flash Player as well. There is a link to “update” Adobe Flash Player but this is actually a malicious link:

The download starts automatically. Save and run it and you get a rogue antivirus product named “SecurityTool” which starts finding threats which aren’t there and demanding payment in order to remove them.

Fake Firefox Update Screen

With the recent increase in Firefox updates (especially for Firefox 3.6) it is easy for users to get mislead into thinking there is a new update. Some tips to protect yourself against fake update notices:

  • Update notifications are normally delivered via a pop-up window not a web page
  • Use the Check For Updates… feature under the Help Menu if you are unsure about an ‘update notice’. If there is an update available you will get the pop-up window as described above.
  • Mozilla has an official site where you can check to make sure your plugins (such as Flash Player) are up to date: www.mozilla.com/plugincheck The browser normally does not alert you to out-dated plugins.
  • Current release information is posted on the main site (ffextensionguru.com) and is usually update within a few hours of the new releases. We always post a blog entry for any new releases (including the current developmental version). Also we publish a weekly Release Recap every Saturday morning.

Thanks to Gareon for posting this alert at Go Firefox!

Source: PC Magazine

Make Firefox a bit more netbook-friendly

Posted: Tuesday, July 27, 2010 by gareon in Add-ons, Firefox, Tips & Tweaks
Tags:


” I’ve never exactly had a problem running the Firefox web browser on a netbook. But I do tend to disable a few toolbars so that the browser UI doesn’t take up too much screen real estate. When you’re using a 1024 x 600 pixel display, every pixel counts.
One user has gone a few steps further and created a collection of 10 add-ons for Firefox designed to improve the experience of using the browser on netbooks with small screens and relatively slow processors…. “

Source: Netbook Optimization Kit makes Firefox a bit more netbook-friendly
http://www.liliputing.com/2010/07/netbook-optimization-kit-makes-firefox-a-bit-more-netbook-friendly.html

Firefox 4 Beta 2 Breaking Extensions

Posted: Friday, July 23, 2010 by El Guru in Add-ons, Blogs, CyberNet, Firefox, Fx 4.0, Mozilla News

This recent news concerning the next Beta release of Firefox 4 which is due out either later today or Monday surprises me. While it is not unusual for developmental releases to break current extensions it seems odd that Mozilla would choose to do this during the Beta phase and this is going to break a lot more extensions than ‘normal’. Usually by the time a an upcoming major Firefox release reaches the beta phase major changes have already been implemented. However, Firefox 4 Betas are a little different than previous Betas.

Prior releases were labeled as Firefox 3.7/Gecko 1.9.3 and were still being built on the current Gecko 1.9.x rendering engine. When the first beta came out earlier this month for this upcoming version of Firefox it was re-numbered to Firefox 4 because now it is being built off of the new Gecko 2.0 rendering engine.

The breakage is due to an XPCOM change and being implemented as part of Gecko 2. CyberNet News’ Ryan explains in Firefox 4 Beta 2 Will Break Many Extensions (emphasis is mine):

This XPCOM change. Many extensions, including CyberSearch, use what’s referred to as components in their code. This change landed in the nightly releases shortly after Firefox 4 Beta 1 was made available, and it reworks the way these components get registered with the browser. The fix is pretty easy, and should take extension developers very little time (took me about 30 minutes) to update their add-ons. The problem is that there are so many add-ons that have been abandoned by their developers, and that will likely leave a lot of users frustrated.

So why the change? Well, it’s better in the long run. Previously if you did anything with an extension (install, remove, enable, disable, etc…) you would have to restart your browser, and doing so would require ALL of your browser components to have to re-register. With the way it was set up every component would be “loaded and executed, then unloaded, then reloaded again during the restart.” You’ll still need to restart your browser after installing/updating extensions, but now the components are pulled directly out of the extension’s manifest file which avoids many of the otherwise poor side effects. Not only that, but as Mozilla points out this is a good move in helping to make Firefox multithreaded.

Unfortunately this new change means it is no longer going to be as simple as downloading the extension to your local system and hacking the install.rdf file then installing the modified extension. Simply bumping the max version as described in the Manually Updating Add-ons to Work post from last month likely won’t work any longer. While Ryan says the fix pretty easy and only about took 30-minutes, he is an extension developer. Somehow I doubt this is going to be something the average to semi-advanced Firefox user is going to be able to do to make their favorite extension work with Firefox 4. This is defiantly something I am going to have do some more research on. Look for a/some follow-up post(s) in the coming days.