jamesrom / jamesrom.github.io Goto Github PK

Seems to timeout after some time and only returns a 500 and no data is shown :(

3e6d586 changed // to http:// which causes unsafe content warnings when https://jamesrom.github.io/ is loaded over https. The loading over https happens automatically for users of https anywhere.

I think a trendline would be pretty nice (and easy enough to achieve with d3), especially since the actual lines start to be too thin if the site has run for too long.

Right now its at -6,633ms...6 seconds of time difference. But what is it a difference of? Is that coming from the websocket data from reddit? Like, everyone is behind -6.6 seconds? Or just uniquely this app? If it's the app, what causes that?

I noticed that some of the bars appear to be incorrectly flaired:

My stats at the time:

It's impossible to view the hover info when the button reaches 1 second, as it did earlier today. It disappears behind the browser UI as seen in the image.

In other words, you're not gracefully handling the case of not having enough horizontal pixels to show every reset. So, resets falling on just the wrong subpixel positions aren't shown at all until they move.

For me, it only took leaving it open for about two hours for this to start happening

Scrollbar seems like the easy answer.

Currently a info popup on the far left or far right can be too wide and increase the width of the page. Here is an example on the right side overextending:

The page can be scrolled rightward to see the full popup, but far left popups are just cutoff. A workaround for users is to zoom in so that the center of the click bar is farther from the edge of the page.

This project keeps getting better.

I would love to see a better explanation of what all the terms mean, especially the new ones on the hover popup.

What does "Clicks" mean and how can there be more than one person clicking at a specific bar? I thought only one person could get a specific number and then it reset.

Also explain what "Resets" means and how it relates to clicks.

Thank you.

It would be a nice idea so when you hover over the column it will have the time that it reached.

as when you leave it running for a while it is quite hard to tell at what time it reset.

There should be a button to reconnect the websocket forcibly, so you don't lose history but just have a gap of "no data" [e.g. computer went to sleep]

Hi. I couldn't quite track down the piece of code that needs changing, do not have loads of time, but in general, I noticed that when I have the tab open, it is running at around 70% CPU usage. This indicates busy waiting (redrawing with a while loop somewhere?).

It is probably a good idea to leverage setTimeout and redraw, say, 60 or 120 times a second (the refresh rate of standard monitors). An alternative could be using CSS transitions, but that might be hard to get right such that it looks smoothly.

Heavy CPU usage isn't a huge problem per se, but I work on dual-screen, sometimes doing CPU intensive work, which makes having the page open slow my computer down a bit. And if you are running on a battery, having the CPU usage so high drains it quite heavily.

The reason for this is that the highest bar (least time remaining on timer) would be closest to the current bar, which would give you a sense of how "good" the current run is compared to the slope to the left of it.

This feels like something quick (button which toggles a boolean which controls whether or not to sort the data points) but I'm not familiar enough with the technologies involved to whip it together, unfortunately.

Hello,

It seems that there are a few empty columns. See from the screenshot: http://i.imgur.com/qVJ4wY5.png

From the left it's your application, from the right it's mine. I'm comparing both and it seems that you have a few empty spots. It seems very random.

Hey,

The monitoring doesn't works, I got an error 500 :
WebSocket connection to 'wss://wss.redditmedia.com/thebutton?h=0ac3a25d899813fdf6ce06b0e80b7ef56a850bce&e=1428493002' failed: Error during WebSocket handshake: Unexpected response code: 500