User blog:TimmyQuivy

User blog

TimmyQuivy TimmyQuivy 1 June

FandomDesktop: A New Experience Has A New Customization Policy

As we continue transition our platform’s communities onto our new Unified Community Experience (UCX), you are now getting the chance to design and test how your community will look.

For many of you, beyond the basic theme and color pattern of the wiki, there will be other things to test and redesign. Tweaking your wiki’s appearance often goes well beyond the defaults and into the realms of deeper customization.

As we will explain, with the rollout of the UCX, we are today also rolling out an updated Customization Policy - the rules for how and what you can customize in your community. Based on your feedback from the previous version of the Customization Policy, there are a few areas we believe we are able to offer a more open approach. Howe…

Read Full Post
TimmyQuivy TimmyQuivy 4 August 2020

Introducing SOAP: Our Anti-Vandalism & Spam Team Gets a New Name

Hey gang! (I am channeling my best inner MisterWoodhouse because he is on a much deserved vacation)

Today, I’m pleased to announce we’ve reached another milestone in the United Community Platform initiative, a minor technical tweak that has some big and exciting social ramifications. On wikis using the UCP, you will now begin to see some users referred to as members of the SOAP team.

This is just a new, combined name for two groups familiar to our editors. The VSTF (Volunteer Spam Task Force) from Fandom and the GRASP (Gamepedia Rapid Anti-Spam Patrol) from Gamepedia have merged into one team. We decided to give the group a new name, since we didn’t want to favor one platform’s history over the other. All the members of the team came up wit…

Read Full Post
TimmyQuivy TimmyQuivy 7 May 2020

On the Importance of Upgrading MediaWiki

If this is the first you're hearing about the Unified Community Platform project, read this to learn more about the entire scope of the project before commenting.

As Fandom continues to roll out our United Community Platform this year, one reason you have seen us cite for creating this new platform is that it'll allow our entire wiki network to exist together on the same version of MediaWiki. This means, for communities already on the Fandom platform in particular, upgrading to MediaWiki 1.33.

That explanation might make a lot of sense for our oldest, most experienced users, but for many of our users, the term 'MediaWiki' is a mystery. What is MediaWiki and why does Fandom care about it? Doesn’t Fandom have its own unique code? Why does upgr…

Read Full Post
TimmyQuivy TimmyQuivy 12 July 2018

HTTPS Next Steps: URL Changes for International Wikis

In the first half of this year, FANDOM has been steadily rolling out HTTPS to more and more of our network.

HTTPS is a protocol that encrypts data being sent through a webpage, as compared to normal HTTP, which sends data in plaintext. FANDOM has already been encrypting and securely transmitting personal data - such as your login and password details - for many years, but it’s increasingly a web standard to transmit all parts of a website over HTTPS. That’s why we’ve been working to get our entire website HTTPS-compliant.

A few months ago, we finished making logged-in users able to use HTTPS on all single subdomain wikis (i.e.wikis without a language identifier, such as, compared to, first using an…

Read Full Post
TimmyQuivy TimmyQuivy 26 April 2018

Opt-In Now Available for HTTPS on FANDOM

Late last year, we updated the community on our plans to migrate FANDOM to the HTTPS protocol. This is something many of you have wanted to see, just as we have, and a lot more work has been done to help make this happen!

Since our last update, we’ve continued making changes to our codebase to make switching to HTTPS as simple as possible. To kick off the migration, in early February we enabled a preference that allowed FANDOM Staff members to opt-in to having pages served over HTTPS for a number of randomly-chosen communities. After fixing a few bugs and doing some extra future-proofing — making sure images imported through custom JavaScript use the HTTPS protocol, for example — we extended the use of HTTPS to include all communities cover…

Read Full Post

Community content is available under CC-BY-SA unless otherwise noted.