Easter Egg Is Confusing  ## Metadata - Author: [[wordpress.org]] - Full Title: Easter Egg Is Confusing - Category: #articles - Document Note: --- tags: - #wordpress - #ux - #openSource Author: wordpress.org contributors (Trac discussion: lead devs and community members) Source: WordPress Core Trac Reference: https://core.trac.wordpress.org/ticket/12816 date created: 2025-08-21 00:00 --- # Title: “Easter egg is confusing” — WordPress Core Trac discussion on the revisions easter egg ## Table of Contents: - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#-notes) - [📖 References](#-references) - [🗣️ Paraphrase](#-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment](#-deib-diversity-equity-inclusion-and-belonging-assessment) - [✅ Logical validity](#-logical-validity) - [🔍 DARVO Analysis](#-darvo-analysis) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ### References: - WordPress Core Trac ticket 12816 - Related references mentioned in-thread: #15262, #24852 ## 📝 Summary: This Trac thread debates a WordPress admin “easter egg” that appears when users compare a post revision to itself in the Revisions screen. Some contributors argue it’s confusing, unprofessional, and occasionally flagged as malware due to obfuscated JS. Others defend it as harmless tradition, citing other software’s easter eggs and proposing un-obfuscation or providing hooks to disable it. The ticket cycles through wontfix/closed and is later revisited when the Revisions UI changes make the egg unreachable, prompting removal and suggesting a plugin for those who want it. Key positions: - Defense: It’s harmless and explanatory (“Self-comparison detected”), common in software culture, and could be kept if un-obfuscated and enqueue-able. See remarks by @nacin (14 years ago) and @dd32 (14 years ago). - Critique: Confuses non-technical users, looks unprofessional/like malware, violates GPL spirit due to obfuscation, triggers false positives. See @thomasq (14 years ago), @filosofo (14 years ago), @Lletnek (14 years ago), @biziclop (14 years ago). - Pragmatic path: Provide hooks/filters to disable; later, removal when it’s no longer reachable, with a plugin alternative. See @ericmann (14 years ago) and @adamsilverstein (11 years ago). Direct anchors to selected comments: - @nacin notes it’s been in since 2.6 and issues are about obfuscation, not existence. [“been in WP for two years”] - @sivel closes as wontfix: “I honestly see no harm in this.” [“Closing as wontfix.”] - @thomasq: user confusion and professionalism concerns. [“lost in the middle of nonsensical messages”] - @filosofo: GPL and security optics concerns; suggests a filter. [“violates the GPL 2”] - @Lletnek: client-facing harm; calls to remove. [“could potentially lose people clients”] - @strider72: options: clarify, hide better, remove, un-obfuscate. [“Make it less obscure/bizarre OR…”] - @dd32: support un-obfuscation and proper enqueueing. [“+1 for adding it in as revisions-egg.js”] - @biziclop: antivirus false positives. [“Virus Detected and Removed”] - @ericmann: wants a hook to disable for certain clients. [“reopened”] - @ianatkins: hook as solution; context confers authority. [“The context gives the message authority.”] - @RavanH: remove for multisite subsites; shares workarounds. [“VERY likely to cause panic”] - @jane: wontfix; “soul, etc” with link added elsewhere. [“We’re not taking the easter egg out”] - @adamsilverstein: time to remove; plugin to re-enable. [“see #24852”] ## 📖 Main Content: This discussion captures a classic product governance tension: playful culture vs. professional UX and compliance. The “revisions self-compare” easter egg lives in admin JS, initially obfuscated, triggering: - UX risks: Non-technical editors misinterpret it as an error/hack, especially because it’s surfaced in a core workflow (revisions), not via a hidden trigger. - Security/compliance optics: Obfuscated admin JS resembles compromised files; can trip antivirus heuristics; raises GPL source availability concerns. - Community compromise: Supporters propose un-obfuscation and enqueueing (so it can be dequeued), or adding a filter/hook to disable. Critics push for removal, especially for client-facing and multisite contexts. - Resolution arc: Initially closed as wontfix with cultural justifications. Later, as the Revisions UI changes, maintainers agree to remove it (no longer reachable) while providing a plugin path for nostalgia. Personal reflections: - The most compelling critique is that context matters: an egg embedded in a core editorial task inherits the authority of that context, so ambiguity becomes UX debt. The pragmatic governance approach—expose a hook or move to a plugin—aligns with WordPress’s extensibility ethos and open-source best practices. - The licensing/security optics lesson is durable: avoid obfuscation in core; transparency builds trust and eases audits. ### 🗒️ Notes - History and status - “In WP since 2.6; complaints mostly about obfuscation” — @nacin (14y) - Initially closed as wontfix: “I honestly see no harm” — @sivel (14y) - UX concerns - Confusion for non-geek editors; “Self-comparison detected” buried among odd messages — @thomasq (14y) - “Context gives the message authority” (it’s in a core workflow) — @ianatkins (14y) - Multisite sub-sites: higher risk of panic — @RavanH (13y) - Professionalism and optics - Perceived as unprofessional, “amateurish” — @thomasq (14y) - Looks like a hacked file; obfuscated JS — @filosofo (14y) - Licensing/security - GPL concern: preferred form for modification — @filosofo (14y) - False positives from AV when uploading files — @biziclop (14y) - “False positives happen; update scanner” — @dd32 (14y) - Proposed solutions - Un-obfuscate; enqueue via wp_enqueue_script for dequeuing — @dd32, @nacin (14y) - Add a filter/hook to disable per site/client — @ericmann, @ianatkins (14y) - JS guard to prevent self-compare selection — @anonymized_6443559 (14y) - Removal requests — @Lletnek (14y) - Outcome - “We’re not taking the easter egg out (soul, etc)” — @jane (13y); link added elsewhere (#15262) - Finally: remove due to new Revisions UI making it unreachable; plugin to re-enable — @adamsilverstein (11y) ## 📖 References: - WordPress Core Trac Ticket 12816 - Related: #15262 (added link addressing confusion), #24852 (triggering removal due to UI changes) ## 🗣️ Paraphrase: 1) Original idea (defense, paraphrased from @nacin and @sivel): - Original: “It’s been in since 2.6... only complaints about obfuscation; I see no harm; the message explains self-comparison; closing as wontfix.” - Paraphrase: This behavior has existed for several versions with minimal pushback beyond the code being obfuscated. The UI already indicates when you’re comparing a revision to itself, so the feature doesn’t introduce real harm. We’ll close this without changes. 2) Critical stance (paraphrased from @thomasq and @filosofo): - Original: “Message is obscure; non-geek editors are confused; obfuscated code impeded investigation; appears amateurish; possibly GPL violation; looks like compromised files; propose a filter.” - Paraphrase: The notice is easy to miss and fails to prevent confusion for typical editors. Obfuscated JavaScript complicates troubleshooting and undermines professionalism, potentially clashing with the GPL’s spirit. Because the code resembles malware patterns, adding a filter to easily disable it would be a practical compromise. ## 📰 Newsletter: This week in WordPress: Learning paths, cleaner UX, and community care - Learn web development: Whether you’re starting with PHP/JS or leveling up your Gutenberg skills, map your growth with curated tracks on core APIs, hooks, and testing. Pro tip: practice by writing a small plugin that registers a custom block and integrates REST endpoints—commit early, iterate often. - Recent updates: Remember the classic “revisio - Summary: I honestly see no harm in this. - URL: https://core.trac.wordpress.org/ticket/12816 ##### [Attachments (1)](https://core.trac.wordpress.org/ticket/12816#no1) [easter-egg-revisions-filter.12816.2.diff](https://core.trac.wordpress.org/attachment/ticket/12816/easter-egg-revisions-filter.12816.2.diff)[​](https://core.trac.wordpress.org/raw-attachment/ticket/12816/easter-egg-revisions-filter.12816.2.diff) (656 bytes) - added by filosofo [14 years ago](https://core.trac.wordpress.org/timeline?from=2010-04-02T16%3A46%3A55Z&precision=second). Download all attachments as: [.zip](https://core.trac.wordpress.org/zip-attachment/ticket/12816/) ##### [Pull Requests](https://core.trac.wordpress.org/ticket/12816#section-pr) * Loading… Oldest first Newest first Threaded Show comments Show property changes Show only commits/attachments ##### [Change History (31)](https://core.trac.wordpress.org/ticket/12816#no2) ##### [#1](https://core.trac.wordpress.org/ticket/12816#comment:1) [@nacin](https://profiles.wordpress.org/nacin) Lead Developer [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-02T15%3A32%3A14Z&precision=second) ago For what it's worth, it's been in WP for two years now, since 2.6. I think the only complaints I've seen are related to the obfuscation of the code, not its existence. ##### [#2](https://core.trac.wordpress.org/ticket/12816#comment:2) [@sivel](https://profiles.wordpress.org/sivel) [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-02T15%3A57%3A11Z&precision=second) ago * **Milestone** *Unassigned* deleted * **Resolution** set to *wontfix* * **Status** changed from *new* to *closed* I honestly see no harm in this. In addition the message does actually explain that a "Self-comparison detected", so I, as well as several others who discussed this, feel that your proposed idea is already implemented. Closing as wontfix. "Follow the white rabbit." ##### [#3](https://core.trac.wordpress.org/ticket/12816#comment:3) [@thomasq](https://profiles.wordpress.org/thomasq) [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-02T16%3A10%3A11Z&precision=second) ago Sivel, the harm is that "Self-comparison detected" is lost in the middle of a bunch of nonsensical messages, and completely obscure to users. Let me stress that this is not just a theroetical concern mentioned out of principle considerations. I am administering a Wordpress site whose contributors are not geeks, and one of our editors wrote me to inquire about this behaviour he didn't understand at all. The fact is, even seeing the message, he completely failed to realize that he was comparing a revision with itself, which is an easy mistake to make. I would also like to stress that the code being obfuscated made it much more complicated to me to investigate this issue and find out what it was all about, which is more than a bit frustrating. Others here also remarked that this made Wordpress look amateurish and unprofessional, which is a pity. ##### [#4](https://core.trac.wordpress.org/ticket/12816#comment:4) [@filosofo](https://profiles.wordpress.org/filosofo) [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-02T16%3A32%3A57Z&precision=second) ago How about adding a filter that makes this easy to disable via plugin and commenting in the relevant file? It does have the air of a site attack to it: `wp-admin/js/revisions-js.php` looks just like files that have been compromised. Also, the obfuscated JS violates the GPL 2: ``` The source code for a work means the preferred form of the work for making modifications to it. ``` ([GPL 2](http://www.gnu.org/licenses/old-licenses/gpl-2.0.html)) However, since this was put in with great effort (to the extent of stopping Trac notifications) by Matt himself, and because there's been little opposition to it, any realistic solution has to accept that it's not going to be removed. ##### [@filosofo](https://profiles.wordpress.org/filosofo) [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-02T16%3A46%3A55Z&precision=second) ago * **Attachment** [*easter-egg-revisions-filter.12816.2.diff*](https://core.trac.wordpress.org/attachment/ticket/12816/easter-egg-revisions-filter.12816.2.diff)[​](https://core.trac.wordpress.org/raw-attachment/ticket/12816/easter-egg-revisions-filter.12816.2.diff) added ##### [#5](https://core.trac.wordpress.org/ticket/12816#comment:5) [@matt](https://profiles.wordpress.org/matt) Project Lead [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-02T16%3A56%3A02Z&precision=second) ago Gotta have a little soul. ##### [#6](https://core.trac.wordpress.org/ticket/12816#comment:6) [@markmcwilliams](https://profiles.wordpress.org/markmcwilliams) [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-02T17%3A15%3A10Z&precision=second) ago I have yet to actually do this myself, and it's been built in for that long, I must go do that right now before I forget again! :P ##### [#7](https://core.trac.wordpress.org/ticket/12816#comment:7) [@Lletnek](https://profiles.wordpress.org/lletnek) [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-14T19%3A57%3A08Z&precision=second) ago I realise this is closed now and I'm probably just repeating what others are saying but this is confusing, it's not professional and could be very confusing and could potentially lose people (including myself) clients for such a trivial little easter egg which could and should be easily removed. How on earth do you explain this away when a client asks you what it is without just stuttering and saying uhhh I can't do anything about it. I think the reason people probably haven't spoken up about it is because they simply haven't found it or don't use wordpress in their jobs, where it could potentially cause some real issues. ##### [#8](https://core.trac.wordpress.org/ticket/12816#comment:8) [@strider72](https://profiles.wordpress.org/strider72) [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-15T21%3A20%3A53Z&precision=second) ago Even as major a program as Microsoft Excel has had Easter Eggs, so that in of itself isn't unprecedented; but the Excel egg was very well hidden, while this is one that can be readily stumbled upon by an average user. I would have to say: 1) Make it less obscure/bizarre OR 2) Hide it better OR 3) get rid of it OR 4) un-obfuscate the code **and comment it** so people can figure out what the heck is going on. Personally I go with [#4](https://core.trac.wordpress.org/ticket/4). IT was a good gag, but now the "the in crowd" is in on the joke, it can be slightly less hidden.... ##### [#9](https://core.trac.wordpress.org/ticket/12816#comment:9) [@nacin](https://profiles.wordpress.org/nacin) Lead Developer [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-15T21%3A24%3A10Z&precision=second) ago FWIW, I agree with un-obfuscating it. ##### [#10](https://core.trac.wordpress.org/ticket/12816#comment:10) [@dd32](https://profiles.wordpress.org/dd32) Lead Developer [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-17T02%3A55%3A47Z&precision=second) ago same here, I'm +1 for adding it in as revisions-egg.js + revisions-egg.dev.js (obfuscated).. as well as adding it via wp\_enqueue\_script().. ##### [#11](https://core.trac.wordpress.org/ticket/12816#comment:11) [@dd32](https://profiles.wordpress.org/dd32) Lead Developer [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-17T03%3A44%3A59Z&precision=second) ago > same here, I'm +1 for adding it in as revisions-egg.js + revisions-egg.dev.js (obfuscated).. as well as adding it via wp\_enqueue\_script().. > > > Of course, I meant, un-obfuscated. ##### [#12](https://core.trac.wordpress.org/ticket/12816#comment:12) [@Lletnek](https://profiles.wordpress.org/lletnek) [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-17T22%3A02%3A15Z&precision=second) ago And I say again how about just removing it, it serves no purpose and just pisses me off... there's absolutely no reason for it, it's unprofessional and easily makes people look bad, childish and immature by leaving it in... Please remove it!!!! ##### [#13](https://core.trac.wordpress.org/ticket/12816#comment:13) [@xenlab](https://profiles.wordpress.org/xenlab) [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-17T22%3A15%3A51Z&precision=second) ago Same could be said about your comment, Llentek. ##### [#14](https://core.trac.wordpress.org/ticket/12816#comment:14) [@nacin](https://profiles.wordpress.org/nacin) Lead Developer [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-17T22%3A21%3A58Z&precision=second) ago It's not being removed. The unprofessional aspect is easily discounted by the fact that programs include or have included Easter Eggs. Take Mozilla for example. Are you using Firefox 3.6.x? Type in about:mozilla or about:robots into your address bar. I support un-obfuscation, and I will do it if I get around to either finding the original source or reverse engineering it myself. In the process, we might as well enqueue it so it can be dequeued. ##### [#15](https://core.trac.wordpress.org/ticket/12816#comment:15) [@greenshady](https://profiles.wordpress.org/greenshady) [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-17T22%3A31%3A53Z&precision=second) ago Keep it, please. The discussion on whether it should stay should be over. +1 on un-obfuscating it and using `wp_enqueue_script()`. ##### [#16](https://core.trac.wordpress.org/ticket/12816#comment:16) [@Frumph](https://profiles.wordpress.org/frumph) [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-17T22%3A36%3A13Z&precision=second) ago Easter eggs can be put in a plugin as wordpress tricks, they don't need to be in the core. ##### [#17](https://core.trac.wordpress.org/ticket/12816#comment:17) [@johnjamesjacoby](https://profiles.wordpress.org/johnjamesjacoby) Core Committer [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-17T22%3A44%3A38Z&precision=second) ago Add a hook on it, so that a plugin can take it out (if there isn't one already.) Win + Win ##### [#18](https://core.trac.wordpress.org/ticket/12816#comment:18) [@matt](https://profiles.wordpress.org/matt) Project Lead [14 years](https://core.trac.wordpress.org/timeline?from=2010-04-18T12%3A37%3A42Z&precision=second) ago This ticket is a parody of every default argument people make in WordPress development. ##### [#19](https://core.trac.wordpress.org/ticket/12816#comment:19) [@biziclop](https://profiles.wordpress.org/biziclop) [14 years](https://core.trac.wordpress.org/timeline?from=2010-09-22T10%3A49%3A54Z&precision=second) ago * **Version** set to *3.0.1* While I generally like easter eggs, it isn't really funny, when the ftp server explicitly says it has a virus in it, and refuses to upload the file (unknown ftp server type/virus scanner): /wordpress/wordpress/wp-admin/js/revisions-js.php STOR revisions-js.php 150 Opening BINARY mode data connection for revisions-js.php 550 Virus Detected and Removed: PUA.Script.Packed-1 /wordpress/wordpress/wp-includes/js/tinymce/plugins/paste/js/pasteword.js STOR pasteword.js 150 Opening BINARY mode data connection for pasteword.js 550 Virus Detected and Removed: PUA.HTML.Infected.WebPage-1 ##### [#20](https://core.trac.wordpress.org/ticket/12816#comment:20) [@dd32](https://profiles.wordpress.org/dd32) Lead Developer [14 years](https://core.trac.wordpress.org/timeline?from=2010-09-22T11%3A19%3A36Z&precision=second) ago * **Version** *3.0.1* deleted > when the ftp server explicitly says it has a virus in it, and refuses to upload the file (unknown ftp server type/virus scanner): > > > Unfortunately False Positives are going to happen occasionally. Its strange that it detects [this](http://core.trac.wordpress.org/browser/trunk/wp-includes/js/tinymce/plugins/paste/js/pasteword.js) sane file (pasteword.js) as being infected as well.. But ultimately, thats not grounds for a change here.. rather, Get your host to update their virus scanner's signatures. ##### [#21](https://core.trac.wordpress.org/ticket/12816#comment:21) [@ericmann](https://profiles.wordpress.org/ericmann) [14 years](https://core.trac.wordpress.org/timeline?from=2010-10-22T14%3A48%3A30Z&precision=second) ago * **Resolution** *wontfix* deleted * **Status** changed from *closed* to *reopened* I'm a big fan of the easter egg, and most of my clients find it hilarious. But there will always be one or two "special" cases that I have to protect while helping them launch their sites. Last night, one of them stumbled upon this easter egg, thought their site had been hacked, and freaked out. After several panicked emails and a couple of "holy crap my site's been deleted!" voicemail messages I finally got them to calm down, explained what happened, and helped them learn how to use post revisions properly. I'd never propose removing a feature from core that I enjoy. However, if there was a hook that allowed me to turn it off (either the filter in the attached patch or by using `wp_enqueue_script()`) then I'd be able to silently remove the feature for these "special" clients and avoid the frantic "what happened" and "should I still be using WordPress" conversations that result. I see the arguments about un-obfuscating the code or removing the feature are moot. But I would like a way to disable the feature without having to hack core to do it. ##### [#22](https://core.trac.wordpress.org/ticket/12816#comment:22) [@anonymized\_6443559](https://profiles.wordpress.org/anonymized_6443559) [14 years](https://core.trac.wordpress.org/timeline?from=2010-10-23T03%3A29%3A47Z&precision=second) ago For those who really don't like it couldn't you add some javascript to disable the second radio button for a revision when the other is selected therefore ensuring that a revision cannot be compared to itself, short of someone manipulating the URL directly. ##### [#23](https://core.trac.wordpress.org/ticket/12816#comment:23) [@filosofo](https://profiles.wordpress.org/filosofo) [14 years](https://core.trac.wordpress.org/timeline?from=2010-10-30T18%3A56%3A15Z&precision=second) ago Related: [#15262](https://core.trac.wordpress.org/ticket/15262) ##### [#24](https://core.trac.wordpress.org/ticket/12816#comment:24) [@nacin](https://profiles.wordpress.org/nacin) Lead Developer [14 years](https://core.trac.wordpress.org/timeline?from=2010-11-13T01%3A51%3A02Z&precision=second) ago * **Milestone** set to *Future Release* ##### [#25](https://core.trac.wordpress.org/ticket/12816#comment:25) [@ianatkins](https://profiles.wordpress.org/ianatkins) [14 years](https://core.trac.wordpress.org/timeline?from=2011-02-07T22%3A22%3A46Z&precision=second) ago I think a hook is the solution. Let those that want to hang onto something for old times sake keep it, let those of us who don't want our non-tech savy users screwing when they see the message, disable it. I think the issue I have with this is that most easter eggs are some obscure combination of key presses, or a hidden button etc. They are hidden, its their nature; this 'easter egg' is accessed by function, which only adds to the confusion. The context gives the message authority. ##### [#26](https://core.trac.wordpress.org/ticket/12816#comment:26) [@strider72](https://profiles.wordpress.org/strider72) [13 years](https://core.trac.wordpress.org/timeline?from=2011-04-06T05%3A06%3A30Z&precision=second) ago I know there is a comment added to revisions-js.php, but is there any way to just disable the easter egg? (short of removing or modifying the core file?) Also, comment notwithstanding, it's still pretty much a "you can't find it unless you know where it is" situation. ##### [#27](https://core.trac.wordpress.org/ticket/12816#comment:27) [@RavanH](https://profiles.wordpress.org/ravanh) [13 years](https://core.trac.wordpress.org/timeline?from=2011-04-14T08%3A35%3A11Z&precision=second) ago I suggest removing it at least for sub-sites in a multi-site network setup where it is VERY likely to cause panic among less nerdy clients :) In the mean time, both the winner and runner-up of Eric Mann's contest on <http://wordpress.stackexchange.com/questions/3253/coding-challenge-javascript-easter-egg/> are pretty easy work-arounds when thrown in /mu-plugins/ on multi-site or in /plugins/ + activated on a regular setup. ##### [#28](https://core.trac.wordpress.org/ticket/12816#comment:28) [@sussane](https://profiles.wordpress.org/sussane) [13 years](https://core.trac.wordpress.org/timeline?from=2011-04-24T17%3A36%3A55Z&precision=second) ago \*spam removed\* Last edited [13 years ago](https://core.trac.wordpress.org/timeline?from=2011-04-24T22%3A25%3A07Z&precision=second) by Otto42 ([previous](https://core.trac.wordpress.org/ticket/12816?cversion=1&cnum_hist=28#comment:28)) ([diff](https://core.trac.wordpress.org/ticket/12816?action=comment-diff&cnum=28&version=2)) ##### [#29](https://core.trac.wordpress.org/ticket/12816#comment:29) follow-up: [↓ 30](https://core.trac.wordpress.org/ticket/12816#comment:30) [@jane](https://profiles.wordpress.org/jane) [13 years](https://core.trac.wordpress.org/timeline?from=2011-12-19T01%3A50%3A45Z&precision=second) ago * **Milestone** *Future Release* deleted * **Resolution** set to *wontfix* * **Status** changed from *reopened* to *closed* A link to address some of this was added in [#15262](https://core.trac.wordpress.org/ticket/15262). We're not taking the easter egg out (soul, etc). ##### [#30](https://core.trac.wordpress.org/ticket/12816#comment:30) in reply to: [↑ 29](https://core.trac.wordpress.org/ticket/12816#comment:29) [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein) Core Committer [11 years](https://core.trac.wordpress.org/timeline?from=2013-07-28T20%3A31%3A36Z&precision=second) ago Replying to [jane](https://core.trac.wordpress.org/ticket/12816#comment:29): > A link to address some of this was added in [#15262](https://core.trac.wordpress.org/ticket/15262). We're not taking the easter egg out (soul, etc). > > > its finally time to take out the easter egg (see [#24852](https://core.trac.wordpress.org/ticket/24852)) - you can't reach it now that revisions has been updated; for those who miss it, i'm working on a plugin to re-enable it. **Note:** See [TracTickets](https://core.trac.wordpress.org/wiki/TracTickets) for help on using tickets., Easter Egg Is Confusing, wordpress.org, 01j8favjzvb5hhent2z4sakzx7.