What known quirks does PixivFE have?

Updated

PixivFE's documentation lists a "Known quirks" page, which means the project openly tracks behaviors that differ from what you might expect from pixiv's official front-end. The documentation does not reproduce the contents of that page in the material available here, so the specific quirks themselves are not enumerated. What can be said with confidence is that PixivFE is an open-source, self-hostable alternative front-end for pixiv, and that its maintainers treat "known quirks" as a distinct documentation topic alongside hosting, configuration, authentication, and development.

Why a "Known quirks" page exists

An alternative front-end sits between you and pixiv's own services. That position creates predictable categories of difference:

  • Rendering and layout. PixivFE is its own front-end, not a skin over pixiv, so pages are built by the project rather than by pixiv.
  • Data access. It talks to the pixiv API, and the docs include a separate "Authentication for the pixiv API" topic — a sign that access to pixiv data involves its own setup rather than being fully transparent.
  • Images. The docs list "Public image proxies" and "Hosting an image proxy server" as separate topics, so image delivery can route through a proxy rather than directly from pixiv.
  • Caching. "Caching" appears as a feature topic, so what you see may be served from a cache rather than fetched live.

Each of these is a plausible source of behavior that differs from pixiv's official front-end, and the quirks page is where the project records the concrete cases.

What to check before assuming something is broken

If you encounter behavior that seems wrong, the documentation structure suggests an order of checks:

  1. Read the Known quirks page first. It exists precisely to distinguish intended-but-unusual behavior from actual bugs.
  2. Check whether the instance uses an image proxy. If images fail or load differently, the proxy configuration is the relevant variable, not the front-end code.
  3. Consider caching. A stale or unexpected view may be a cache effect rather than a data problem.
  4. Check API authentication. If content is missing or limited, the pixiv API authentication setup for that instance is a likely factor.

Limits of this answer

The available documentation excerpt names the "Known quirks" page but does not include its list. Anyone who needs the actual quirks should read that page directly on the PixivFE documentation site, and should treat the categories above as the areas where quirks are most likely to appear rather than as a substitute for the list itself.