Civil Rights
Movements, leaders, victories and the continuing fight for equality.
q2K BHP
Black History Portal
THE BHP WIRE —
HIDDEN TRUTHS
What's New!
Explore the people, places, events, achievements, struggles and stories that shaped our journey.
Movements, leaders, victories and the continuing fight for equality.
Innovation, patents, science, technology and world-changing contributions.
Pioneers, champions, Negro Leagues, records, activism and excellence.
Meet the people whose lives, choices and achievements shaped the journey.
Black towns, communities, institutions and places where history happened.
Moments that changed communities, movements, institutions and the nation.
In August 1908, a white mob attacked Springfield, Illinois’s Black community, destroying homes and businesses and lynching two Black men. National outrage over the violence helped spur the movement that created the NAACP the following year.
MORE →Reflects the personal views, recollections, and perspective of the author, Mike Davis.
This is a personal recollection on the Move fire on May 13, 1985
| Greasemonkey | |
|---|---|
 | |
| Original author | Aaron Boodman |
| Developers | Anthony Lieuallen, Johan Sundström,[1] 13 more[2] |
| Release | 6 December 2004[3][4] |
| Stable release | 4.14
/ 2 June 2026 |
| Written in | JavaScript, XUL, CSS |
| Operating system | Cross-platform |
| Available in | English |
| Type | Mozilla extension |
| License | MIT License |
| Website | www |
| Repository | |
 |
