All images must be yours or must be original images that you have permission to share

Single images should be clear, well focused, well composed and of a high resolution. If you are submitting a set, they should be of at least decent quality and should tell a story.

All images must be accompanied by a detailed description so that it makes sense to those viewing it. What does the image show? Where was it captured? When was it captured? What is the story behind it?

The preferred method to submit images is to upload them to a free image hosting service and then paste the direct links to the images in the message text box below. You can get the direct links to the image files by left-clicking each image and then clicking "Copy image location" or "View image" and then copying the URL in your browser address bar. A direct link to your image file will end in .JPG.

If you are unable to upload your images to a hosting service for some reason, then you may submit images, one at a time, by attaching them below as long as the file size is less than 10 MB. Understand that email is not the best way to send large attachments and so i may not receive your images. If you have sent an image and it does not get posted to this website after a couple of days, please contact me.

Unless you specifically remove it, your images will likely contain EXIF data. This data may contain detailed information about your camera and its settings, but may also contain the GPS based location at which an image was captured. While in some cases you may want your images to include this data, it is also possible that you may not. If you do not want EXIF data included with your image, please remove it before uploading or sending it (some image hosting services will remove it automatically). If you are unable to remove it and you want it removed, let me know and i will remove it for you.

I quickly realized what i got myself involved in when i started publishing my own user.js file in that it’s a lot of work to keep pace with the rapid development cycle of Firefox and i began to dread sifting through a large and ever-growing list of preferences every time i published an update. As such, i decided to piggy-back on the excellent work done by ‘Pants’ and his helpers whose custom user.js file has become rather popular since it was first published by Martin Brinkmann on Ghacks. Just a couple of days ago Pants also published his work on GitHub which i think was a great idea that will attract even more contributors.

So what does all this mean to you, the guy or gal that uses my user.js? Well, initially it means you’re going to have a lot of work to do insomuch as you’re going to have to go through the entire user.js file all over again from top to bottom. Sorry about that, but scope of this update meant it would have been extremely time consuming for me to document every single change. The good news is that future updates will be a lot easier.

The format of the new file and everything you need to do is explained in my guide. In short, i am using Pants’ configuration almost verbatim, other than commenting out a few of his preferences, and then appending my personal settings to the end of his.

A new tutorial was added that offers some information and software resources for fixing and formatting your MP3 collection on Debian based Linux distributions (Debian, Ubuntu, Mint). None of the software tools require Wine. Read more here: An MP3 Collection Editing Guide For Linux