1. 1

    I’m not sure it’s working right. I went into the elevator and saw a mess of black lines that I soon recognized as dozens of character images overlapping. Then I clicked on some of the speech options, and the one I clicked on was swapped for a new one, but that’s it. I’m not sure if there’s supposed to be somewhere on the screen where other people’s messages would appear, but if so, none of these dozens of people seem to be saying anything.

    What I’m seeing on Firefox 75 on macOS: screenshot of page

    Given the interface I see, I would expect that when I click a button, a speech bubble with the message I clicked would animate in over my character’s head. And I expect that the other characters I see are people using the site right now, and I would be seeing speech bubbles appear over their heads with what they are saying.

    1. 2

      I see something similar in Chrome. Maybe the site is overloaded. Looking at the console, react devtools seems to be breaking down too:

      Uncaught RangeError: Maximum call stack size exceeded

      at He (react_devtools_backend.js:6)

      1. 1

        Seems like it was overloaded at some point and didn’t recover nicely! Thanks for pointing it out. Should be working a bit better now.

    1. 1

      Loved the insight into horizontal bars being easier on the eye trajectory. But reading this had me triple-take:

      because vertical space is usually less constrained than horizontal space.

      The animation clarifies the distinction. Phones are most likely in portrait mode, where horizontal space is constrained. Desktops are most likely in landscape where vertical space is constrained. So Penny charts are optimized for consumption on a phone.

      1. 1

        I don’t know if it’s like this in other databases or not, but something that tripped me up multiple times over the years with pg was using “timestamp” as opposed to “timestamp with time zone”. The timezone information gets thrown away instead of converted to UTC so applications need to actively fiddle with it.

        Is it strange that I assumed “timestamp” being “timestamp without time zone” meant that postgres didn’t store timezones because it’s always in UTC and clients would automatically convert back and forth?