Alicornutopia

Thank you, time traveling tech support!

And Alicorn for voicing an issue I was frustrated with and Ezra for pointing out the fix.

I tried searching for a thread. In the search results, I expected the continuities to be links, but they weren't.

Search results also don't say who the authors of a thread are iirc? It's weird.

Search results need to be generally overhauled and thus are not particularly nice-looking atm.

<33333 okay

Speaking of searching and continuities: If you view a character or template page, you can see the posts they appear in. It would be nice if those posts were grouped by continuity. This would allow the use cases "read continuities containing this template" or "read the portions of a continuity containing this template, but in internal order".

(Well, the character one says 'Recent Threads' which implies it is an incomplete list, but I see no reason why it shouldn't also be as complete as a template page's list?)

After I edit a gallery and save it there seems to be no good way to return to the actual gallery's page

It used to do that automatically, I think, and so at that time there was no reason to have a link. I think it would be good to link from the edit gallery page to the... don't edit gallery page... anyway, but it's particularly important now that there isn't an automatic redirect on save.

Reading room of requirement I suddenly want the diff feature a lot more, but that doesn’t actually make it any more tractable.

If you don’t want to provide even a toggle of Kappa’s moiety colors thing, could you at least provide data-moiety-color on infoboxes, and maybe author links, so we can attempt to implement it as a user style? I’m not sure we can succeed unless CSS has a way of extracting the luminosity of a color, though.

Or is the lack of toggle less an issue of philosophical objection and more one of low priority (even if the low priority is caused by philosophical objection), because I would be more than happy to learn Haml and make a pull request.

Either way, Kappa, did you tweak the design at all after the linked post?

At this point I've done literally nothing for a week but review/merge Throne's pull requests and bang my head on our memory usage. It doubled when we upgraded Ruby and I've been fighting a losing battle trying to keep it under control. We used to run 100-200MB per instance, and we had two instances running because the box tops out at 512MB; we had to drop to one instance pretty much as soon as we upgraded and I've been struggling to keep the single instance from maxing out the box. I can't upgrade the memory on a single box easily, it bumps the price from $7 to $50 a month, and we shouldn't be using this much memory anyway I am losing my damn mind. Today's changes might get us from 470MB to 360MB? But it has to run for a few hours before I can tell for sure? Ughhhhhhhhhh.