The other issue is that a big part of ao3 most people don't realize is there is the volunteer tag wranglers. Some of that might be able to be done by an llm that can catch basic misspellings and common ship naming conventions but sometimes ship names refer to really obscure references that can't be reliably sorted that way.

I applied to squidgeworld personally. I'm super bummed because I JUST finished my latest two chapters of my slow burn tentacle porn plus the actual porn part for later down the line because it needs a little more burn to fully satisfy.

The catchy name certainly doesn't hurt either

How does adding federation to something like AO3 interact with the very important property that AO3 has that authors are in control of their space? Can an author moderate the remote / federated comments on their work?

Does fediverse have automatic content propagation across instances? Because from what I have seen, content preservation is not the strongest suit of the fediverse unless it's a major instance, in which case we're just back to rebranded AO3.

Look if you want to run something like that, then go for it, nobody is stopping you. But we've had a bunch of threads like this already and srsly, the software is not an issue. The reason AO3 came into existence in the first place was to create a home for stories and authors that kept getting banned from other sites. It's about the stories and content policy, not the software. Do you think a federated version will allow those stories? Will your own instance allow them?

I'm not into those kinds of stories myself (by far the biggest Harry Potter category there has Harry dating Draco), but the fact that they are allowed contributes to the tolerant atmosphere of the whole site. It was similar with Reddit before it got too corporate, and to some extent even now. Lemmy is ridiculously stuck-up by comparison. I don't understand why people think federation (Lemmy style) is some kind of fairy dust. It operates the wrong way imho: stuff like subscriptions should be entirely on the client side, to get rid of the choke point that exists at every interface between two federated servers.

The name "ourchive" is cute but I think it's too imitative of AO3. So I'd hope for a different name. But, props for cleverness.