Yep

[branchandroot]

The only thing I really have to say about AO3's latest contretemps is: I told you so~

When a platform is so fucked up that the only way to make it run is to take out the navigation, then it's time to think real hard about who's been driving development.

Comments

[mitsuhachi]

Woooooooow. Just. Wow.

[tavella]

I did some testing a few weeks ago, and as of then, they were not caching works listings, or if there was any caching it was a matter of seconds. Every single time I clicked on a page in my "1000 works" list, it was doing a new db search. And every single time, it was regenerating the tags list for the filter. Every time I changed sorting. Every page. Every time I used the filter. Crushing the db again and again. It was jawdropping.

(Dropping in from link-hopping)

[jackandahat]

Have used that twice to explain that while X and Y had the same name, they were from totally different fandoms and ask if there was any way to fix that.

The first time, I eventually got a nice reply saying "Oops, we'll sort that" and the names became Name(Fandom One) and Name(Fandom Two).

The second time I got a snotty reply about how they could only go on what names were there, and nothing could be done about it. When I grumbled about this on Twitter, I got a long lecture from a total stranger (friend of a friend) about how hard it was to be a tag-wrangler and how I had no right to complain because I wasn't even a user. (I'm not registered. And given it takes six months to sign up...)

So, the option exists, but...