874
edits
Do Not Fool: Difference between revisions
Jump to navigation
Jump to search
added a "wait, is this really a joke?" section
m (corect header name in intro section) |
(added a "wait, is this really a joke?" section) |
||
| Line 40: | Line 40: | ||
* Clicking privacy/advanced/privacy enables the injection. | * Clicking privacy/advanced/privacy enables the injection. | ||
* The [https://builder.addons.mozilla.org/addon/1001305/latest/ latest revision of DNF] supports the nightly. | * The [https://builder.addons.mozilla.org/addon/1001305/latest/ latest revision of DNF] supports the nightly. | ||
== Wait, Is This Really a Joke? == | |||
It was originally intended as such, but as Twitter will tell you, there are actually lots of people who need to get actual work done on April 1, and the ambiguity between what's real and what's not is a barrier to that. | |||
However, a custom header isn't necessarily the best solution because: | |||
* It requires pranksters to do additional work by accomodating for people who don't want to be fooled. This is particularly difficult for resource-constrained organizations that are just trying to have a little fun on April Fools'. | |||
* It's potentially a privacy violation for end-users because they're essentially broadcasting to every site they visit that they dislike April Fool's day. That makes it easier for sites to learn more about their identity. | |||
A more pragmatic and privacy-respecting approach to a "real" Do Not Fool feature might be to crowd-source a custom "April Fools' blacklist" from Twitter, and warn users visiting a pranked page via a door-hanger notification, or through a page similar to the [http://www.mozilla.com/firefox/its-a-trap.html reported web forgery] warning. | |||