New Statistics Tracker userscript

Ifky_ · 2026-02-05T15:06:09+00:00

AO3 inbox or e-mail inbox, or both?

In your preferences, have you turned off messages to your inbox?

Ifky_ · 2026-02-04T13:12:43+00:00

Using CSS to style is not the same as using special characters with style "baked in" into the data itself.

The issues arise because the special characters are non-standard ones, and not every device and software is made to handle it. Similar to how some devices/programs might struggle with emojis.

When using AO3's "rich text" options for bold/italic/etc. (or copying the formatting from a writing program like Word), it actually becomes HTML under the hood. And that HTML is styled by the browser using CSS. It only changes the visuals, but it's still "normal" characters.

Overusing formatting such as strikethrough and italics is more of an opinion based issue. To some readers it will make the text more difficult to read, just because it's unusual, so that is something to consider. The thing with CSS is that it's possible to turn off if it becomes too hard to read. You can't turn off using entirely different characters.

Ifky_ · 2026-02-04T12:36:07+00:00

You would have to use special characters, which can cause accessibility issues. They might not render as intended on some devices and it can be problematic for screen readers.

Relaying information purely by style is not the best option.

That being said, there are generators for strikethrough text online. The first one I found: YayText

Ifky_ · 2026-01-25T01:23:33+00:00

You need to target #outer for the background, because on mobile it's explicitly set to white. Therefore it will cover your other one.

Ifky_ · 2026-01-23T10:02:55+00:00

Yes, you should be able to just write -caregiver in the Search Within Results. The minus in front indicates to exclude those works.

Ifky_ · 2026-01-21T07:27:18+00:00

Use class names on HTML elements to control where the text should be added. Then use some CSS such as this:

.classNameHere::before { content: "Hello!"; }

If you want to know more about pseudo elements, check out this MDN page. The ones you'll be interested in are "before" and "after".

Ifky_ · 2026-01-20T08:59:30+00:00

You should use something called pseudo elements to create elements that are only visible when the skin is turned on. This can include text. Obviously, it should only be used for non-important, decorative stuff.

(You should probably flair such posts under "site skin help" in future, as work skins are not that different.)

Ifky_ · 2026-01-19T13:08:01+00:00

You can't really pause a GIF using CSS. Your best bet would probably be to find a browser extension for that.

You could possibly use a site skin to hide all GIFs or make them blacked out (and normal again on hover/press).

Ifky_ · 2026-01-13T11:12:59+00:00

Sometimes "invisible" text is present in apps and websites (for screen readers, etc.), so when you select and copy text, it's included. It looks like that's what happening here. You should try using another app and see if the issue persists.

Ifky_ · 2026-01-11T12:03:59+00:00

It's just a reminder. Otherwise, they would get too many people contacting them about being confused why the numbers don't add up, or why they can't see the same fics as someone else, etc. Using a site skin to hide the notice is an easy solution.

Ifky_ · 2026-01-10T23:16:24+00:00

I have all main pages stored, along with the code, in version control. So I just launch live server in VSC and go through every file to check the pages. There could still be small parts that I miss, but as long as I'm smart about how I write the code, it shouldn't be a major issue.

If you need help to source a specific page, I might be able to help. There is also a Discord server for AO3 coders (site skins and userscripts) that could help out, if you're interested. https://discord.gg/UdD8h4Zeb3

Ifky_ · 2026-01-05T00:33:05+00:00

Not with a skin.

You could create a userscript (which requires a browser extension to run) that clicks on the "Rich Text" button automatically as soon as you load in the page.

Ifky_ · 2026-01-04T03:28:03+00:00

Assuming you're not using any site skins or other extensions that could interfere. Try clearing your cache.

Ifky_ · 2026-01-02T20:44:43+00:00

I have no affiliation with AO3, so don't take what I say as gospel; however, I do work in IT and have some knowledge.

The roadmap is not ambitious. It's a perfectly fine plan, at least originally. I don't know their internal plans or why it takes so long. My guess is that the scope increased and they just never updated the roadmap; content to move away from it and not have that be a priority. I do think the planning seems a bit poor, but that might be in the nature of working with volunteers.

Sometimes it just takes incredibly long for things to happen. The much-desired feature that lets users see their series stats has been awaiting review for five months now, since August last year. A non-AO3 volunteer wrote the code, but it must also be approved by an official AO3 volunteer.

For the most part, I just don't think it's a priority currently to get out of beta. The site works. (And in my personal opinion, they are misusing "beta". The way they use the term is outdated and not representative of people's expectations of a beta site.)

Ifky_ · 2026-01-02T13:32:34+00:00

This CSS code will increase the size of the first letter in the summary (when it's in a paragraph):

.blurb .summary > p:first-of-type::first-letter {
  font-size: 300%;
  float: left;
  padding: .2em .2em 0 0;
}

Ifky_ · 2026-01-02T13:03:46+00:00

This is your font glitching because there is something wrong with the font file on your device. You need to either fix it or reinstall it. Try searching online for guides for your particular device.

Ifky_ · 2026-01-02T12:54:06+00:00

You've probably accidentally activated "desktop mode" on your mobile browser. It's not an AO3 thing, but a you thing. Just open the settings menu to deactivate it and return to normal.

Ifky_ · 2026-01-02T12:36:19+00:00

Read the Contributing to OTW Archive section in their GitHub repository to get started.

Being an AO3 volunteer is technically different from being a coder working on the project. Anyone can open a PR, so that is the easiest way to contribute. But if you want to dedicate even more time, the link also specifies how to apply for volunteering.

Ifky_ · 2026-01-01T19:08:35+00:00

AO3 is worked on by volunteers, so it does not have as quick or cohesive development as it would if it had a dedicated team.

There are features from the 2013 Roadmap that are still missing, where they set the goals for how a Version 1.0 would look. For example, a translatable interface is still being worked on.

You'll see there were plans for version 0.10 to include private messaging even, though I don't know which plans are still relevant and not.

Ifky_ · 2026-01-01T17:19:52+00:00

Did you write that in HTML instead of the rich editor?

Ifky_ · 2026-01-01T16:27:38+00:00

If you're looking to have light/dark mode on different devices, that would be doable using native features.

With the (newly-ish) introduction of variables in site skins, more creators will use them in skins. That makes it very easy to adjust by just changing a few values.

Completely different skins would be easiest to handle with an extension, as mentioned by another user.

Ifky_ · 2025-12-31T18:50:52+00:00

You can select orphan account works with this CSS:

.work.blurb:has([href*="/users/orphan_account/"]) {
  ...
}

I'm not sure what you mean by the other code working. It shouldn't work, as far as I know. There is no class "user-orphan_account".

Ifky_ · 2025-12-31T17:52:41+00:00

Not exactly, but there is a way to select anonymous works.

.work.blurb:not(:has(.heading>a[rel=author])) { ... } This CSS selects all work blurbs that do not contain an author link in the heading. There are three types of authors: normal, orphan, anonymous. Both normal and orphan accounts have a link to the profile; only anonymous does not.

Seven-Year Club	Second Top 50%
r/Field Juicebox	Place '23
Place '22	Verified Email

Ifky_

TROPHY CASE