Muhammad Zulfikar — Blog Docs

Apple MacBook Pro, Specification : 15.4 inch LCD LED display, 2.4 Ghz Intel Core 2 Duo, 256 MB GDDR Nvidia 8600M GT, 4 GB of RAM, 160 GB HDD.

Ever since its debut, Firefox has garnered a reputation for being an enormously customizable program, both through its add-on architecture and its internal settings. In fact, many of Firefox’s settings aren’t exposed through the Tools > Options menu; the only way to change them is to edit them manually. In this article, we’ll explore some of the most useful Firefox settings that you can change on your own and that aren’t normally available through the program’s graphical interface. The closest analogy to how Firefox manages its internal settings is the Windows Registry. Each setting, or preference, is given a name and stored as a string (text), integer (number) or Boolean (true/false) value. However, Firefox doesn’t keep its settings in the registry, but in a file called prefs.js. You can edit prefs.js directly, but it’s often easier to change the settings through the browser window.

Type about:config in the address bar and press Enter, and you’ll see all the settings currently enumerated in prefs.js, listed in alphabetical order. To narrow down the hundreds of configuration preferences to just the few you need, type a search term into the Filter: bar. (Click the Show All button or just clear the Filter: bar to get the full list back again.)

To edit a preference, double-click on the name and you’ll be prompted for the new value. If you double-click on an entry that has a Boolean value

Before you begin but it’s often easier to change the settings through the browser window. Here are a few caveats to keep in mind as you explore and tweak:

Not everyone will get the same benefits by enabling these tweaks. This is especially true for changing the network settings. If you habitually visit sites that don’t allow a large number of connections per client, for instance, you won’t see much benefit from raising the number of connections per server. Some hacks may have a limited shelf life. With each successive release of Firefox, the need for tweaking any of the performance-related config settings (like the network settings) may dwindle as Firefox becomes more self-tuning based on feedback from real-world usage scenarios. In short, what works now may not always work in the future — and that might not be a bad thing. Keep a log of everything you change, or make backups. If you tweak something now and notice bizarre activity in a week, you’ll want to be able to track back to what was altered and undo it. Firefox does show which about:config changes have been set manually, but this isn’t always the most accurate way to find out what you changed.

To make a backup of your preferences in Firefox, just make a copy of the file prefs.js, which is kept in your Firefox profile folder. If you mess something up, you can always copy this file back in. (Be sure to shut down Firefox before making a copy of prefs.js or moving a copy back into the profile folder!)

In Windows XP, the profile folder is
\DocumentsandSettings\\Application Data\Mozilla\Firefox\Profiles\.default\

In Windows Vista, this folder is
\Users\\AppData\Roaming\Mozilla\Firefox\Profiles\.default\

Note that Application Data and AppData are hidden folders by default, so they may not show up unless you force Explorer to show hidden objects. (Open the Control Panel, double-click Folder Options, select the View tab, select “Show hidden files and folders” and click OK.)

In Mac OS X, the profile folder is
/Library/Application Support/Firefox/Profiles/.default/

and in Linux it’s
~/.mozilla/firefox/.default/

but on those platforms it’s usually quicker simply to search for prefs.js.

Alternatively, you can use the handy Firefox Extension Backup Extension (FEBE). It backs up not only the prefs.js file but just about every other thing in Firefox — extensions, themes, cookies, form history and so on.

Lagi males nulis pake english nih, lagi pingin cerita pengalaman kemarin dan minta solusinya. Ceritanya, kemarin siang, setelah selesai motret-motret, saya kepikiran buat upload gambar dengan cara memasukkan memory melalui card reader yang ada di notebook saya. sebelumnya, saya selalu menggunakan kabel USB yang langsung dihubungkan ke camera. Pada waktu itu saya menggunakan Windows Vista Home Premium karena di ubuntu card reader saya tidak terdeteksi. Ketika saya memasukkan memory (Stick Duo pake’ sambungannya) terasa sangat berat, tapi saya coba tekan hingga akhirnya masuk ke card reader. Kemudian, Windows pun mendeteksi (Muncul tulisan “Found New Hardware”), tetapi, setelah 2 detik, tiba-tiba notebook saya mati dan card reader mulai mengeluarkan asap dan bau gosong, langsung saja, saya tarik memorynya dan ternyata gosong di bagian sambungannya. Setelah memorynya saya ambil dari sambungannya, Alhamdulillah, memorynya masih terdeteksi di camera digital saya, dan laptop saya masih bisa menyala seperti biasa walaupun masih bau gosong. Sampai hari ini saya masih belum mencoba memasukkan memory lain (karena cuma punya satu).

Saya ingin minta pendapat dari teman-teman semua, kira-kira kenapa hal itu bisa terjadi ? dan yang rusak memorynya atau card reader di notebook ?.

Google has unveiled OpenSocial, a set of APIs for building social applications online. OpenSocial is a set of application programming interfaces (APIs) that will allow web developers to create applications for a variety of social networks, rather than having to learn a different markup language for each new social networking platform.

The list of web organisations already signed up to use OpenSocial is already lengthy, and crucially - as far as competitor Microsoft and part MS-owned Facebook are concerned includes social networking giant MySpace. According to Google, the release of OpenSocial marks the first time that multiple social networks have been made accessible under a common API, potentially making development and distribution easier for developers.