Manage Services List

Begining with termBlaster 2.0, termBlaster services can be managed using FireFox's Library. To access the Library, select Bookmarks -> Organize Bookmarks (or press CTRL + SHIFT + B). In the Library, you can find a folder called "termBlaster" under All Bookmarks -> Unfiled Bookmarks -> termBlaster. Within this folder, you can:

Add a service

1. Right-click on the folder you want the item added to, then select New Bookmark.
2. Fill in the name, then for the "Location" field: enter a Service URL.

Edit a service

1. Right-click on the service you want to edit, then select "Properties".
2. Fill in the name, then for the "Location" field: enter a Service URL.

Delete a service

1. Right-click on the service you want to delete, then select "Delete".

Pin a service on the Quick List

The Quick List is the list of Services displayed below the "Search Selected With", within "Quick List" submenu, and in the Search Blaster. It allows you to quickly select one of your favorite services.

1. Select service you want to pin to the Quick List.
2. Near the bottom right of the window in the "Tags" field, enter in "termblaster quick"
• You can change the tag used from "termblaster quick" to whatever you want in the termBlaster options.
3. At the time of writing, you will need to restart Firefox for the change to be visible. The FireFox API does not yet support a way to keep track of this.

Notes

Service URL

This URL is what termBlaster will use to make requests to the service. For most websites, you can just:

1. Search for "termblaster" (without the quotes) using the service you want to add.
2. Wait for the results page to finish loading.
3. The service URL is the page's address with "termblaster" replaced by "$s"
4. Note: without the quotes and with a lower-case "s"

If "termblaster" does not appear in the page's address, these are few and are not covered in this guide.

Sometimes Services do not allow GET requests so support for POST may be available in the future; however, most services that were designed to take POST'd data can also handle GET requests so this feature has very low priority.