Welcome!

What's this site?

This website originally started as a new, automatic way to process and store the requests & reservations users want to make. It was born due to the fact that in the past, the handling of comments under journals was done manually. Because of this, there had to be people who checked those comments every once in a while, evaluated them, then updated the journal accordingly. This was a time consuming task, and since the group's staff consists of busy people expecting them to constantly monitor new incoming comments is unrealistic. The initial goal of this website was to provide an easy-to-use interface where new entries can be submitted and added to a list (just like the journals) automatically, eliminating this monotonous task.

After some time, the idea of moving the old PNG color guide into an easier to use format was brought up and met with positive responses. Since then, the site also houses the vector club's official color guide, with freshly picked colors from recent episodes (and cute little pictures to go with a couple popular characters) among other information such as recommended cutie mark vectors and tag-based search. For easier use in drawing applications individual characters can still be downloaded as PNG files that contain all colors associated with them.

Attributions

Please refer to the project's GitHub page for an up to date list of all used tools & libraries.

Episode synopsis data is provided by The Movie Database API. This product uses the TMDb API but is not endorsed or certified by TMDb.Coding, design & hosting:SeinopSys

What image hosting providers do you support?

As you can probably tell we do not host a large majority of images you can see on episode pages, we just
steal the bandwidth
use the help of already established sites. Here's a full list of all providers we can recognize and that you can use to submit images:

* Using direct links from these providers is not supported due to the ambiguous URL schema shared by both Sta.sh and DeviantArt (both links end with an ID in the same format). Example: the link http://fav.me/dzc2af9 could have a download link that points to http://orig11.deviantart.net/27f5/f/2017/107/3/b/image_by_user-dzc2af9.png. If you use the second link, the site won't accept it. But why?To understand why I, as a developer cannot provide support for this, let's look at an example with a normal link and its corresponding direct link from Sta.sh: https://sta.sh/0z5gg4as67m → http://orig00.deviantart.net/9935/f/2016/089/8/e/another_image_by_user-dxc2f9v.jpg Notice anything different? It's the lack of distinct difference between the two, there's nothing to tell which site the image came from. Hopefully this gives you an idea of why things are the way they are.

What's after the @ sign in the footer?

This website is open source, you can find the code on GitHub. What you're seeing is the commit ID which refers to the most recent version of the code the site is currently operating on. Whenever a new update is deployed, the version number changes automatically. The code on the server mirrors the repository exactly with no hidden alterations.