AniList Wrapped 2024

Welcome here friend! Are you here to take a look at your AniList Wrapped 2024? Well this is somewhat embarassing but the registration period for AniList Wrapped 2024 is closed and no new submissions are accepted.

Next time do try to be a bit earlier with your intent. Make sure to subscribe to this thread to stay informed when a new event drops!

If you have already applied and would like to check your status, please login below.

Frequently Asked Questions:

How does this work? Is my data safe?

Glad to have you here. We want to be completely transparent with you.

By logging into AniList and authorizing Kusogaki, you are allowing AniList to share a token (think of it as a pass) with us that allows us to perform actions on your behalf. The login credentials that you have used on AniList are never shared with us. You can think of this working quite similarly to how other sites work when providing the option to Login through Facebook / Google - in fact it uses the same authentication system. The only notable difference is that while other systems usually provide scopes, AniList doesn't.

This essentially means that we cannot ask AniList to limit the level of access that we are provided with. As such with a token we could practically do anything that a user could through AniList itself, such as commenting / liking activities and marking media status.

In our case we would be using the authorization for these exclusive purposes:

1. Read general user information and preferences (such as username, avatar, and preferred media language)
2. Read the list of media activities performed (such as watching, reading or dropping a media)
3. Read the list of media you've added under their respective lists and their scores
4. Count the number of messages / likes received by each person - NOT the message content (to calculate biggest fan)
5. Count the number of status posts that you have posted - NOT the post content (to show relative statistic)
6. Post a single status post on your own profile to deliver the wrap

Without a valid token, we would be unable to fulfil one or more of the above - and therefore unable to provide the wrap. The token that AniList provides us with remains valid for about one year. However should you wish you can revoke the token provided to Kusogaki either from AniList itself or by visiting here.

What's taking so long?

First off, are you sure that the event has started in earnest? The AniList Wrapped registration period usually starts between two-weeks to one-month before the wraps start getting delivered. If your position in the queue hasn't moved at all after a couple of hours, either: the event hasn't started yet or something has gone wrong, and we're doing some maintenance.

If your position in the queue is moving along - just slowly - note that AniList imposes some heavy limitations to prevent abuse and keep the systems running stable. Have you ever tried to spam a ton of likes only to be stopped halfway through? That's rate-limiting in action. There are a number of different limits imposed, depending on the action that is being performed. One notable rate-limit is on the number of messages that you can, which stands at three per minute.

On the first iteration of AniList wrapped we have had the honour of serving over 15,000 users! However if we were to exclude all the statistical analysis, and assume that the bot had been doing nothing apart from sending out messages, that amounts to over four days running non-stop to get through the whole load. In addition to this, there are other rate-limits that had to be factored in.

The above coupled with a change of WAF from AniList's end means that the issues have been further exacerbated, with rate-limits being applied from two different ends. Some time in the distant past a few select users were immune to these imposed limits, but later changes - and the WAF addition - completely reverted these exceptions.

We have tried to address this issue with AniList administrators a number of times, but sadly, it has become increasingly clear that there seems to be no interest in having any immunity applied at all - for whatever reason. This severely limits our options, and excluding WAF, the only real option is a workaround that reduces the number of requests that we - as Kusogaki - perform in the first place. Going down this path means that we either use ALT accounts (which is against AniList's terms') or use our team member's individual accounts to split the load.

While this helps in the short term, this is not a scalable or practical solution. That leaves us with a third option: we make use of your own account to compute and publish your statistics. We believe that this is fair since the only time that a user would be impacted is whilst their wrap is being generated. This should be virtually seamless for the vast majority of users, and any rate-limiting impacts are very short-lived.

What's up with my statistics? They don't seem right, or they're missing some data

Your statistics may appear inaccurate due to limitations in how data is tracked and collected. This includes activity tracking issues, merge time settings, and cases where data collection takes too long and needs to be rescheduled. Unfortunately, at this time, there is no single solution that will fix all these issues.

What happened to the AniList Wrapped registration thread?

In short, there isn't one anymore. After the first edition of AniList Wrapped, we have decided to start moving away from AniList threads in favour of opting to the wrap from our website. If you have ever participated in our GTA events or perhaps our first AniList wrap, you would have noticed that the AniList thread happens to break as soon as it gathers some traction. We can barely explain what break implies in this case, but it ranges from anything between missing comments / reordered comments, comment replies losing their associated comment, direct comment links being incorrect, and paging not working correctly.

This is no new issue, in fact it has been an issue for years on end, and there seems to be no imminent intent of AniList addressing this. As such, we will continue evaluating and considering feedback.

Why isn't the website generating the wrap on-the-fly?

That's a good question, and it's something that we have been giving some thought. We could certainly have it perform a large number of the statistics on-the-fly, but, considering the number-crunching and the number of AniList API calls that we make to retrieve and cross-reference information, you will likely be waiting for a while anyway.

For the moment we have decided that the best course of action that is able to deliver results without a major rework would be to have the backend do the calculations at its pace, while also giving us the flexibility to deal with large amounts of data.