The pageview pixel code expects various things (the base URL, the secret token, etc.) to be configured. Other places (like base.html) always check if `g.tracker_url` is valid before generating the pageview pixel. This was broken in 1f6a9aa when `js_config()` started calling `get_pageview_pixel_url()` indiscriminately. Ouch for poor open source and dev installs.
mobile-web keeps cropping up with a bug that puts private IPs into the account history for users. Best not to worry them with such things and hide it from their activity page.
differences. This is partially a guess, but is also based on a 15% stat for difference between in memory size and pickled size.
Previously was returning None, but when looking up a list of ids it should return an empty list or empty dict.
The opacity rule "stacked" onto child messages and comments resulting in whiter and whiter child elements.
The translations are currently being done in the context of the moderator that creates the ban, not the recipient of the message. So if the moderator has their language set to something different than the banned user, the message will be in the wrong language for the recipient.