Live data from Hacker News

My ISP has a poor service record. I made a tool to test how shitty it is

iscableoneshitty.com

31–37 of 37 posts

Re: My ISP has a poor service record. I made a tool to test how shitty it is

#31

I worked at a company that made electricity usage monitors. The little boxes would send data to us with energy usage every minute. We could see how often internet went down, based on how many times the boxes sent us "stored" data. We didn't do any analysis on the data, but we did note that the residential internet while good isn't as always on as you think it should be. We were wondering how much of a problem this wa…

The question is, is it that corporate internet is that much better, or that they're just more diligent about making sure that their internet never goes down? In other words: a residential customer is more likely to accidentally unplug their modem, or maybe flip a lightswitch that controls an outlet that the modem is plugged into, or accidentally flip the switch on their surge protector, or turn their modems off at ni…

>or that they're just more diligent about making sure that their internet never goes down?

I think that has something to do with it. Business too have blocks of time (nights) when the internet can go down and nobody is going to call for service. I wasn't involved with the network provisioning but often we were put on the same network as the "guest wifi" as opposed to the business network or the network with the cash registers (for security reasons)

Re: My ISP has a poor service record. I made a tool to test how shitty it is

#32
post #27

Earlier quoted context omitted.

Points are fully responsive. They correspond to the on-screen physical size of the text. (See http://en.wikipedia.org/wiki/Point_%28typography%29 ) If the text doesn't fit on your screen -as it fails to on mine-, then either your screen is physically too small (as mine is), or your user-agent (or windowing system, or display, or video card drivers) is broken.

While you're totally correct, the point implementation fails to display the content correctly across all devices, hence it's not really responsive in the standard 'responsive design' definition.

If your intent is to display letters that are X inches high, then points correctly display textual content on all devices that:

* Know how large their display is

* Know the display's DPI

* Can correctly communicate this information to the underlying windowing system and applications

(Note that it is highly unlikely that any high-end "mobile" device fails to perform any of the items in the bulleted list.)

The designer wanted letters that were five inches high. It's not the designer's fault that your screen is too small. :)

Do you disagree that it is important to have a display-density-independent method of specifying the physical size of text or (for that matter) an image?

Re: My ISP has a poor service record. I made a tool to test how shitty it is

#33
post #14
post #9

Earlier quoted context omitted.

I dont suppose you have a tool that does this? I've been pondering building one, but I'd rather just skip to the part where I can start complaining about my service :p

smokeping does this.

came here to post about smokeping. here's their demo: http://oss.oetiker.ch/smokeping-demo/?target=Customers.OP

Re: My ISP has a poor service record. I made a tool to test how shitty it is

#34
post #25

Earlier quoted context omitted.

That's unfortunate. My little 512Mb Linode apparently couldn't handle it. It's back up for the moment. Edit: Scratch that. Resizing to a larger linode now. This got far more traffic than I ever expected it would.

Linode has a maximum packet per second limit set by default on all nodes. You'll need to email them to have them remove the limit for this particular box. They're very responsive and will increase it within a few minutes. No matter how big your instance is, there's probably way too many packets hitting it right now.

Ah. Good to know. This is just running on a personal test box. I'll email them, though I think the wave is over anyway.

Thanks :)

Re: My ISP has a poor service record. I made a tool to test how shitty it is

#35

Earlier quoted context omitted.

It's not on a machine I have access to right now, but I'm fairly certain it went something like: while [ "true" ] do printf 'google_ping %f %s' $(ping -c1 www.google.com | awk '/ms/ {print $7};' | awk -F '=' '{print $2};') $(date +%s) | nc graphite_host 2003 sleep 10 done

fwiw I use ping -n www.google.com | awk '/ms/ {split($7,p,"="); print "ping.google " p[2] " " strftime("%s")}; fflush()' | nc -q0 127.0.0.1 2003 &

I bow before your awk-fu. :)

Re: My ISP has a poor service record. I made a tool to test how shitty it is

#37
post #9

Earlier quoted context omitted.

I dont suppose you have a tool that does this? I've been pondering building one, but I'd rather just skip to the part where I can start complaining about my service :p

It's not on a machine I have access to right now, but I'm fairly certain it went something like: while [ "true" ] do printf 'google_ping %f %s' $(ping -c1 www.google.com | awk '/ms/ {print $7};' | awk -F '=' '{print $2};') $(date +%s) | nc graphite_host 2003 sleep 10 done

Awesome, thanks :)
Post reply on HN