AniList Wrapped 2024

Welcome here friend! Are you here to take a look at your AniList Wrapped 2024 details? Look no further!

Get insight into how much media you've consumed, your top animanga, your rank amongst your fellow AniListers, and much more! The Kusogaki Events team proudly presents the Unofficial AniList Wrapped for 2024!

Note: Unlike the first iteration of AniList Wrapped, there have been some changes that you should be aware of:

• You are now required to sign-in to your AniList account and authorize Kusogaki access
• We will not deliver your wrap through a message. Your wrap will be posted on YOUR AniList account through a status post that is created on your behalf.

Login through

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. Reading general user information and preferences (such as username, avatar, and preferred media language)
2. Reading the list of media activities performed (such as watching, reading or dropping a media)
3. Read the list of non-private media under their respective lists (used to correlate 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.

Based on the first iteration of AniList Wrapped we have received a ton of valuable feedback (thank you!), which include:

• Excess delays
• Incorrect / missing stats
• Thread comments being ignored
• Wraps not delivered

Excess delays

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.

Incorrect / missing stats

There are a ton of things that contribute to this, so this is no silver bullet that pretends to fix everything. In fact this is probably the point that is less addressed with this change individually. However this will definitely help with edge cases in which collecting statistics takes too much time causing the task to be aborted until a later time.

Thread comments being ignored

This is probably one of the more compelling reasons as to why 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.

Wraps not delivered

Fortunately this was not a very common issue, but even so, this is aggravated by all the above issues. The one final issue would be with users that have private / read-only profiels that disallow Kusogaki from dropping the way on their profile. This issue in particular could be resolved by working around such limitations.