© 2022 - aleteo.co
Greasemonkey allows you to customize the way popular websites look and behave by tweaking their functionality with a script. In fact Greasemonkey is not an application in itself. It’s a Firefox add-on that prepares your browser to support Greasemonkey scripts. The add-on puts a small monkey icon in the bottom right corner, from where you can. AnonymoX for Chrome is an add-on that gives you fast, anonymous browsing in the click of a button. If you're concerned about privacy online, anonymoX is a good option. When enabled, you'll be able to pick a random IP, delete cookies and view your public IP, all with a view to making life online just that little bit safer. Turkopticon helps the people in the 'crowd' of crowdsourcing watch out for each other—because nobody else seems to be. Almost half of the Mechanical Turk workers who wrote their Bill of Rights demanded protection from employers who take their work without paying. How to Install ADB and Fastboot On Windows 15 SECONDS Download Google Camera 8.1 From Google Pixel 5 Phone GCam 8.1 Apk How to Install ADB on Windows, MAC, and Linux UPDATED – 2019. Greasemonkey is the User Scripts API/extension system used by Firefox - but the User Scripts used in Chrome and Firefox are so similar, I figure its still relevant to link it. Hope this helps! How to use Chrome User Scripts.
F.B. Purity is compatible with the following web browsers: Firefox, Google Chrome, Edge, Safari, Opera, Brave and Maxthon, running on Windows, Mac, Linux etc. Installation instructions are listed below:
After installing F.B. Purity, please read the F.B. Purity User Guide for information on how to use its various functions and also how to customise FBP's settings and options.
Next step: Please click the 'Share' button below, to share this page with your friends, so they will also be able to benefit from a cleaned up and customized Facebook too:
Get the latest updates: click 'Like' on the F.B. Purity Fan Page on Facebook, so you will be kept up to date on news of the latest versions of FBP, when they are released.
Problems? If you have any problems getting FBP working, want to uninstall, or have any questions about it whatsoever, please read the F.B. Purity Help / FAQ (Frequently Asked Questions) page, as the solution to your problem or answer to your question will almost certainly be there.
Support FBP: If you like F.B Purity, please Donate to show your appreciation of all the hard work i have put into developing this and keeping it running.
N.B 'Facebook' is a registered trademark of Facebook Inc. This site and the F.B Purity extension/script are neither endorsed by or affiliated with Facebook.
Terms and Conditions : Use F.B. Purity at your own risk, it comes with no warranty or guarantee, neither explicit or implicit towards functionality or usability. The author shall not be held liable for any damage or loss of data caused by use of this program. By downloading and installing Fluff Busting Purity, you agree to these terms.
If the metadata block includes a key that Greasemonkey does not understand, it will be ignored.
The metadata block must follow the format:
It must use line comments (
//) like above, not block comments (
/* */).Note that the opening
// UserScript and closing
// /UserScript must be precisely at the beginning of its line.Some keys may have multiple values.In all cases the key and value(s) are separated by whitespace.The closing
/UserScript line should be at the end of the metadata block (not at the end of the script).
Just a brief summary of what the script does, presented to the user as the script is installed, and in the manage dialog.
As of Greasemonkey 2.2: can be localized for multiple languages; see the #@name documentation for more detail.
Examples: see @include
See Include and exclude rules.There can be any number of @exclude rules in a script.
See dedicated @grant page.
The icon is, as of Greasemonkey 0.9.0, displayed in the script management interface.Almost any image will work, but a 32x32 pixel size is best.This value may be specified relative to the URL the script itself is downloaded from.
See Include and exclude rules.There can be any number of @include rules in a script.
@match metadata imperative is very similar to
@include, however it is safer.It sets more strict rules on what the
* character means.
For details, see the documentation on Match Patterns for Google Chrome.Chrome implemented
@match first, and Greasemonkey has been designed to be compatible.
The name of the script.This appears in the monkey menu, and is also the unique identifier of a script (within a namespace).If no name is provided, it will be derived from the file name.
As of Greasemonkey 2.2: can be localized for multiple languages, for example:
Add a colon and the locale code, which is the ISO 639 language code and optionally a hyphen and ISO 3166 country code, when disambiguation is necessary.When the user's browser is configured with the matching primary language, that value will be displayed instead.
The combination of namespace and name is the unique identifier for a Greasemonkey script.If a script is being installed, and a script with that same name and namespace already exists, it will be replaced by the new script.Otherwise, the new script is added to the set of installed scripts.A script author will usually put all of their scripts under one common namespace, and then assign each script a unique name.
While the namespace is non-semantic, a URL is often used.Some authors use the common home page for the collection of scripts they have written.But remember, the namespace can be any unique value.
When present, this imperative restricts the execution of the script.The script will run only in the top-level document, never in nested frames.It takes no arguments, it is either present or not present.This is off (scripts run in frames) by default.
There can be any number of @require keys in a script.Each @require is downloaded once, when the script is installed, and stored on the user's hard drive alongside the script.The URL specified may be relative to the URL the script is being installed from.
Note that since Greasemonkey 0.9.0, if Greasemonkey detects that the
@require value(s) have been altered, these new values will be used (thus each
@require shall be re-downloaded).
There can be any number of @resource keys in a script.
Each @resource is downloaded once, when the script is installed, and stored on the user's hard drive alongside the script.The URL specified may be relative to the URL the script is being installed from.
These named resources may be accessed through GM_getResourceText and GM_getResourceURL respectively.
Note that since Greasemonkey 0.9.0, if Greasemonkey detects that the
@resource value(s) have been altered, these new values will be used (thus each
@resource shall be re-downloaded).
This key supports three values:
To detect if you are running at
document-start time, check the value of
Scripts running at
document-end will have the value
Two metadata imperatives allow downloading files (once, at install time) for efficient reference:First @require, which includes a remote code resource.Second @resource, which makes a remote data resource available.
It is possible to add a new entry for either of these values, while editing a script that is already installed.In either case, simply add the appropriate line and the referenced file will be downloaded and made available the next time the script runs.If you specify a relative URL, then it will be interpreted as relative to the the URL the script was originally downloaded from.