| Related articles |
|---|
| Origins and lineage |
| Category |
Greasemonkey is a userscript manager made available as a Mozilla Firefox extension. It enables users to install scripts that make on-the-fly changes to web page content after or before the page is loaded in the browser (also known as augmented browsing).
The changes made to the web pages are executed every time the page is viewed, making them effectively permanent for the user running the script.
Greasemonkey can be used for customizing page appearance, adding new functions to web pages (for example, embedding price comparisons within shopping sites), fixing rendering bugs, combining data from multiple web pages, and numerous other purposes.
The Greasemonkey project began 28 November 2004, written by Aaron Boodman.[5][6][7] Boodman was inspired to write Greasemonkey after looking at a Firefox extension designed to clean up the interface of AllMusic,[8] written by Adrian Holovaty, who later became a userscript developer. By May 2005, there were approximately 60 general and 115 site-specific userscripts distributed for Greasemonkey.[8] In July 2005, serious vulnerabilities were found in Greasemonkey by Mark Pilgrim,[9][10] and fixed in the 3.5 version of Greasemonkey.[11] During this time, a Greasemonkey compiler was also developed for converting a userscript into a standalone Firefox extension.[12] Greasemonkey was initially met with complaints by publishers for its ability to block ads.[13] However, this criticism shifted its focus to other addons starting with the 2006 release of Adblock Plus.
To accommodate the growing number of scripts, userscripts.org was founded by Britt Selvitelle and other members of the Greasemonkey community in late 2005. Userscripts.org was open sourced in 2007 but the site later moved away from this code base.[14] As the main script repository listed on Greasemonkey's official site, userscripts.org accumulated thousands of scripts per year.
In 2010, the last known admin Jesse Andrews posted that the site was in maintenance mode due to lack of time and asked for a new maintainer to volunteer.[15] Nevertheless, he remained the sole admin of the site until a discussion about install counts began on 1 April 2013.[16] Prior to this, many of the "most popular scripts" as listed by the site had nominal install counts of zero. Over the following year spam scripts became more common, server downtime increased and the install count bug remained.[17] With no further communication by Andrews, userscript writers described the site as neglected and the official Greasemonkey site removed its front page link.[18][19] In response, script writers and other developers began working on the fork "openuserjs.org",[20][21] and later greasyfork.org,[22] as an immediate replacement.[23]
In May 2014, userscripts.org became inaccessible on port 80, prompting users to access it on port 8080 instead.[17] In August 2014, the site was shut down completely. Most of its scripts were backed up to the static mirror userscripts-mirror.org where they can now be found.[17]
Greasemonkey user scripts are written in JavaScript and manipulate the contents of a web page using the Document Object Model interface. Scripts are generally written to be either page-specific or domain-specific (applying to all pages within a domain) but may also be tagged to apply to all domains for global browser enhancements. Users of Greasemonkey can write or download scripts and save them to their own personal library. When users visit a website matching a script in their personal script library, Greasemonkey invokes the relevant scripts.
Greasemonkey scripts can modify a webpage in any way that JavaScript allows, with certain Greasemonkey security restrictions. Scripts can also access other web pages and web services via a non-domain-restricted XMLHTTP request, allowing external content to be merged with the original page content.
Scripts are named somename.user.js, and Greasemonkey offers to install any such script when a URL ending in that suffix is requested. Greasemonkey scripts contain metadata which specifies the name of the script, a description, resources required by the script, a namespace URL used to differentiate identically named scripts, and URL patterns for which the script is intended to be invoked or not.
Writing a Greasemonkey script is similar to writing JavaScript for a web page, with some additional allowances such as cross-site XMLHttpRequests. Compared to writing a full-fledged Firefox extension, user scripting is a very modest step up in complexity from basic web programming. However, Greasemonkey scripts are limited due to security restrictions imposed by Mozilla's XPCNativeWrappers[24] For example, Greasemonkey scripts do not have access to many of Firefox's components, such as the download manager, I/O processes or its main toolbars. Additionally, Greasemonkey scripts run per instance of a matching webpage. Because of this, managing lists of items globally is difficult. However, script writers have been using cookies, and Greasemonkey even offers APIs such as GM_getValue and GM_setValue to overcome this.
File hosting servers for Greasemonkey require that the URLs for the scripts end with .user.js and not with a MIME type like text/html. Support for HTTPS will meet with[clarification needed] Greasemonkey's built in update checker. As of July 2019, the Greasemonkey project lists three recommended user script hostings:[25]
Greasemonkey is available for Firefox, Flock, and GNOME Web (formerly called Epiphany). The Greasemonkey extension for Web is part of the Web extensions package. However, this extension is not fully compatible as of release 2.15.1, since some Greasemonkey API functions (e.g. GM_getValue) are unsupported. There are also custom versions for SeaMonkey,[26][27] Songbird,[28] Pale Moon,[29] qutebrowser,[30] and Falkon browser.
Media related to Greasemonkey at Wikimedia Commons
Source: Wikipedia. Article content is retrieved live through the MediaWiki API.
Greasemonkey is a userscript manager made available as a Mozilla Firefox extension. It enables users to install scripts that make on-the-fly changes to web page content after or before the page is loaded in the browser (also known as augmented browsing). The changes made to the web pages are executed every time the page is viewed, making them effectively permanent for the user running the script. Greasemonkey can be used for customizing page appearance, adding new functions to web pages (for example, embedding price comparisons within shopping sites), fixing rendering bugs, combining data from multiple web pages, and numerous other purposes.
A userscript manager, also known as a userscript engine, is a type of browser extension and augmented browsing technology that provides a user interface to run and organize userscripts. The main purpose of a userscript manager is to execute scripts on predetermined webpages as they are loaded, for example, running a userscript to modify only youtube.com pages. But, userscript managers do a lot more than execute scripts, and screen for the pages they are intended to run on. The most common operations performed by a userscript manager include installing, organizing, creating, copying, saving, deleting, and editing (including modifying webpage permissions of) userscripts. Userscript managers use metadata that is embedded in a script's source code primarily to determine the websites it should execute on and the dependencies necessary for the script to run properly. Metadata can also include information that is useful to the user such as the script's name, author, description and version number. Popular userscript managers include Tampermonkey, Greasemonkey, Violentmonkey, and Userscripts for Safari. The Gear browser for iOS has a userscript manager built in.
Grease monkey may refer to: Grease monkey, a slang term for a mechanic Grease Monkey (business), a franchised chain of automotive service centers Greasemonkey, an extension for Mozilla Firefox Grease Monkey, a comic Grease monkey, a slang term for a slightly built burglar with entry skills.
IE7Pro is an add-on for Internet Explorer 6, 7, and 8 that aims to enhance the feature set provided by the browser. IE7Pro adds features such as tab enhancement, an ad blocker and flash blocker, mouse gestures, inline search, privacy enhancements, online bookmark service, Greasemonkey-like user script support, and plug-in support. IE7Pro is available in several languages – this is made possible by user translations. The support of the product was discontinued after the release of minor version 2.4.7 before Internet Explorer 8 was fully supported. The support of the product was continued again and a new version, IE7Pro 2.5.1 was released on June 2, 2010. However, the website's forum link and the Help & FAQ link are both dead. As of the latest version, 2.5.1, there are still some minor incompatibility issues with IE8 (the IE7Pro icon does not display in the status bar and the flash blocker does not work).
Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.
MORE →Shirley Chisholm, elected in 1968.
