Skip to content

Update Shikimori domain from shikimori.one to shikimori.io#837

Open
noctuum wants to merge 1 commit intoz411:masterfrom
noctuum:fix/shikimori-domain
Open

Update Shikimori domain from shikimori.one to shikimori.io#837
noctuum wants to merge 1 commit intoz411:masterfrom
noctuum:fix/shikimori-domain

Conversation

@noctuum
Copy link
Copy Markdown
Contributor

@noctuum noctuum commented Mar 1, 2026

Summary

Shikimori has migrated to shikimori.io as the canonical domain. The old domain (shikimori.one) currently redirects, but API/OAuth URLs and docs should point to the new one.

  • Update url, auth_url, api_url in libshikimori.py
  • Update OAuth authorize URL in utils.py
  • Update link in README.md

Fixes #835

Shikimori has migrated to shikimori.io as the canonical domain.
Update API URLs, OAuth URLs, and documentation links accordingly.

Fixes z411#835
Copy link
Copy Markdown
Collaborator

@FichteFoll FichteFoll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at shikimori.one and .io, they are mostly identical and there is no redirect either, but the forum links on .one point to .io while links on the .io page always go to .io, so I'm inclined to believe that the domain change is authentic despite not looking for an official announcement (I do not speak Russian).

@noctuum
Copy link
Copy Markdown
Contributor Author

noctuum commented Mar 1, 2026

Looking at shikimori.one and .io, they are mostly identical and there is no redirect either, but the forum links on .one point to .io while links on the .io page always go to .io, so I'm inclined to believe that the domain change is authentic despite not looking for an official announcement (I do not speak Russian).

I wasn't able to find an official announcement, but there is a clear reason for that (see below). Here's what I found in chronological order:

Timeline
2023 - Shikimori's .one and .org domains were hijacked via a social engineering attack on the domain registrar (inwx). The site temporarily moved to shikimori.me. Later, RKN (Roskomnadzor - Russian federal media regulator) blocked .me for LGBT-related content. The site then returned to shikimori.one after recovering the domain.

January 22, 2026 - RKN added shikimori.one to its block registry.

January 27, 2026 - The block took effect. Shikimori admin posted on the forum acknowledging the block without specifying the reason. The Russian State Duma later stated the site was blocked for "systematically evading prior blocks by changing domains and creating mirrors."

Late January 2026 onwards - shikimori.io appears as the new primary domain. No official announcement was made - which makes sense: publicly announcing the new domain would make it trivial for RKN to block it immediately, defeating the purpose of the migration.

Technical evidence that .io is the canonical domain

  1. HTML source of shikimori.one itself references .io more than .one - curl -s https://shikimori.one | grep -oP 'shikimori\.\w+' | sort | uniq -c shows 201 references to shikimori.io vs 141 to shikimori.one
  2. shikimori.io exclusively references itself - the same check shows 337 references to .io and zero to .one
  3. OpenSearch metadata on .one points to .io: <link href="/search.xml" rel="search" title="shikimori.io" ...>
  4. Internal forum links on .one point to .io (as @FichteFoll noted in the review)
  5. No HTTP-level redirect exists - .one returns HTTP 200 through DDoS-Guard CDN, so the migration is happening at the application/content level, not via HTTP 301/302

Sources
⚠️ Note: most sources below are in Russian.
РКН заблокировал Shikimori - Shikimori forum announcement (Jan 27, 2026)
Госдума объяснила блокировку - RIA Novosti (Jan 28, 2026)
Роскомнадзор ограничил доступ - TASS
За что заблокировали Shikimori - Fontanka.ru (Jan 27, 2026)
Domain hack & migration history - Shikimori forum

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update Shikimori domain from shikimori.one to shikimori.io

2 participants