Former name: Facebook Content Filtering
Version: 2.1.0
Currently upgrading
As 2.1.0 are currently under construction, this code will ge updated very soon, with the new variables.
For version 2.0.0.2, see where.
Configuration
Descriptive states
| State color | Meaning |
|---|---|
GREEN | Indeed an active configuration key |
YELLOW | Undocumented, inofficial, secret |
BLUE | Deprecated. Removed in future. |
RED | Obsolete, probably removed |
| Variable | State or version | Default value | Description |
|---|---|---|---|
Enabled | 2.1.0 | 1/ON | Disabling the full extension when you want to pause is no more. Just use this one. |
Debug | 2.1.0 | 0/OFF | Show information in console when working with the censorship |
BorderizeMe | 2.1.0 | 1/ON | Put a red warning border around marked content |
BlacklistNotifications | 2.1.0 | 0/OFF | "Notify me about details when I'm choosing to block something" Meaning: Every time you choose to block something by right clicking on it, you'll get a notification (alert) of exactly what you blocked. Might be good, if you're unsure what you really are blocking. |
BlacklistRequireConfirm | 2.1.0 | 0/OFF | Before adding something to the blacklist, user has to confirm |
utf8_decode | 2.1.0 | 1/ON | Apply utf8_decode on URIs |
HandleFacebookTimeLine | 2.1.0 | 0/MARK | Renamed! Rules of element handling - On Facebook, and found blacklisted words in the timeline, the element of choice will get replaced with a "this one is removed"-message instead of total removal |
HandleFacebookComments | 2.1.0 | 0/MARK | Renamed! Rules of element handling - On Facebook, and found blacklisted words amongst comments, the element of choice will get replaced with a "this one is removed"-message instead of total removal |
HandleFacebookCommentReplys | 2.1.0 | 0/OFF | New! If this extension finds out that a comment contains a blacklisted word, this option will decide on how to handle comment-replies. If this setting is off, you will se a comment, replaced with "this one is removed", and all other replies remain in place. If this setting is on, the extension will - as it is replacing the comment with "this one is removed" also clean up amongst the replies (as in: purged) |
HandleUnsupported | 2.1.0 | O/OFF | New! How to handle unspecified detected elements (normally occurs outside Facebook and in a shitload of cases, while scrolling through the Facebook-timeline). In tests, this part has been the most function. |
AllowUnsupported | 2.1.0 | O/OFF | New! To use the features for unsupported elements this has to be activated first. |
RescanOnUpdates | 2.1.0 | 0/OFF | New! This defines how to act when you add new blacklisted objects into the list. If this one is active, there will be an instant rescan of the current page as you add the word. |
LegacyScanning | 2.1.0 | 0/OFF | Legacy scanning is about adding an extra interval (setInterval) for the current site, so even if we try to detect stuff in realtime, this setting activates an extra interval-scanner, that rereads all elements, with an interval of two seconds. This may affect performance, and has mostly been used for testing purposes. |
useClearFixFailOver | 2.1.0 | 0/OFF | Experimental: To find some suggested links on Facebook, we can look for clearFix-elements when userContentWrapper is missing on a bad match.
|
LoopedIntervals
| 2.0.0.2 | N/A | Removed! How many loops that should be run before shutting down. This is considered "How long is the user running around in the Facebook scrollback before updating the window?" and we don't really need to run this eternally |
uficomment | 2.0.0.2 | N/A | Removed! [Recursive scans] Sets the depth to scan for badwords in comments Should normally not be needed to change |
usercontentwrapper | REMOVED | N/A | Removed! [Recursive scans] Sets the depth to scan for badwords in timeline posts Should normally not be needed to change |
The art of blocking content
There will be some changes here, so the former content has been removed and will not be updated until an official release of version 2.1.0